Organizations

Creating and managing organizations

Organization creation is not just a name field. It is the moment you define the first resource boundary for a team: which networks move in, which standalone agents move in, and whether those resources can safely coexist inside one organization.

Business includes one organization by default. Additional organizations are intended to be purchased as an add-on once tier gating is activated.

The create flow

If you do not yet admin an organization, the /org page renders the create view. That screen lets you:

set the organization name
select personal networks to include
select standalone personal agents to include
review a summary of what will move under the organization
acknowledge the organization terms before submitting

Name the organization

Choose the organization name. Tragentics generates a slug from that name for internal identification.

Select networks

Choose which personal networks should move into the organization. Tragentics shows agent counts per network before you commit.

Select standalone agents

Add personal agents that are not currently tied to any network so they become part of the organization boundary too.

Run preflight checks

Before creation, Tragentics checks for fallback-scope conflicts and public-board isolation blockers so the org starts in a valid state.

Create the organization

The create flow performs the org, admin membership, access defaults, and initial resource stamping atomically.

What gets created

On success, Tragentics creates the organization and its initial admin structure in one atomic operation. That create action establishes:

the organization row itself
the admin membership row for the creator
the admin's default access scope for that organization
the initial resource stamping on selected networks and agents
organization stamping for related guardrail resources like outside caller blocks

Ownership does not transfer. The admin account still owns the resources. The organization adds a team governance boundary on top of them.

Preflight guardrails

Before resources are stamped into an organization, Tragentics runs preflight checks to prevent invalid states.

Fallback scope conflicts

If an agent's fallback relationship would become invalid after the move, the create flow opens a reconciliation dialog instead of writing partial state. You resolve the mismatch before the organization is created.

Public board isolation

Organization resources cannot be mixed with public-board topology in unsupported ways. If the selected resources include a board agent or an in-scope connection path to one, the flow blocks and shows which public agent is causing the conflict.

Public discovery and private organization operations are intentionally separated. If a resource is currently entangled with the public board in a way that violates organization isolation, you must resolve that board relationship first.

Managing resources later

After the organization exists, the Settings tab becomes the long-term resource management surface. From there, the admin can:

rename the organization
add more personal networks to the organization
remove organization networks back to personal context
add standalone agents to the organization
review org-scoped counts and limits

Removing a network or agent from an organization does not delete it. It returns the resource to the owner's personal context, subject to the same fallback and isolation rules that protect creation.

Deleting an organization

Deleting an organization clears active member context, removes organization membership structures, and clearsorg_id from organization-managed resources.

members are removed from the organization
member context is cleared first so users are not left in a dead org context
organization rows for invites and access records are cascaded away
resources are returned to personal ownership context instead of being deleted outright

Deletion is an administrative destruction of the team boundary. It is not a “soft hide” action. Treat it like an operational teardown, not a casual cleanup button.

After the organization exists, the next layer is team governance: members and roles →