Organization Console

Admins manage the organization in Console after switching the workspace to that Organisation. Members never use this surface. They use the organization login.

Open it

1. Sign in on LoginSign and open /console.
2. Use the workspace menu at the top of the sidebar.
3. Pick the Organisation, or create one with New → Organisation.

The owner and every user with the Admin, Developer, or Accounting role see that workspace. Other members do not. Older /portal links redirect to Console. Internal APIs stay under/api/developer/teamspaces/… and require the admin session cookie.

Menus

Filtered by role and by the live plan:

• Owner — every menu, plus plan and billing actions.
• Admin — Overview, Users, Roles, Blueprint, Settings (can see the current plan).
• Developer — Overview, Applications, Assignments, Sessions, On-premise, Settings (branding).
• Accounting — Overview, current plan, and invoices.

Always available on a live plan when the role allows it:

• Overview — member counts.
• Users — allow-list, roles, Windows username, authentication code.
• Roles — permission groups.
• Blueprint — shared collection.
• Settings — name, logo, domain, login methods.

Enterprise only (Developer, Admin, or Owner):

• Applications, Assignments, Sessions
• Internal studio under /console/apps
• On-premise

Company unlocks the custom-domain card in Settings. Team shows the card as locked. The Apps Console article (OAuth, licenses) is Console.

What Console writes

• Members, roles, settings, billing, SSO apps, and on-premise config.
• The shared Blueprint only from /console/organization.

Edits on /org/:slug write that member's overlay only, including when the person is an admin.