DEVELOPERS

Use Atom9 login and workspace context in your app.

Atom9 can provide account creation, login apps, invited users, sessions, and profile context for products that do not want to build authentication from scratch.

Auth flow

The normal integration path is short and reviewable.

1Create a login app

Choose a name, environment, allowed return URLs, and the sign-in methods you want to support.

2Send users to Atom9

Use hosted login or the SDK flow. The user signs in, chooses the right workspace if needed, and returns to your app.

3Verify the session

Your server validates the session and reads the user, workspace, roles, and permissions your app needs.

4Invite contacts when needed

Contacts can stay contacts. Invite them only when they need login access to your product.

SDKs

SDK packages will live here as the public developer surface is finalized.

JavaScript SDK

Browser sign-in helpers, hosted login redirects, and session reads.

React helpers

Components and hooks for sign-in state, user menu, and protected screens.

Server SDK

Session verification, user lookup, workspace context, and webhook handling.

Events and webhooks

React to login, invite, role, and account lifecycle events.

// SDK shape, not a secret-bearing config.
const atom9 = createAtom9Auth({
  appSlug: "your-login-app",
  returnTo: "https://your-app.example/auth/callback"
});

await atom9.signIn();
const session = await atom9.getSession();
What to model

Keep your app model simple.

  • UserThe person who can sign in.
  • WorkspaceThe company, team, or project space they can access.
  • ContactA person in the network or CRM area who may never need login.
  • RoleWhat the user can do inside the workspace.
  • Login appThe auth configuration for one product or environment.
  • SessionThe verified sign-in state your app trusts.