Project Roles - Stackone

Project-level RBAC is only available on certain plans. See plans and pricing.

Apart from Organization Admins, a user can only reach a project once they’re given a role on it:

Role	Access
Project Admin	Manage everything in the project: every linked account, API keys, webhooks, and who has access.
Project Member	Link their own accounts, and use and manage them.
Project Viewer	See how everything in the project is set up, without changing anything.

Organization Admins act as Project Admin on every project, without being added to it.

Add people to a project and choose their role in Project Settings > Access, or give a whole group a role with Assign a group to a project.

What each role can do

Resource	Project Admin	Project Member	Project Viewer
Linked accounts	Link, edit, re-authenticate, suspend, delete, and run requests against any account	Link their own accounts, then edit, delete, and run requests against those	View status and details
Connector profiles	Create, configure, scope actions and events, and delete	Create their own, which they then manage, and link accounts through shared ones	View authentication type and enabled actions of shared profiles
MCP connectors	Add, and enable ones a Project Member added	Add one by linking their account to it. The connector and the account stay disabled until a Project Admin enables them	View
Request logs	View	View for their own accounts and accounts shared with them	View
API keys	Create, scope, and revoke	No access	No access
Webhooks	Create, route events, and delete	No access	No access
Project settings	Manage all settings	No access	No access

If explicit account access is enabled, a Project Admin can only view other people’s accounts until granted a role on them.

Which accounts a Project Member can hand to an AI platform.

Limit who can link accounts through a sensitive connector profile.

Let several people work through one linked account.