Manage projects, members & roles
Set up the project structure, get the right people in with the right access, and keep it current as the team changes.
Roles at a glance
Section titled “Roles at a glance”Access works at two levels:
- Organization roles —
owner,admin,member— set when someone is invited to the organization. - Project roles —
owner,admin,editor,viewer— set when an organization member is added to a project.
| Project role | Can do |
|---|---|
| Viewer | See the project’s processes, runs, and tasks (read-only). |
| Editor | Plus build and deploy processes, agents, functions, decisions, and forms, and work tasks. |
| Admin | Plus manage the project’s members and settings. |
| Owner | Full control of the project. |
Beyond these built-in roles you can define custom roles with granular permissions (see below).
Create a project
Section titled “Create a project”-
Open Projects. In the organization sidebar, click Projects. (The project switcher also lives in the sidebar header.)
-
New Project. Give it a name and an optional description, and save. The project opens with you as its owner.
Screenshot placeholderThe Projects page with New ProjectReplace with real capture from app.superagent.studio
Add a member to a project
Section titled “Add a member to a project”-
Open the project’s members. Go to Settings → Members.
-
Add a member. Search for an existing organization member and pick their project role (viewer / editor / admin / owner). To bring someone entirely new into the organization first, invite them by email at the org level (Settings → Members at the organization).
-
Save.
Change a role or remove a member
Section titled “Change a role or remove a member”On Settings → Members, change a member’s project role from the dropdown, or remove them from the project. Their past actions (approvals, edits) stay in the audit trail under their name; only their current access changes.
Custom roles
Section titled “Custom roles”When the four built-in project roles don’t fit, go to Settings → Roles → Create role, pick a set of granular, category-grouped permissions, and assign it like any built-in role.
Groups — routing, not permissions
Section titled “Groups — routing, not permissions”Settings → Groups define who work is routed to. A user task’s assignee group draws from these. Keep the distinction clear: a role says what a member may do; a group says which tasks reach them.
Archiving a project
Section titled “Archiving a project”Settings → Archive project stops the project’s triggers, hides it from the default list, and makes its runs read-only. Unarchive at any time to restore it.