Grant the access a task needs
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.
MolternPlatform teams
For your team
Make self-service fit the way your team operates.
Give builders applications and services while keeping access, policies and operating ownership in view.
Flight paths artwork / 08
Self-service should remove repeated setup without hiding responsibility. Organize workloads by environment, grant scoped access, and set policies for sensitive changes. Builders get a path forward while the platform team keeps the decisions that need central oversight.
Put it into practice
Bring organization controls into the workflow
Configure enterprise identity, policy guardrails and approvals according to your organization’s needs. Sensitive actions can require confirmation, MFA and an authorized role.
Check the release people will use
Inspect deployment status and logs, verify the URL and test the application’s main workflow. Record who owns configuration changes, service upgrades and recovery.
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.
What should I check when a deployment fails?
Start with deployment logs, build commands, runtime port, health checks and required variables, then follow the troubleshooting guide.
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 ↗