Roles
Everyone in an organization has one of three roles: member, admin or owner. The person who creates the organization is its first owner. You see each person’s role on the Members page.
Members build and run the work. Owners and admins also manage what the whole organization shares: its app connections, its billing, its API keys and its people. Every plan includes unlimited members, so a role is about what someone may change, never about cost.
What each role may do
Section titled “What each role may do”| Task | Member | Admin | Owner |
|---|---|---|---|
| Create projects, and build, run, publish and pause workflows | Yes | Yes | Yes |
| Create and change agents, skills and databases | Yes | Yes | Yes |
| Approve or deny an action that is waiting for approval | Yes | Yes | Yes |
| Chat with agents and use the assistant | Yes | Yes | Yes |
| See the Apps page, the Members page, and the plan and usage on Billing | Yes | Yes | Yes |
| Change their own profile name and password in Settings | Yes | Yes | Yes |
| Connect an app, and reauthorize or disconnect a connection | No | Yes | Yes |
| Upgrade the plan and manage the subscription | No | Yes | Yes |
| Create and revoke API keys | No | Yes | Yes |
| Rename the organization and set its own AI key | No | Yes | Yes |
| Invite people as member or admin, change those roles, remove them | No | Yes | Yes |
| Get an email when an action is waiting for approval | No | Yes | Yes |
| Invite someone as owner, make someone an owner, or change or remove an owner | No | No | Yes |
Members
Section titled “Members”A member works with everything the organization already has. They use its connections in Action steps and agent grants, but they can’t add a connection. When a workflow or agent needs an app that isn’t connected, a member asks an owner or admin to connect it on the Apps page.
A member doesn’t see API keys in the sidebar. Opening that page directly lands them on the dashboard. On Billing, Members and Settings they see the same page as an admin, without the buttons that change the organization.
Admins
Section titled “Admins”Admins have every member ability, plus the organization-wide settings in the table above. Any admin can approve a waiting action, the same as any member. Admins are also emailed when one appears, with a link to the run. See Runs and approvals.
An admin can invite people as members or admins, switch someone between those two roles, and remove them. An admin can’t touch an owner’s role.
Owners
Section titled “Owners”Owners can do everything an admin can. On top of that, only an owner can invite someone as an owner, make someone an owner, change an owner’s role or remove an owner. An organization can have several owners.
An organization always keeps at least one owner. The last owner can’t be removed or given another role.
Super Flows has no separate ownership transfer and no way to delete an organization. To hand an organization over, make the new person an owner, then have them change your role. See Hand the organization over.
Roles and API keys
Section titled “Roles and API keys”An API key acts as the organization, not as a person, so it has no role. It calls the organization’s API, for example to start runs or query databases. It can’t connect apps or change the organization’s AI key, and it can’t use the assistant.
Where to change a role
Section titled “Where to change a role”Owners and admins change a role on the Members page. See Inviting and removing members.