Mission SDKOrganizations, Groups, and teams

Organizations, Groups, and teams

Select the Mission ownership and access scope for an integration.

Select the owning organization, then the Group and team when your data needs them. A Mission Group organizes a module's teams under an optional immutable access policy. A team carries assignments and team-write authority.

Model the scope explicitly

ObjectSDK accessIntegration use
Organizationatlas.app().orgs()Membership, organization identity, and administrative operations
Groupatlas.app().task_groups()Module selection, Group policy, subordinate teams, and Group roles
Teamatlas.app().teams()Team roster, entity assignments, and team authority
Entity placementatlas.app().entities()Resolve the entity's organization and owning team before writes

A Mission Group is not the generic Platform group primitive. A Group identifier, policy identifier, and team identifier are not interchangeable strings, even where a binding represents them as strings.

Protected Group access

A protected Group binds to one immutable policy. Each protected team binds before its name or content is published.

  • Organization administrators can read and manage the organization's policies.
  • Group Members hold policy read access across subordinate teams and cache data, including attachments.
  • Group read does not grant team-write authority.
  • Group Leads inherit team-lead authority for every team in that Group.
  • Direct team authority for protected data also requires access to its Group policy.
  • Organization membership alone does not expose protected Group data.

The application displays Group Lead as Group Leader. Only an organization administrator assigns that role. A Group Lead can create a new protected team in its Group and add eligible Members to that Group. It cannot promote another Group Lead or manage a different Group.

Demoting a Group Lead to Member retains read access but removes inherited lead authority. A deleted Group retires its policy-derived authority. Do not use a stale Group roster as proof of access.

Data without a Group policy

Organization members can read unprotected organization data across teams, including entities, entity events, reports, and aggregates. Team assignment restricts writes, not those reads.

Cache Management also applies an application display scope to unprotected sites and inventory. Administrators see all. Team members and Team Leads see their teams' sites and related inventory. This display filter is not a general SDK authorization boundary.

Protected Groups enforce native authorization, not a display filter. Distinguish a missing card in the module's current view from a denied SDK read.

Place entities atomically

When creation includes ontology, team ownership, or a containing site, use create_entity_with_placement with CreateEntityWithPlacementParams. Keep the entity and placement in the same checked operation.

A location identifier links an asset to its containing site. A team identifier assigns ownership. Ontology can carry module metadata such as team_id, but metadata alone does not replace the signed team assignment.

On protected data, the SDK resolves the team's policy and checks current authority. A failed assignment lookup rejects the operation. It never silently converts a protected write into an organization-wide write.

Manage membership safely

Use native methods and their typed results for organization and team changes. Paginated roster methods return items and next_cursor. Continue until next_cursor is absent when you need a complete roster.

Organization administrator changes require a fresh complete pull from an authorized Gateway Fabric peer and the local sole-administrator check. These actions require connectivity. Ordinary entity writes do not inherit that requirement. Direct peer data exchange does not make every administrative action offline-capable.

Group removal can return an incomplete outcome when the remover cannot establish that every relevant admission was considered. Present that outcome, rather than claiming all peers immediately removed access.

Entity placement defines ownership and containment.