Documentation

Console

Structure

An organization is one workspace. Console is where admins configure it. Members never open Console. They sign in on the organization login and land on a filtered collection.

Two Console workspaces

The same Console switcher holds App Authentication projects and Organisation workspaces. Pick the organization to see Users, Roles, Blueprint, and Settings. Applications and On-premise appear only on Enterprise.

  • App Authentication — OAuth clients for a website or product. See the Apps articles above.
  • Organisation — a company or school space. The articles under Organizations.

In APIs the organization is still called a Teamspace (/api/developer/teamspaces/:id). The public URL is /org/:slug.

Who is who

  • Owner — created the workspace. Always sees it in the Console switcher. The only person who can change the organization plan or open Stripe billing.
  • Admin — built-in operational role. Opens Console. Changes users, roles, Blueprint, and settings. Can see the current plan. Cannot change billing.
  • Developer — built-in role. Overview plus Applications, Assignments, Sessions, On-premise, and branding settings.
  • Accounting — built-in role. Overview plus the current plan and invoices. Cannot change billing.
  • Member — allow-listed email. Signs in on the organization login. Sees only folders and apps their roles allow, plus their own overlay. Does not open Console.

Adding a person does not create a password. It puts their email on the list. They sign in with the LoginSign methods enabled in Settings. The email must match.

What members see

  1. The server loads the shared Blueprint.
  2. It hides folders, bookmarks, and apps the member's roles do not cover.
  3. Assigned SSO applications are added as collection tiles (sso_…).
  4. That person's overlay is merged: renames, icons, personal folders, wallpaper.

Search, share, and the consume API never see hidden Blueprint items. Personal folders can sit inside a Blueprint folder. If Admin deletes that folder, personal children move up. Overlay rules: Personal overlay.

Permissions in one sentence

Roles are groups. Assign them to people and to Blueprint items. No role on an item means every active member can see it. Multiple roles on an item means the member needs at least one of them. A hidden folder hides everything inside it.

Admin is not a visibility filter. Admins see everything. Details: Roles and visibility.

Plans gate the menus

  • Team — people, roles, Blueprint, settings.
  • Company — plus custom domain and role governance.
  • Enterprise — plus applications, assignments, sessions, internal apps, and on-premise.

Without the matching live plan those Console pages are hidden and the APIs return403 PLAN_REQUIRED. After expiry or too many seats, login and Console stay locked until the owner renews or upgrades.