Skip to main content

Roles Reference

A list of what each role can do in a Marketplace edition project. The way of thinking is in Who Can Decide What.

What they can doOwnerOperatorMemberOrganization operations role
See Overview, Execution history, Workflow history, and Action needed○○○○
See Settings○○○ (view only)—
Change Settings○———
Open the body of a record (a reason is required)○○○—
Start a case○○○○
Pause and resume the project○○—○
Cancel a case○○Only cases they started○
Stop a cycle execution○○—○
Set a case's deadline○○—○
Reassign reviewers○○—○
Edit a case's settings and artifacts (while awaiting review)○———
Enter the webhook secret for external wait○———
Export the definition○———

What decides a review is not the role but being a person named as a reviewer, or a delegate they have handed it to for a period. Even someone named as a reviewer cannot edit a case's settings or artifacts unless they are the owner.

A person who opened the project only through the organization operations role cannot open the definition screens (Edit and Settings). When calling the external API, a service account token can perform, on every project in this environment, the operations a service account is allowed. The token of a user who logged in through an external tool can call it according to that person's role and organization operations role (User API Reference (Projects)).

Decided for the whole environment​

These are decided in the admin console, outside the project. Their result applies to the project.

What they can doOwner / Operator / MemberAdministrator
Decide the whole-environment run rules (basic rule and prohibited operations) (“Execution rules” in the admin console; only a system administrator can decide them, and other administrators can only view)—○
Register a registered agent and enter its contract and certification (“Marketplace AI Agents” in the admin console)—○
Decide the destinations to block for outbound traffic (“Banned URL” in the admin console)—○
Decide the sending method and sender of review emails (“Announcements and Notifications” > “Notification Settings” > the “Mail Provider Settings” tab in the admin console; system administrators only)—○
Decide who may use “File attachment” (permission of the feature; system administrators only)—○

What anyone can do regardless of role​

  • Create a project (the person who creates it becomes the owner)
  • Copy a published project (the person who copies it becomes the owner)
  • Choose their own delegate for review requests (“Delegate for review requests” in personal settings)