Organizations And Seats

Organizations represent companies. They centralize identity, seats, licensing, policy, and SSO while allowing optional Teams and a My workspace for every member.

Open organizations at https://your-deployment.example/app/governance/overview.

What an organization gives you

• A My workspace for each member, governed by the Organization.
• Optional Team workspaces for shared agents.
• Member roles and seat management.
• Company license and seat management.
• Shared inference usage and usage reporting.
• Organization-scoped MCP servers and secrets where available.
• Team-scoped integrations and secrets without exposing them to other Teams.

Common roles

Use Roles And Permissions to choose among the Organization roles, including delegated identity, security, agent, audit, and licensing responsibilities.

Organization Owners, Admins, and Agent Admins can administer Teams and Organization-governed agents. Other members need explicit Team or resource access. A member's My workspace is subject to company oversight.

Agent naming

Open Governance → Policies → Agent creation and find Agent naming beside Member agent creation. Owners, Admins, and Agent Admins can change this setting; saving may require recent authentication.

• Generate random names is the default. Leave the name blank to generate one, or enter a custom name.
• Require a name makes the name mandatory before creating an agent. Use a functional name such as Finance Review if it helps people understand the responsibility.

The setting covers every new agent in the Organization's member and Team workspaces, including template launches, API/MCP calls, and agent tools. Specialist approvals ask for the name before Create; Decline needs no name. Imports use the name confirmed during selection. Names may contain spaces, must fit within 255 characters, and must satisfy the destination workspace's existing uniqueness rules.

Existing agents, restored agents, and agents moved into the Organization keep their names. If the setting changes while someone is creating an agent, the form preserves the draft and asks for a name before retrying. Changes appear in the Organization security audit log.

Joining an organization

Public registration is closed by default. Open the invitation sent by your organization or use Company SSO. If you have neither, contact your administrator.

A new invitee can create a password account when the installation permits password sign-in and the organization does not require SSO. The email is fixed to the invitation and is verified by that emailed link; no second verification message is needed. If an account already uses the address, including a renamed directory login address, sign in with that account instead. The invitation cannot replace an existing password or sign you into someone else's account.

Accepting requires an explicit confirmation. Expired, revoked or already-used invitations require administrator assistance. Required company SSO remains required during provider outages; an invitation does not bypass it or restore a directory-deactivated account. Joining consumes the reserved licensed seat and does not automatically add you to Teams.

Installation administrators may explicitly enable public password or ordinary-social registration in System Settings. These controls are independent of company SSO, SCIM, existing-user login and first-administrator setup. Upgrading through migration 0623 resets both saved public-registration controls to off, including development installations. Database choices take precedence over environment variables; reset the saved choice before using an environment opt-in.

Seats

Every active human member consumes one seat, including Owners and Viewers. Valid pending invitations reserve seats; acceptance consumes that reservation once. Agents, Teams and service credentials do not consume seats. Revoke obsolete invitations to release reservations.

Owners, Admins and License Admins import signed replacements through Governance → License. A smaller seat allowance is accepted without removing members; additions are blocked while over capacity. The initial Owner can set up an unlicensed Organization, but execution and further seat reservations require a valid license.

Before adding seats, decide:

• Who needs full organization membership.
• Who only needs collaborator access to one agent.
• Which work belongs in a Team rather than in a member's My workspace.

Create and assign Teams

Teams are optional and belong to exactly one Organization. Do not create a placeholder General Team just to give members somewhere to work; their My workspace already serves that purpose. Create Teams for work that should be shared with a defined group.

Open Governance → Access → Teams, create the named Team, and assign the members and Team roles that should share its work. A Team Admin role does not grant Organization-wide administration. Verify the new Team in the workspace selector before creating or moving agents into it.

When reassigning an agent, check:

• Who is accountable for the agent and its usage.
• Which collaborators still need access.
• Whether secrets, contacts, MCP servers, and app connections still apply.
• Whether the agent's charter references personal context that should be removed.

Workspace Pets

Organization Owners and Admins can open Settings → General → Pets and turn Enable Pets on or off. Pets are disabled by default. This setting applies to every member and Team workspace in the Organization.

Your personal pet display also defaults to off. When your workspace allows Pets, you can enable your companion in your profile. Existing saved display preferences are preserved.

Disabling Pets hides workspace companions and their controls. Saved pets and personal preferences are preserved, and nothing else in the Organization changes. When Pets are enabled again, each member's saved preference determines whether their companion appears. An open session picks up another administrator's change when the user returns to the tab or reloads it.

License and usage

Organization usage appears in the Usage area for users with permission. Licensing is in Governance → License.

See License and Usage.