Use cases

Internal approval workflow apps, built with AI and approved by IT

An internal approval workflow app lets employees submit a request, such as a purchase or an access request, and lets the right reviewers approve or decline it with a record of who decided what. With Diakrin, a team describes the workflow to its coding agent, IT approves the app's data access and release, and the app runs in the company's own cloud behind company sign-in.

Last reviewed

An internal approval workflow app lets employees submit a request and lets the right reviewers approve or decline it, with a record of who decided what and when. Purchase requests, spend approvals, time-boxed access requests and vendor renewals are typical first apps, because they replace email threads and spreadsheets that nobody can audit.

What does the app do?

A typical approval workflow app has three screens:

  • Requests. An employee submits a request with the details reviewers need, such as item, amount, team and reason.
  • Approvals. Reviewers see a queue of open requests with the context they need and approve or decline each one.
  • History. Everyone sees the status of their own requests; reviewers see decisions over time.

Who uses it?

WhoWhat they do
RequestersSubmit requests and follow their status
ReviewersApprove or decline requests in their area
The app ownerChanges the workflow and manages who can open it
ITApproves the app's data access and its releases

For example, a finance team might run spend requests for the whole company, while an IT team runs access requests with a small group of approvers.

What data does it touch?

Requests and decisions live in the app's own PostgreSQL database in your cloud account. If reviewers need context from a company system, such as a budget figure or a list of systems, the app requests a named read operation. IT approves it with resource and field limits, and the app and each employee need their own grants. Credentials are entered by an authorized owner on a customer-hosted form, never in the coding tool.

How is it built?

The builder describes the app in the Diakrin console or straight from Claude Code, Cursor or Codex, then lets the coding agent build it on the company template. A useful brief:

text
App: Spend requests
Purpose: Employees submit purchase requests; budget owners approve or decline them.
Audience: Everyone can submit; the finance team and named budget owners review.
Initial data: Synthetic examples only.
Success: A requester sees their request and its latest decision; a reviewer can approve or decline with a note.
Before launch: Confirm reviewer access, approved data and the cloud setup.

Then ask the agent: "Use this app's approved requirements to build the spend request workflow with synthetic examples. Show any missing access or deployment prerequisites before continuing." See Create your first app and Connect your coding tool.

How does IT approve it?

  • Data access. Each named data operation is requested by the app and approved by IT, separately from the release.
  • Release. Diakrin builds and scans the app in your cloud, prepares a plan with the exact image, target, cost estimate and access implications, and, under your approval policy, an eligible reviewer who is not the requester approves or denies it.
  • Cost. The app has a monthly budget ceiling; a deployment that would exceed it is refused.

See Review capabilities and deployment.

Where does it run?

In your company cloud setup on AWS or Google Cloud, with its own service, database, file storage and secrets. On AWS, employees open the app at its address and sign in through Diakrin, which checks that they are still members and in the app's audience; the app receives a session for that person and never sees a password. On Google Cloud, the app stays on your private network behind Identity-Aware Proxy. See Sign in to company apps.

Related: request trackers and AI app governance.

Frequently asked questions

What kinds of approval workflows can teams build?

Common examples are purchase and spend requests, time-boxed access requests, vendor renewal reviews and onboarding sign-offs. Each is an internal web app with its own database in your cloud.

Who can open the approval app?

Only the app's audience. IT or the app's owner chooses named people, directory groups from your identity provider, access groups or everyone in the organization, and can give a person an end date.

Does the app need real company data from day one?

No. Start with synthetic examples. When the app needs data from a company system, it requests a named operation and IT approves it with resource and field limits.

Can the app send email notifications?

Not by default. Anything beyond the app's own service and data, such as email, is a capability the app must request, and a requested capability can be unavailable or need IT approval. General internet access from apps is not offered yet, so plan the first version around in-app status.

Who approves the app itself before employees use it?

Under your approval policy, an eligible reviewer who is not the requester approves the exact release plan, including the image, target, cost estimate and access implications.

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.