Review people and resource grants
Use managed roles and the narrowest useful scope. Set expiry for temporary access, inspect effective permissions and revoke the grant when the work is finished.
MolternManage team and agent access
Guides
Give each person and agent the access their task needs.
Use managed roles, narrow scopes and a clear way to review or revoke access.
Flight paths artwork / 24
List the resources required for the task before granting permissions. Choose a managed role and the narrowest scope, and use expiry for temporary work. Treat secret use and secret reveal as different decisions. Review the effective access and remove grants when the work ends.
Manage team and agent access
Review identity and policy requirements
Configure enterprise identity, policy guardrails and approvals according to your organization’s needs. Sensitive actions can require confirmation, MFA and an authorized role.
Agree on ownership and handover
Document the infrastructure boundary, access model and responsibilities for configuration, upgrades, data and recovery. Agree on a handover before production use.
Detailed instructions are maintained in the product documentation.
Questions before you start
Does using a secret allow someone to reveal it?
Secret use and secret reveal are separate permissions. Grant sensitive access only when the task requires it.
Which identity and review controls are documented?
The platform docs describe SAML/OIDC, provisioning, scoped roles, access reviews, approvals, sessions and audit history.
Is infrastructure ownership the same as a security certification?
No. Infrastructure placement and operational responsibility are design choices, not claims of independent certification.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗