Try the workflow with the team
Choose a specific problem and the people who need the result. Involve a technical owner for configuration and access, then validate the workflow with its users.
MolternLaunch an internal tool
Guides
Solve one team problem before building a bigger platform.
Choose the smallest app or service that can deliver a useful result to real users.
Flight paths artwork / 21
Write down the job, the people using it and the data it needs. Pick a catalog service or deploy the application you own. Configure access with a technical owner, test the workflow with that team and agree who will maintain it after launch.
Launch an internal tool
Choose the required services
The catalog includes data, automation, AI, monitoring and other packaged software. Read each service guide before deployment and review its configuration and dependencies.
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.
Detailed instructions are maintained in the product documentation.
Questions before you start
Can a non-developer start a project?
A business team can define the need and explore services. Involve an authorized technical owner for deployment and sensitive configuration.
Does every service have the same setup?
No. Required variables, dependencies, storage and access differ. The individual service guide explains the setup.
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.
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 ↗