# Get started

> The onboarding checklist: who does what, in which order, and what to prepare.

Source: https://diakrin.com/docs/get-started

Onboarding takes a few people, each doing one part. Start with one team and one small app; you can widen access once the first app works end to end.

## The onboarding path

```steps
Connect company sign-in | Identity administrator | Follow [Connect your company SSO](/docs/sso): choose your provider, configure a pilot and confirm activation with your Diakrin onboarding contact.
Enter your organization | Everyone | Your onboarding contact or an administrator assigns your email before signup. Sign in with that email and verify it; an active assignment or invitation attaches automatically. See [Invite your team and set roles](/docs/team).
Set organization policy | IT administrator | In **Get started**, choose **Set organization policy** to save spending limits and the rules new projects follow.
Connect your cloud | Owner, admin or Technical administrator | Open **Infrastructure → New setup**, choose AWS or Google Cloud and follow the steps. See [Set up your company cloud](/docs/company-cloud).
Build the first app | Builder | In **Apps**, select **New app** and explain what it should do, or start from **Create example app** in **Get started**. See [Create your first app](/docs/first-project) and [Connect your coding tool](/docs/builders).
Review and launch | IT reviewer | Check capabilities, cost and audience, approve the plan, then confirm the real app works for an authorized employee. See [Review capabilities and deployment](/docs/governance).
Invite your team | IT administrator | Add builders and reviewers once the first app works. See [Invite your team and set roles](/docs/team).
```

Builders can start describing their app while a Technical administrator prepares the company cloud; the two paths meet at the first deployment.

## Set up a self-hosted installation

Install Diakrin in your own AWS account with the [self-hosted install guide](/docs/self-hosted/install). There is no public registration. The person who installs Diakrin completes a one-time sign-in that creates the first owner and the only organization. Owners and administrators then add an authenticator app and save their recovery codes. The console walks the owner through five steps, each verified by the server from current evidence:

```steps
License | Installation operator | Enroll the license, or import a signed license file; the step verifies the signed grant. A test license is labelled as one and is for disposable test installations only.
Workspace | Owner | Verify administrator access and add a second administrator for independent app reviews.
GitHub | Owner | Install the Diakrin GitHub App on your company organization for selected private repositories. Your GitHub Actions runner labelled `diakrin-customer` checks each save; CodeBuild in your account builds, scans and stores the app image.
Deployment prerequisites | Owner | Approve organization spending limits. The server checks DNS and TLS, isolation, the audit archive and the scanner.
First app | Owner + second administrator | Deploy the supplied synthetic app through **Apps**. The second administrator approves its private preview.
```

The cloud installation itself (the Diakrin CLI, certificates, infrastructure and deploy) is in [Install self-hosted Diakrin](/docs/self-hosted/install).

AI assistance is a separate optional card and starts off. Saved settings alone never complete a step.

## Who does what

| Person | First responsibility |
| --- | --- |
| Organization owner | Creates the workspace, chooses administrators and arranges onboarding |
| Identity administrator | Configures the SSO application, its pilot users and optional SCIM provisioning |
| IT administrator | Sets spending limits, invites people, assigns apps and reviews access |
| Technical administrator or cloud administrator | Connects the company cloud and verifies the infrastructure and employee access |
| Builder | Describes an app and builds it within the app's approved access |
| Team member | Accepts an invitation and uses assigned apps |

The owner and the identity administrator can be different people. Employees do not need database credentials or cloud administration access to join Diakrin.

## Prepare for onboarding

- The organization name and the person who will own the workspace.
- Your identity provider and the exact work-email domains you use.
- An identity administrator and two pilot users, including one regular member.
- A simple first app, its intended users and whether it needs real company data.
- Your cloud account (AWS or Google Cloud today, Azure coming soon) and the person who can approve access to it.
- Your Diakrin onboarding contact, who supplies the SSO setup packet and confirms activation.

## Know what is ready

The console keeps saved app definitions, requested capabilities, approved access and real runtime connections apart. A saved app or a green sign-in does not mean an app is deployed. [Key concepts](/docs/concepts#saved-is-not-the-same-as-live) explains what each state proves.

> [!SAAS]
> Company SSO needs activation and a successful pilot for your organization. SCIM provisioning can add and remove members automatically, but identity-provider groups never become Diakrin roles on their own.

For a blocked step, use [Troubleshooting and help](/docs/troubleshooting).
