Managing users & roles

Superprocess uses role-based access control at two levels: the organization (who’s in your company’s Superprocess) and each project (what they can do there).

• Organization members are invited by email and are owner, admin, or member.
• Project members are organization members added to a specific project as owner, admin, editor, or viewer.

The members page

Screenshot placeholderA project's Settings → Members list with rolesReplace with real capture from app.superagent.studio

Inside a project, Settings → Members lists everyone with access and their project role.

Add someone to the project

Screenshot placeholderAdd member — search an org member and pick a roleReplace with real capture from app.superagent.studio

Click Add member, search for an existing organization member, and pick their project role. Someone new to the company? Invite them to the organization first — Settings → Members at the organization level — by email; then add them to the project.

The built-in project roles

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.

For the invoice flow a typical setup is: AP clerks are editors (they build and handle tasks), the AP manager is a project admin (onboards vendors, manages access), and finance leadership are viewers (visibility, not control).

Custom roles

Need something the four built-in roles don’t cover — say, someone who can work tasks but not edit processes? Create a custom role under Settings → Roles with exactly the permissions you want, and assign it like any built-in role.

Groups — routing, not permissions

Separately, Settings → Groups decide which tasks route to whom. Keep the two apart: a role is what a member can do; a group is which tasks reach them.

Changing a role, or removing a member

Open Settings → Members, change a member’s role from the dropdown, or remove them. A role change takes effect immediately; removal revokes access but leaves their past actions in the audit trail under their name.

Audit trail

Every consequential action is recorded — tasks decided, processes deployed, secrets rotated, members changed. Project admins can review the audit log for compliance or to retrace an incident.

Organization roles

Above project roles, organization roles — owner, admin, member — govern who can create projects, invite people to the company, and manage org-wide settings like connectors and secrets. They change rarely and are set as your organization grows.

Next

What's next →Where to go after the full user guide.