# Create your first app

> Describe the app, its audience and the data it needs.

Source: https://diakrin.com/docs/first-project

Choose a small app with a clear owner and audience, such as an internal request tracker. Start with synthetic data until IT has approved real data access.

## Have IT prepare your app

An owner or admin can select **Prepare an app for a team** and choose the builders by their team emails. Members and Technical administrators cannot receive building assignments without an IT-approved company role change.

This prepares building access, a draft approval policy and spending ledgers together. It does not deploy an app. Builders can begin describing the app while a Technical administrator prepares the company cloud.

> [!SELF-HOSTED]
> Apps can be created only after IT configures the audit archive. Until then, builders see "Your company's Diakrin setup is not ready to create apps yet" and nothing is created.

## Describe the app

1. Sign in, select the correct organization and open **Apps**. Choose an assigned app. If none is assigned, ask IT to prepare one.
2. If the company allows you to create apps, select **New app** instead. Your company’s current creation policy determines whether approval is required.
3. Enter **App name** and explain **What should the app do?** Describe the workflow and the result you want.
4. Describe **Who will use it?** and **What kind of data will it use?** Start with sample data. IT handles infrastructure choices and approved capabilities; advanced environment settings are optional.
5. Review and save the app idea. Confirm the saved definition after a reload. A pending approval, saved idea and deployed app are separate states.

## A useful first brief

```text
App: Team request tracker
Purpose: Employees submit requests; team leads review and update their status.
Audience: The operations team and its assigned reviewers.
Initial data: Synthetic examples only.
Success: A requester can see their own request and its latest status.
Before launch: Confirm ownership, reviewer access, approved data and the cloud setup.
```

Keep passwords, access tokens, customer records and production datasets out of the app brief and coding-agent chat. Requirements describe what the app needs; they do not provision credentials.

## Work within approved capabilities

Open the app and review its capabilities, policies and activity. A capability may be requested, unavailable, blocked or require approval. Ask your administrator for the required permission instead of working around a blocked action.

A saved app definition is the start of a build. It does not prove the application has been generated, deployed, connected to real data or accepted for use.

## Continue the build

Follow [Connect your coding tool](/docs/builders) so the agent works with the same app. When it is ready to ship, follow [Preview, approve and deploy](/docs/deploy), and have IT review [capabilities and deployment](/docs/governance) before launch.

For a first task, ask your coding agent: “Use this app’s approved requirements to build a request tracker with synthetic examples. Show any missing access or deployment prerequisites before continuing.”

## Projects are optional

Start in **Apps** with the app itself. A project can group several apps under shared permissions, budget and policy. Grouping does not grant additional access. Moving an app across those boundaries needs an explicit reviewed migration; a normal edit cannot widen its permissions.
