Skip to main content

Who decides what

Assume "an administrator can do anything" or "an owner decides everything" and you will lay the work out wrong. Authority is not a single flight of stairs. The roles are independent layer by layer, and the power to decide a review is settled on an axis of its own. Some things only a higher role can do — and some things a higher role cannot do.

This page explains how far each party can decide. Who to make a member and who to make a reviewer are in the Review Guide.

The roles fall into two layers​

The roles fall into two layers. On the admin side there are the system administrator, the organization admin and the auditor, who can only view the record screens of the admin console; on the project side, the owner, the operator and the member.

The two layers are different things. Holding a role in one does not automatically grant you a role in the other. Holding an admin role alone does not change a project's settings, and a project owner cannot change what the tenant has settled.

There is also the organization operations role, which can run projects without taking part in them (next section).

A project has owners, operators and members​

There are three roles inside a project.

An owner changes the project's settings and can start a run by hand. They also manage members. Changing a project's settings is for owners only.

An operator can do what a member can, and can also run the project: cancel a run someone else started, resume a run closed by a rejection or a failure, set a run's deadline, reassign reviewers, rerun a sweep, pause or resume the project, and extend the deadline of a review request (while an admin has stopped the project, pausing and resuming is not possible). An operator cannot change settings or manage members. As with owners and members, whether an operator can decide a review is not settled by the role (see “Review is not settled by role” below).

A member can see the overview, the run history, the run records and “Action needed”. They cannot change settings, but they can start a run by hand, and by email where starting by email is in use. They can cancel a run they started themselves. They can, however, decide a review on any step where they are named as a reviewer. In the project library, they can register files and add new versions (deleting is for owners only; registering and adding versions are only for people who may use “File attachment” under the feature permissions the administrator sets). So what is handed to a step can change through a version a member added.

A change that would leave no owner at all is refused. Before changing or removing a role, someone else has to be made an owner first.

Separately from the project roles, the organization operations role is the “Operator” role that a system administrator assigns in “Admin Roles” in the admin console (it is held for one's own organization; the badge on the project screens reads “Operations”). People with this role can read the definition and state of their organization's projects without taking part in them, and can start, cancel and resume runs, set deadlines, reassign reviewers, pause and resume projects, rerun sweeps, and extend review deadlines. They cannot see the Agent's outputs, artifacts or files in workflow runs and executions. They cannot open the settings or library screens, and cannot make other changes. When someone who takes part in a project also has this role, they can run the project in addition to what their project role allows.

Review is not settled by role​

This is where it is most often misread.

Whether you can decide a review is not settled by being an owner, an operator or a member. Only the reviewers named on that review step, and their delegates during the delegation period (end of this section), can decide it.

Even an owner cannot decide a review unless they are named as a reviewer on that step (or are a reviewer's delegate). Do not lay the work out thinking "put the owner in and approvals will flow".

The exception is a review request raised from the result of a “Run by Agent” step. If a step's result handling is set to “Ask for review”, the agent's result raises a review request. Such a step has no field for naming reviewers, so as a rule, every owner at that moment becomes a reviewer, and the owners decide (Design Guide). On a review step too, if every named reviewer has been removed from the members by the time the review request is raised, every owner at that moment becomes a reviewer in the same way. A review request raised before an agent uses a connector set to confirm before connecting (a connection confirmation) is handled the same as one raised from the result of a “Run by Agent” step.

The other way round, only participants in that project — owners included — can be named. Someone who is not taking part cannot be made a reviewer.

A reviewer can hand their decisions to one person in the same organization while away. In their personal settings, under “Projects” > “Delegate for review requests”, they choose the “Delegate and period” (up to 366 days). During that period the delegate, even if not a project member, can see the review requests handed over, decide them and extend their deadlines (no one can extend the deadline of a connection confirmation). Review requests, and the notices that a review deadline has passed or that a connection confirmation was closed at its wait limit, also reach the delegate both inside the product and by mail. The review request mail carries a link of the delegate's own, and the delegate can approve by replying to the mail. When reviewers are reassigned, the in-product notice goes to the newly assigned reviewers and their delegates, and the mail goes only to the newly assigned reviewers themselves. The handed-over review requests also appear under “Action needed” in the delegate's own Inbox. A delegate cannot pass this on to someone else. A decision made on someone's behalf shows “(for …)” with the original reviewer's name in the review request's activity and in the run history.

The tenant-wide execution rules are settled by the system administrator​

The tenant-wide rules for which operations an agent may perform are settled by the system administrator. A project owner can move the execution rules only in the stricter direction from them. An organization admin can see what the execution rules say, but cannot change them.

How the tenant-wide rules apply is covered in How much to delegate.

What you can connect to is chosen from what is provided​

Connectors work the same way. A project owner can choose from the candidates provided and authenticate them, but cannot add to the candidates. MCP servers that the project owner's organization or job type cannot use do not appear as candidates, and saving one is refused.

When what you want to connect to is not among them, the system administrator has to provide it.

An organization admin can see their organization's records​

An organization admin can see the records of runs made in the name of someone who belongs to one of the organizations they are responsible for (a project's runs go out in the name of the project's owner). Opening the body of a record takes a stated reason, and who opened it and why are recorded.

The body can be opened by the person themselves, by participants in the project, and by an organization admin for that organization. From the admin side, a system administrator cannot open the body on that credential alone. They can survey the records across the whole tenant, but the body takes an organization admin's credential. This is not a matter of rank.

The organization admin role can only be given to someone who belongs to that organization. An organization admin can add people from their organization to a project tied to that organization, as a member or an owner. They cannot, however, remove a member, or turn an owner or an operator into a member.

A project is tied to an organization when its “Organization” is set. Only an organization the person setting it currently belongs to can be chosen, either when the project is created or, for a project with no organization, once by an owner. Once set, it cannot be changed. A project with no organization is still shared with its participants, but it is not listed or managed by organization admins.

Runs go out in the project owner's name​

A project's runs go out in the name of the project's owner (the first owner is the person who created it; for a project made by copying, the person who copied it). An owner's authority is for managing the project, and is separate from the name runs go out in. Adding or changing owners alone does not change that name. When ownership is transferred, future runs go out in the new owner's name (later in this section).

What the runs produce goes to the owner at the time of the run too. A run's conversation is created as a conversation of the project's owner at the time of the run, but it does not appear in that person's “Chat” list, counts or search (opened in the chat screen, it points to the run record). Files the agent creates go into that person's “Library”. They do not appear in the “Chat” or “Library” of the other owners, operators or members (owners, operators and members alike can open the input files and artifacts listed in a run record). The project's time triggers and sweeps do not appear in the owner's “Schedule” either. You follow the runs on the project's screens.

How many conversations there are depends on how it runs. A workflow step makes a new conversation each time an agent runs. A cycle's sweep keeps using one conversation per placement, so the exchanges pile up with each sweep (a run started by a webhook or by email makes a new conversation each time).

So even when management is handed over by adding or changing owners, the name runs go out in, the conversations and the files the agents created all stay with the owner. When the people in charge change, transfer the ownership.

Ownership can be transferred by anyone with the owner role, and by a system administrator once the owner has left or been disabled. An owner uses “Transfer ownership” on the Settings tab, and a system administrator uses “Ownership handover” in the admin console. The new owner is an active user of the project's organization (when the project has no organization, an active user of the owner's current organization when an owner transfers it, or the active user chosen by a system administrator). It cannot be transferred while work is open, such as a run in progress or a pending review.

Once transferred, the project is paused (while an admin has stopped the project, it stays stopped). Sweeps are recreated in the new owner's name, and one-off starts that have not happened yet (webhook, email and rerun) are stopped. The previous owner stays as a member (and is removed if they have left or been disabled). Check the list shown on screen (connections, Playbooks and Skills) before resuming. The conversations and files of earlier runs stay with the previous owner.

Instead of transferring ownership, the project can also be handed over by copying it. A remaining owner copies the project and deletes the original. The copy's runs go out in the name of whoever copied it. What a copy does not carry over (connections to connectors, the project library's files and so on) is set up again in the copy. Time-based triggers are copied in a disabled state (Design Guide).

A connector's authentication belongs to the project. When the owner changes, the authentication stays in use, and it does not switch to the new owner's personal authentication. When it expires, a current owner authenticates it again (Connection Guide).

An agent's owner is also separate from the project's owner. Only an agent's owner can edit it, and neither changing the project's owners nor transferring the project's ownership changes who owns its agents. For a new owner to change an agent the previous owner owns, they prepare an agent they own and put it in its place (Design Guide). When an agent's owner has left or been disabled, a system administrator can transfer the agent's ownership with “Ownership handover” in the admin console (it cannot be done from the app's screens).

The "Who" in the records is not always a person​

The Who column in the record of operations inside a project lists agents and the system as well as people.

So do not read that column as always meaning a person did it. When you trace who did what, look at the kind of actor along with it.