Reference

Roles and permissions

Every member of your organization has one role, and the role decides what they can do. This page lists every built-in role and every permission it grants, side by side, so you can choose the right role for someone or find out why a button is missing. The tables come straight from Productmind's role definitions, and use the same names as the Roles tab.

Reading the tables

A permission is named by its row and its column, the way the Roles tab's grid names it: Tasks: Update is the Update column of the Tasks row. The rest of this guide names permissions the same way.

  • All means Create, Read, Update and Delete.
  • - means none.
  • Chat is a single switch rather than four columns, written Chat: Enabled in this guide. Enabled lets a role start chats and send messages. The Viewer and Customer roles show Disabled, and can still read conversations.

These are the built-in roles as Productmind defines them. Your organization may have Customized versions of some of them, or Custom roles of its own: the Roles tab shows what your organization's roles really allow. See Roles.

The built-in roles

RoleDescription
OwnerFull access to everything, including billing, member roles, and ownership transfer.
AdminManages the workspace, members, and settings, plus full access to all product work.
Power UserProduct, Engineering, Feedback and General. Everything except Settings — for someone who works across the whole product.
DeveloperProduct, Engineering and General. For engineers who build features — no customer feedback or Settings.
Product ManagerProduct, Feedback and General, and can read applications. For people who run the product process, with no other Engineering access and no Settings.
ViewerRead-only access across all product work.
CustomerReads product work, and can comment and submit feature requests.

Permissions on your product work

ResourceOwnerAdminPower UserDeveloperProduct ManagerViewerCustomer
Core work
Agentic interviewsAllAllAllNoneAllReadRead
Customer meetings & supportAllAllAllNoneAllReadRead
Internal meetingsAllAllAllAllAllNoneNone
Bug reportsAllAllAllAllAllReadCreate, Read
Feature requestsAllAllAllAllAllReadCreate, Read
FeaturesAllAllAllAllAllReadRead
TasksAllAllAllAllAllReadRead
SessionsAllAllAllAllAllReadRead
ApplicationsAllAllAllReadReadNoneNone
AutomationsAllAllReadReadNoneNoneNone
ReleasesAllAllAllAllAllReadRead
MarketingAllAllAllNoneAllNoneNone
Collaboration
CommentsAllAllAllAllAllReadCreate, Read
LogsAllAllAllAllAllReadRead
Decision recordsAllAllAllAllAllReadRead
AttachmentsAllAllAllAllAllReadRead
TagsAllAllAllAllAllReadRead
Workspace resources
NotesAllAllAllAllAllReadRead
Knowledge baseAllAllAllAllAllReadRead
AccountsAllAllAllNoneAllReadRead
ContactsAllAllAllNoneAllReadRead
ChatEnabledEnabledEnabledEnabledEnabledDisabledDisabled
Audit logAllAllNoneNoneNoneNoneNone
Productmind support requestsAllAllAllAllAllNoneNone

The groups are the Roles tab's:

  • Core work is the records you work on.
  • Collaboration applies across those records: comments, logs, decisions, attachments and tags on features, tasks, sessions and the rest.
  • Workspace resources is everything else in a workspace.

Automations and Internal meetings are being rolled out gradually. If they aren't enabled for your organization, their rows don't appear on your Roles tab.

Marketing is the permission for your customer release notes, blog posts and customer emails. Read sees Marketing, the notes, the blog posts and their published and approved versions, and the customer emails and their send log. Update drafts, redrafts and edits a release's notes, blog posts and customer emails. Create publishes the notes, approves blog posts and sends customer emails. Delete deletes blog posts. Customer emails also need Contacts: Read, because they show your contacts' email addresses. The Owner, Admin, Power User and Product Manager roles hold all of it, and Developer, Viewer and Customer hold none. Custom roles, and Customized versions of a built-in role, don't get it automatically: contact Productmind support to add it. See Marketing.

Administrative access

Some access isn't part of the grid. The Roles tab lists it under Administrative access, and it can't be changed for any role.

AccessWhat it allowsRoles
Members & roles
Invite & manage membersInvite people, update their access, and remove members.Owner, Admin
Change member rolesAssign or change which role a member has (except owner).Owner, Admin
View roles & permissionsSee the organization's roles and what each role can do.Owner, Admin
Manage teamsCreate teams and manage their members. A team role adds to a member's permissions.Owner, Admin
Organization
Edit organizationUpdate the organization's profile and details.Owner, Admin
Manage billingChange the subscription plan, buy credits, and set overage and auto-recharge.Owner, Admin
Billing details & invoicesSee and edit the billing details, billing profiles and payment methods, and download invoices.Owner
Transfer ownershipHand ownership of the organization to another member.Owner
Workspace settings
Create workspacesCreate new workspaces in the organization.Owner, Admin
General settingsChange workspace configuration, guardrails, and git workflows.Owner, Admin
IntegrationsConnect and manage the workspace's tools and MCP servers.Owner, Admin
Engineering
SandboxesCreate and manage sandbox container specs.Owner, Admin, Power User, Developer
AgentsManage agent availability, contexts, skills, and templates.Owner, Admin, Power User, Developer
Not listed on the Roles tab
Single sign-onSet up sign-in through your identity provider, and require it.Owner, Admin
Multi-factor authenticationRequire an authenticator app at sign-in, and see who has set one up.Owner, Admin
Audit log retentionChoose how long the audit log keeps events.Owner, Admin
Model providerConnect, replace, verify or remove the organization's own model key.Owner, Admin
Cloud accountsSee the AWS accounts your workspaces deploy into.Owner, Admin
Application and sandbox settings through an AI assistantChange applications' and sandboxes' settings through your own AI assistant.Owner, Admin

How roles behave

One role per member. You choose a member's role when you invite them, and can change it on the Users tab. A change takes effect right away.

Teams add, never take away. A member of a team with a team role gets that role's permissions as well as their own. See Teams.

Workspaces come first. A role applies in the workspaces a member can use. Owners and Admins get every workspace, and everyone else uses the workspaces they have been given. See Organizations and workspaces.

The Owner is one person. Every organization has exactly one owner, and only the owner can transfer ownership. Nobody else can be given the Owner role.

Tools act with your role. The Productmind CLI, AI assistants and API clients you sign in to can do exactly what your role allows, and nothing more. See API access and authentication. Changing application and sandbox settings through an AI assistant is for the Owner and Admin roles only, whatever else a role allows. See AI assistants.

Roles are managed by Productmind. You can't edit a role in the app. To get a role that fits a job the built-in roles don't, contact Productmind support.

Troubleshooting

A menu item or a button is missing

Find the page's permission in the tables above, then check your role: choose your avatar at the bottom of the sidebar, then Profile. Under Your organizations, your role is shown next to each organization. Or ask an Owner or Admin of your organization. If your role should allow it, the feature may be behind a rollout: see the page's Availability block, and Troubleshooting. A feature your plan doesn't include isn't missing: it shows a lock. See Features that depend on your plan.

Last modified on