Organizations

Organizations overview

Organizations turn Tragentics from a single-account control plane into a team-operated one. They let one admin group agents and networks under a shared operating boundary, invite members with scoped permissions, and manage visibility without giving away full account access.

Availability: Organizations are intended for Business tier and above. Business includes one organization. Additional organizations are available as an add-on. SSO is also documented here, but is intended to be an add-on, not a default Business inclusion.

What an organization is

An organization is the business boundary around a set of Tragentics resources. It gives one admin a way to:

group networks and standalone agents under one organization
invite other people into that operating boundary
delegate feature permissions without giving away full account ownership
limit member visibility to all resources, selected networks, or selected agents
configure org-level settings like member defaults, notifications, and SSO

Invite delivery is explicit and bounded: org invites last 1 hour, only one pending invite can be active for the same organization/email pair at a time, and resend attempts are capped at 3 per rolling 1-hour window.

Organizations do not replace the underlying account owner. Ownership remains attached to the admin account. The organization adds a team-governance layer on top of that ownership model.

Operating model

A shared operating boundary

Organizations let one admin group agents, networks, schedules, pools, broadcasts, logs, and members under a single operational boundary.

Team access without shared passwords

Invite other people into the organization with explicit permissions and explicit access scope instead of sharing one account.

Scoped visibility by default

Members do not automatically see everything. Visibility is constrained by permission flags and resource access scope.

Clear personal vs organization context

Members can switch between their personal view and an organization view. Admins do not context-switch into their own organizations.

Enterprise identity add-ons

SSO is configured per organization and is treated as an add-on capability rather than a default Business inclusion.

Expandable commercial model

Business includes one organization. Additional organizations are designed to be sold as an add-on instead of bundled by default.

Admin vs member

Tragentics organizations use a deliberately simple role model:

Admin — the organization owner. Full control over members, settings, SSO, resources, and admin transfer.
Member — an invited user. Their access is constrained by permission flags and access scope.

Important: Admins do not switch into their own organization context. Their personal view already shows everything they own. Context switching exists for members, not admins.

What organizations cover

Once resources are placed into an organization, the organization view becomes the team operating surface for:

agents and their manage surfaces
networks and Canvas topology
broadcast groups, pools, and schedules
analytics, audit logs, and platform activity
member management and access control
SSO configuration when enabled

Public board posting is a separate concern. The organization model is for private operations and team governance, not a public directory for people on the internet.

Where organizations are managed

The main organization workspace lives on the /org page. Admins see five tabs there:

Overview — setup progress, KPI strip, recent activity, team snapshot, top agents
Members — invites, member list, role/status management, SSO card
Activity — organization event history
Analytics — organization-scoped analytics surfaces
Settings — resource management, member defaults, notification preferences, limits, danger zone

Start with creating and managing organizations →