> For the complete documentation index, see [llms.txt](https://docs.emseapea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emseapea.ai/admin-guide/getting-started.md).

# Getting started: your org in 15 minutes

emseapea gives every employee-built AI app in your organization one safe path from idea to production, and keeps a live map of everything that gets built.

**Before the fifteen minutes**, somebody has to create accounts and credentials in other companies' consoles — Cloudflare, Microsoft, Salesforce, Google, and wherever your apps will keep their files. Steps 3 and 4 below have nothing to act on until that is done, so start at [Setting up your accounts](/setting-up-your-accounts/accounts.md), which also says plainly which of those are not yet worth creating.

An empty org becomes a working one in five steps:

1. **Sign in** with the admin account created for your org (or via your trial invite code). The org badge at the top of the sidebar always shows which organization you are acting in.
2. **Invite your people** — Settings people arrive by email invitation with a role attached: *admin*, *approver*, or *builder*. See [Users and roles](/admin-guide/users-and-roles.md).
3. **Set the connector allow-list** — the systems apps may request access to (ERP, CRM, HR, …). See [The connector allow-list](/admin-guide/connectors.md).
4. **Wire your integrations** — GitHub (repo templates), Linear (card sync), and your credential gateway. See [Integrations](/admin-guide/integrations.md).
5. **Approve your first request** — when a builder submits one, it appears in Approvals. Approval automatically creates the repo and issues a scoped credential; you'll see the app's lineage graph grow in real time.

Everything above — every invite, approval, and setting change — is recorded in the [audit log](/admin-guide/decommission-and-audit.md) the moment it happens.