Project-level roles and sensitive-action confirmation
PlannedPlanned roles require server-side permission enforcement; hiding buttons is not authorization.
What this does
Will separate owner, administrator, developer, release manager, QA reviewer, client approver, viewer, and billing manager actions.
What you need
Organization membership and explicit project assignments.
What LaunchLayer automates
Planned permission matrix, audit events, and elevated confirmation for sensitive operations.
What remains external
Identity-provider policy and organization governance.
Exact setup steps
Not released; current account/workspace access remains unchanged.
How to verify it
Attempt every sensitive API as every role, including direct function invocation.
Common failures
Client-only gating, stale membership, cross-project access, or privilege escalation.
Security considerations
Credential changes, uploads, roles, deletion, and billing require recent authentication or elevated confirmation.
Related articles
Security and ownership.