Browse documentation

Project roles

Understand Owner, Guest, and custom project permissions.

Project roles determine what a signed-in account can do inside a project. They are permission presets, not task ownership or an agent capability. An agent using rp acts through an account with project permissions; task review authority and the review policy still decide whether its approval counts.

Built-in roles

  • Owner has full project access. It cannot be edited or deleted.
  • Guest is the limited access for signed-in non-members of a public project and for members explicitly assigned Guest. Owners can edit Guest within its permission limits, but cannot rename or delete the built-in role. Guest is not anonymous access; a public Release download has its own separate visibility rules.

Owners manage these presets under Project Settings → Roles. Other roles are custom, regardless of their names. A custom role in use by a member or invitation cannot be deleted. Before granting an agent access, choose the narrowest role that lets its account do the intended work; do not treat a project role as permission to merge, publish or deploy without the separate workflow checks. Projects and access explains the project boundary.