Roles & Permissions
Pragence applies organization roles and, for project-scoped work, project membership roles. Each API operation declares its own authorization checks, so a role name by itself does not imply access to every resource or action.
Organization roles
Organization users use the admin, member, or viewer role. The first user
created for a new organization is assigned admin. Organization administrators
can manage organization membership and settings through administrator-only
operations. Other operations may grant members or viewers narrower access.
Project roles
Project membership uses owner, admin, member, or viewer. Project
operations check the required minimum role; for example, project configuration
and agent updates require an administrator-level project role, while process
workflows can permit members. Project deletion requires the project owner or an
organization administrator.
Organization admins receive elevated access in many project operations, but authorization remains endpoint-specific. Source access also checks project membership, visibility, and document permissions. Do not infer that membership in one project grants access to another project's private sources.
Managing membership
Use the organization and project membership endpoints in the
API reference and
Projects API. New project memberships default
to member in the project service; invitations and other creation flows may
apply their own documented defaults. Verify the resulting role after inviting
a user.