Create the organization under a verified Obelisk identity.
One login, many organizations, many sites
Your single passkey-first Obelisk identity is the root. From it you can create or join many organizations, and each organization can hold many projects and websites — so one person can run an entire portfolio of teams and sites without a second password anywhere. Switch organizations without signing in again: every organization you belong to opens under the same session.
| Layer | What it is |
|---|---|
| Identity | One passkey-first account — the root of everything below |
| Organization | A team boundary you own or join, with owner / admin / member roles |
| Projects & sites | The apps and websites an organization registers — each earns its own Obelisk Rating |
Manage many orgs, each with many sites, under one login. A studio, an agency, or a parent company can hold every team it operates as separate organizations, keep their members and posture walled off from one another by tenant isolation, and still administer them all from the same account.
Register apps (by request today)
Client ID Metadata Documents: Obelisk resolves an https client_id Metadata Document (CIMD) at authorize time, SSRF-guarded, so the document stands in for a registration record — but not for the redirect check: the client's redirect origin must still be on the Gate's return-origin allowlist (the origins of registered relying parties, plus any the operator lists). App registration on request: self-serve registration is switched off on this Gate right now, so the account portal manages apps but does not mint new ones. Request an app registration with your app's name, its exact redirect URIs and the protected resource URLs it calls. The full flow and token verification live in the developer guide.
Anonymous OIDC Dynamic Client Registration (RFC 7591) is operator-gated and enabled per deployment (switched off here). Rolling out: per-organization SSO policy is switched on organization by organization; where a piece isn't yet enabled for you, talk to us.
How an organization matures — preview
Move the slider to see which evidence exists at each stage. This is an onboarding preview—not your live Obelisk Rating.
Issue role-scoped, revocable invitations with a receipt trail.
Attach a website and turn concrete controls into an Obelisk Rating.
Re-scan after changes and compare evidence, not optimism.
Roles are capabilities, not labels
| Role | Boundary | Proof |
|---|---|---|
| Owner | Organization lifecycle, invitations, and scans | Session + owner authorization + mutation receipt |
| Admin | Team operations delegated by the owner | Role-scoped membership and receipt history |
| Member | Read and participate inside the organization | Accepted, non-revoked invitation chain |
A Rating with levers
The organization scan evaluates observable public controls and returns concrete levers. It does not certify private systems it cannot measure, and missing evidence never reads as green.
Human + agent parity. Humans use the organization dashboard; agents discover the same endpoint/auth contract through /api?format=json.
Start with one passkey
Create or sign in to your Obelisk account
After sign-in, create the organization from your account hub. See pricing. Need an architecture review first? Talk to us.
Building on top of it? Integrate Obelisk with the official SDK, connect agents through MCP authorization, or read the whole surface in the API reference.