Project Access & Portal User Authorization
AVAILABLEThe Project Access section controls which human Portal Users have permission to enter, view, and manage an individual Project workspace.
- Portal Location:
Projects & Workspaces > [Project] > Access & Authorization(/projects/[projectId]/access) - API Endpoint:
/v1/organizations/{orgID}/projects/{projectID}/users
Rendering diagram...
graph TD
Org["Organization Portal Users"]
Org --> Owner["Owner / Admin (Automatic Access to All Projects)"]
Org --> Standard["Standard Member (Requires Explicit Assignment)"]
Standard --> Assign["ProjectAccessAssignment"]
Assign --> Project["Project Workspace Access Granted"]
1. Access Model & Built-in Roles #
Naagmani enforces strict project authorization boundaries:
- Automatic Administrative Access: Organization Owners and Admins retain automatic organization-wide access to all project workspaces across all installations without requiring explicit assignment records.
- Explicit Assignment for Standard Users: All other organization users require an explicit
ProjectAccessAssignmentto enter the workspace. - Fail-Closed Isolation: Standard users cannot view project dashboards, members, service tokens, or API keys for projects to which they are not assigned (
403 Forbidden). - Inherited Authority: Permissions within an assigned project workspace (e.g. creating members, rotating tokens) are authoritative and inherited from the user's Organization Role.
2. Managing Project Access in Developer Portal #
Assigning a Team Member to a Project #
- Navigate to the target project workspace: Projects -> Select Project -> Access & Authorization (
/projects/[projectId]/access). - Click Assign Portal User.
- Select an active team member from the organization dropdown.
- Click Confirm Assignment. The user will now see this project in their project switcher.
Revoking Project Access #
- Locate the assigned user in the table under Assigned Portal Users.
- Click the trash icon / Revoke Access.
- Confirm the revocation dialog.
- Access is invalidated immediately. In-flight sessions or cached views in the user's browser fail closed on their next operation.
3. Empty State & Disambiguation #
- Zero Assignments: A user assigned to zero projects sees an informative empty state advising them to contact their organization administrator for project access. No unauthorized project names or descriptions are exposed.
- Single Assignment: Navigating to generic project links automatically redirects to the user's single authorized workspace.