Roles & Permissions

Access in ArtlessDev is controlled at two levels: Workspace roles govern the team, billing, and Workspace-wide settings; Project roles govern what a member can do inside one specific Project. A person can hold a Workspace role and a different Project role in each Project they’re a member of.

Workspace roles

• Owner — full access; exactly one per Workspace; can’t be reassigned.
• Admin — manages teammates, billing, and Workspace settings.
• Member — has access to the Workspace; their capabilities inside any given Project come from their Project role there.

Project roles

• Reader — browse only. Can see Scenarios and their statuses, but can’t change anything.
• Reviewer — can change either status axis, but not Scenario content.
• Editor — can edit Scenario content and change either status axis.
• Member — the same as Editor (edit content and status); the default contributor role on plans without granular roles.
• Admin — everything Editor can do, plus managing Project members.
• Owner — the Project’s creator; full access.

Put another way: editing content requires Owner, Admin, Member, or Editor. Changing a status requires any role except Reader. Workspace admins can manage Project members even without an Admin role on that specific Project.

Role availability

Some Workspaces can only assign Admin and Member per Project. Workspaces with granular roles unlock the full set — Reader, Reviewer, Editor, and Admin — which is what makes it possible to add a stakeholder who can browse without ever being able to edit, or a QA reviewer who can record a gap without touching the Scenario’s content.

Invites and seats

Members are invited by email and accept by signing up or signing in with that exact address. A pending invite can be revoked before it’s accepted. A Project invite requires the invitee to already be a Workspace member — invite them to the Workspace first if they aren’t. Every accepted invite counts toward the Workspace’s seat limit. See Inviting Your Team for the practical steps.