Identity and Mission admission
Bind an integration to an account and obtain scoped Mission authority.
Admit the integration's account to the organization, bind its device identity, and obtain authority for each data path. The verified device signs for the account. Membership alone does not authorize every Mission operation.
Platform identity and authorization defines key, signature, and capability verification.
Keep identities distinct
| Identity or evidence | Meaning | Not a substitute for |
|---|---|---|
| Account identity | Durable owner of devices and membership | The current device signing key |
| Device identity | Verified signer bound to the account | Organization or Group permission |
| Organization identity | Authority root and data context | A secret token |
| Display role or roster row | Human-readable membership projection | A current authorization decision |
| Gateway Fabric identity | Approved persistent service peer with organization gateway authority | A user administrator or Group Lead |
An organization identifier names a scope. Protect keys, recovery phrases, invite secrets, and authorization tokens as credentials, separately from ordinary identifiers.
Join through the right admission flow
An integration acting as a user uses account device binding and membership. Gateway Fabric uses a provisioned system-node identity and matching organization credentials. Do not provision every unattended sensor adapter as a gateway.
A Group invitation grants basic membership for one immutable Group policy and module. It does not grant Group Lead or team-write authority. Possession of its QR data does not make the QR key a standing principal. A submitted request is not an accepted admission.
The mobile client accepts one effective organization per device. A new Group admission into another organization is refused while foreign membership remains effective. Retained history alone is not current membership.
Gateway Fabric uses separate approval
An authorized administrator approves the durable Gateway Fabric identity through the organization's provisioning process. Directory presence alone is insufficient. The operator installs the identity and matching credential bundle before operational startup.
Gateway Fabric stores and forwards authorized Mission data. Its domain-neutral carriers do not grant Group membership or the Group Lead role. The Gateway Fabric configuration reference defines required startup inputs.
Authorize each data path
OrganizationAccess carries the selected org_id and optional group_id. It identifies the requested scope and associated authority context. It is not self-issued permission.
| Operation | Required decision |
|---|---|
| Save or modify a Track | Entity write in the resolved organization and placement |
Publish TrackDetected | Detection publication in that scope |
Observe TrackDetected | Detection subscription in that scope |
| Resolve its entity | Entity read in that scope |
| Advertise or publish telemetry | Telemetry publication for that entity and producer |
| Open telemetry | Telemetry subscription for that consumer |
Handle denial on each operation. Event access grants neither entity read nor stream access. Never place credentials in an observation or stream descriptor.
Missing evidence and revoked authority
Missing synchronized evidence can leave authorization unresolved. Do not replace it with a roster-derived allow decision. A live application decision fails closed until the required authority is verified.
Revoked or expired authority refuses new protected work and ends further authorized delivery according to the subscription contract. Device revocation retires an account's device globally. Organization device distrust rejects that device's subsequent organization operations. These actions have different scopes and do not imply remote erasure of data a peer already received.
See security and error handling for recovery and secret handling.