Skip to content

Members, roles and teams

Who can do what in SpecsGraph: the four roles of an organisation, teams, the project edit gate, invitations and what agents may do for you.

Roles

A member has one role in the organisation. Each role can do everything the role above it in this table can.

RoleCan
Viewerread every project, comment, reopen threads
Editoralso edit in workstreams, accept staged revisions, run tasks, publish, resolve conflicts and threads; edit work items and record results; mark code as implemented; create and order milestones
Adminalso create and archive projects, manage project settings and Git, members, invitations, teams, integrations and the token policy; set the flow template, code repositories, deploy tokens and work source; unblock a work item; overwrite a blocked publish
Owneralso billing, export, import and deleting the organisation

An organisation always keeps at least one Owner.

Teams and the project edit gate

Teams group members. A project's Settings > Teams lists the teams that may edit it: with none, every Editor may; with some, only their members plus Admins and Owners. Everyone else reads.

Questions can be asked to a team, and each member hears about it.

Invitations

Admins invite by email with a role, and can also copy the invitation link and send it themselves. A member is removed from Settings > Users; removing someone revokes their access tokens in the organisation.

An invitation that is still pending takes a seat, like a member, until it is accepted, revoked or expires. When every seat is in use, new invitations wait until an Owner adds seats in Settings > Billing or someone frees one; see How seats work.

Agents act for a person

An agent uses your access token, or signs in as you, and can never do more than you, and does less: agents never publish, manage settings, record a verify or uat result, edit or complete work items, mark code as implemented or change the roadmap, and unless the project has Agent autonomy on, they never edit a workstream directly, accept, scope, mark a task Ready, mark Done or resolve threads. Read only tokens only read.

Tip

What agents do instead

Agents stage revisions into the workstream's proposal, group them into plans for the task they intend, and ask questions with thread_ask. A person accepts, marks Ready and publishes. With Agent autonomy on, an agent with read and write access accepts, scopes and marks Ready too; a person still publishes.

Next steps