Access and approvals
Separate connection approval, shared information access, and permission to change resources in each product.
Connection approval authorizes selected information exchange between products. Your product role and resource scope still determine which shared records you can read and which product actions you can request.
Administrative authority
Each administrator approves the participation of the product they administer. An Infra Organization Admin approves Infra scope. A Guard Administrator approves Guard scope within their permitted asset groups. Organization-wide scope needs organization-wide authority in that product.
General Console administration does not replace product authority. An operator who maintains a self-hosted installation also needs product membership to read organization data or approve a connection.
Connector roles for customer integrations
Connector roles govern API registrations and permitted connection administration:
| Role | Authority |
|---|---|
| Connector Administrator | Manage registrations, connection settings, and custom endpoint approvals |
| Integration Developer | Manage assigned integrations and explicitly allowed connections |
| Connector Viewer | Read explicitly allowed connections and shared resources |
Service-account keys narrow those roles through scopes and explicit connection and integration bindings. A native product administrator still approves the native side of a custom connection. Connector roles do not replace Infra or Guard permissions for native operations.
For a worker identity, follow Create Connector API credentials.
Effective scope
A shared record must satisfy both the source grant and the receiving scope. The receiving product then applies the reader's permissions. A project or group outside the approved grant contributes no records through that direction.
The following boundaries govern separate decisions:
| Decision | Authority |
|---|---|
| Share Infra inventory | Infra grant and selected projects |
| Receive inventory in Guard | Approved Guard asset groups |
| Share Guard security summaries | Guard grant and selected mapped assets |
| Read received security context | Infra role and project scope |
| Request containment | Guard response permission and approval rules |
| Change a droplet or load balancer | Infra resource permission and operation admission |
Read access to a shared finding does not include raw evidence or the right to approve a response. Follow the source record to use the source product's authorized investigation or response workflow.
Grant revisions and approval
Each saved grant revision records its scope and approvers. Editing a pending request invalidates approvals for the earlier selection. Scope expansion enters Pending approval; the existing active grant remains the exchange boundary until the replacement is approved and activated.
Narrowing a grant blocks subsequent exchanges outside the reduced scope. Records already received retain the destination's access and retention rules. Removing a category from a grant does not recall prior copies.
Audit correlation
Connector activity records the actor, connection ID, grant revision, resource references, and outcome. Product audit records describe the product operation and its executor result. Both references are needed to trace an information exchange that led to a separate operational decision.
The connection maintenance guide identifies the audit entry points. Product access rules remain defined by Infra roles and Guard identity and access.