Use cases
Internal admin panels with access IT has approved
An internal admin panel is a back-office app that lets a small, trusted group view and manage records, such as accounts, vendors, contracts or reference data. With Diakrin, a team builds the panel with its coding agent, IT approves exactly which data operations it may use and who may open it, and the panel runs in the company's own cloud with every release approved.
Last reviewed
An internal admin panel is a back-office app that lets a small, trusted group view and manage records: customer accounts, vendors and contracts, reference data, or configuration that other teams depend on. Admin panels are useful and risky for the same reason: they sit close to important data. The questions IT asks are always who can open it, what it can reach and who approved the latest change.
What does the app do?
- Lists records. Searchable, filterable tables of the records the panel manages.
- Shows detail. One record at a time, with its history.
- Edits within limits. Create and update records the panel owns, with validation.
- Records changes. Who changed what and when, stored by the app.
Who uses it?
| Who | What they do |
|---|---|
| Operators | View and update records as part of their job |
| A team lead | Reviews changes and handles exceptions |
| The app owner | Manages the audience and the panel's features |
| IT | Approves data access, the audience policy and releases |
For example, a procurement team might manage vendor contracts and renewal owners, or an IT team might manage time-boxed access records.
What data does it touch?
Records the panel owns live in its own PostgreSQL database in your cloud, with files in its own storage and secrets in your cloud's secrets service. When the panel needs data from a company system, the app requests a named operation, and IT approves it with resource and field limits. The app and each employee need their own grants, and only an authorized owner enters credentials, on a customer-hosted form. Request only the operations and fields the panel needs.
On AWS, IT can see what the app stores by size and name, never by value, and can set retention, export, quarantine or delete its data. See Manage access and security.
How is it built?
Describe the panel to your coding agent, starting with synthetic data:
App: Vendor contracts admin
Purpose: Let procurement view vendors, their contracts and renewal owners, and update contract details.
Audience: The procurement team only.
Initial data: Synthetic examples only.
Success: An operator can find a vendor, open its contract and update the renewal owner; each change is recorded with who made it.
Before launch: Confirm the audience, any approved data sources and the cloud setup.The agent connects through MCP or the Diakrin CLI as you, reads the app's approved requirements and builds on the company template. If it needs access the app does not have, it requests it from IT. See Connect your coding tool.
How does IT approve it?
- Audience. Named people or an access group, with end dates for temporary access. Admins can require company SSO or a shorter session for this app; an app can tighten the organization's sign-in policy but never loosen it.
- Data. Each named operation is approved separately, for the app and for each employee.
- Release. Under your approval policy, an eligible reviewer who is not the requester approves the exact plan before promotion, and each later publish follows your approval policy.
See Review capabilities and deployment.
Where does it run?
In your company cloud setup on AWS or Google Cloud. On AWS, employees sign in through Diakrin at the app's address, and the app receives a session for a checked person, never a password. On Google Cloud, the panel stays on your private network behind Identity-Aware Proxy. See Sign in to company apps.
Related: operations dashboards and approval workflows.
Frequently asked questions
Who should be able to open an admin panel?
Usually a small group. Set the app's audience to named people or an access group, give temporary users an end date, and require company SSO or a shorter session for the app if the data is sensitive.
Can an admin panel edit records in company systems?
The app can manage records in its own database. Access to a company system is a named operation that IT approves with resource and field limits. Do not assume broader access than the grants IT has approved.
How do we stop an admin panel from becoming a data leak?
Keep the audience small, request only the operations and fields the panel needs, and keep credentials out of the coding tool. On AWS (BYOC), IT can see what the app stores, quarantine its data or stop its runtime.
What happens to access when an admin leaves?
Removing the person from the Diakrin organization revokes their app grants, ends their recorded app sign-in sessions and stops their coding-tool tokens.
Do we have to give the builder cloud console access?
No. The builder works through Diakrin with their own permissions. Builds, deployments and data controls run in your cloud through the access IT has set up.
See Diakrin with your own cloud
Let your team build internal apps with the AI tools they already use, while IT keeps control of identity, data, approvals and spend.