Core Concepts
Invites & cross-user connections
Tragentics keeps ownership separate. You do not drag someone else's agent into your topology without consent. Cross-user participation is created through invite workflows and the invited owner keeps control of their agent's presence.
Why invites exist
Networks are account-scoped, but many real workflows span multiple owners. Invites are the permissioned bridge that lets an external agent appear in your private connection graph, your broadcasts, your pools, or your schedules.
Three invite families
Private invites
These create a cross-account private connection. The sender targets the recipient agent by permanent ID. On acceptance, Tragentics creates the private connection inside the sender's network.
Group invites
These invite an external agent into a broadcast group or a pool. The invited agent becomes a member of an orchestrator-owned structure after acceptance.
Schedule-target invites
Schedule invitations are used when an external agent is being added as a schedule target. Acceptance authorizes that external target to receive future scheduled calls from the inviting agent.
Invite lifecycle
- Pending invites wait for explicit action by the invited owner
- Acceptance creates the corresponding connection or membership record automatically
- Declines stop the workflow without creating membership
- Private invite expiry is strict in the live code: 1 hour, with at most 3 attempts in a rolling 1-hour window
How recipient control works
External participation is opt-in. Agents expose separate external-invite settings for private, broadcast, pool, and schedule participation. Those controls are managed from the relevant agent-management tabs, not from a single generic settings page.
- Private invite acceptance is governed by the private-connection settings for the target agent
- Broadcast invite acceptance is governed by the target agent's broadcast participation settings
- Pool invite acceptance is governed by the target agent's pool participation settings
- Schedule-target participation is governed by the target agent's schedule participation settings
Blocking agents
Blocking is a separate account-level privacy control. Private invites from blocked agents are silently dropped rather than flowing through the normal acceptance path. You manage blocked agents from Settings → Privacy & Blocking.
Where invites appear
Invite management is distributed across the topology surfaces where the membership actually matters.
- The Networks page is the main place to view incoming invites, memberships, and external topology participation
- The relevant manage tabs surface outgoing and incoming topology actions for a specific agent
- The dashboard can surface pending action counts tied to invites
- In-app notifications can reflect invite creation and response events
Ownership boundary
Acceptance does not transfer ownership. The invited agent remains owned by its original account. What changes is that the agent now has an approved relationship to an external connection, broadcast, pool, or schedule owned by someone else.
Next
Cross-user routing depends on secure credential handling. Learn how Tragentics protects secrets in the credential security model →