Getting started

The quickstarts get one framework to a first sign-in. These pages are the next layer: the decisions behind that first app, and the things most products add next.

Your app

• Integrate your app — where a client_id comes from: register an application, copy its credentials, find your issuer, point an SDK at them; publishable keys and drawing your own sign-in form.
• Organizations in your app — ask for an organization, let people pick, switch or create one, and let strangers sign themselves up.
• Sign in from a CLI — the device grant, for a terminal, a CI job or anything without a browser of its own.
• Let your customers create API keys — keys for your own app's API, created on a hosted page and verified with your app's credentials.

Your backend

• Run your tenancy from your backend — the environment management API by task: organizations with owners, members, invitations with your app's roles, admin & support roles, apps, APIs and support sessions.
• Enterprise self-serve — hand a customer's IT admin an Admin Portal link so they set up Enterprise SSO and Directory Sync themselves.

The console

• Screens — the workspace, organization and environment consoles and the sign-in surface, area by area.

Running Cbox ID yourself

• Installation & first run — set up the app, create the first platform operator, and provision your first environment and organization. The short version is the self-hosting quickstart; for production hardening, see Deployment.