Organizations

Roles and permissions

Clerk organization permissions, workspace roles, and how effective access is calculated.

10 min read

Especially for

adminownerorg admin

Typically requires permissions

org:settings:manage

PromptPal uses two complementary systems:

Clerk organization permissions

Used on sensitive org APIs and sidebar visibility:

  • org:audit:view — audit logs and export
  • org:prompts:create / edit / delete / share_external
  • org:members:manage
  • org:settings:manage
  • org:billing:manage

Clerk roles such as org:admin, org:workspace_admin, org:editor, org:viewer, org:api_only map to these permissions.

Workspace roles

Per workspace membership: owner > admin > editor > reviewer > viewer.

Lifecycle actions (submit, approve, reject, deprecate) use workspace roles. The effective organization role can be derived from workspace memberships when Clerk permissions are absent (legacy fallback).

Organization owner

The user in organization.ownerUserId has owner-level access regardless of workspace role.

ActionViewerEditorReviewerAdminOwner
View org library & run playground (if policy allows)YesYesYesYesYes
Edit org promptsNoYesYesYesYes
Approve review queue itemsNoNo*YesYesYes
Manage org settings / SSONoNoNoWith permissionYes
View org audit logsNoNoNoWith org:audit:viewYes

Related articles