Project access requests
Updated 2026-04-18
If you are in an organization but cannot access the project you need, use the project access request flow instead of asking for broad org-level role changes.
When to request access
Request access when:
- You can open the organization but see no eligible projects
- You are scoped to some projects and need one more
- You are a viewer and need project visibility for review
Member flow
- Open the organization workspace.
- Go to the relevant area where project access is missing.
- Use the in-app request action and include context (project name, reason, urgency).
Role required: Any organization member can submit a request for additional project scope.
Admin/owner flow
Owners/admins should process requests by:
- Verifying requestor identity and org role.
- Granting only required project IDs (least privilege).
- Confirming requestor can access the target project after update.
Role required: Owner/Admin to update member project scope.
Best practices
- Prefer targeted project scope over blanket role elevation.
- Remove stale scope when engagement ends.
- Keep request notes concise so audits can reconstruct why access changed.
Related
- Team & invitations — role and project scope fundamentals
- Organizations — workspace context and routing
- Troubleshooting — permission and access diagnostics