Administration
Administration is for the people and automation that configure an Axec Account, rather than the Applications that execute tools. Operators manage the Account as administrators or read its management projections as viewers, while Service Accounts perform explicitly permitted management tasks. Neither kind of management access lets a caller borrow a User’s Connection or act through that User’s consent.
Account access
Section titled “Account access”Operator SSO connects management sign-in to your organization’s identity provider. It is configured independently from User sign-in, and the identity provider’s application assignments determine who can enter the Account as a Viewer. An administrator controls subsequent role changes; directory groups and identity-provider claims do not assign management roles.
For pipelines and scripts, Service Accounts provide named credentials and explicit permissions without a human session. Start with management automation for a bounded inventory task, then use the management SDK reference for the TypeScript and Python interfaces. An agent that calls tools should instead use an Application and one of the runtime Guides.
Management boundaries
Section titled “Management boundaries”Management views and personal activity have different visibility boundaries, so read access to Account-wide evidence must not be confused with permission to use a User’s upstream account. Security Architecture explains the separation between management and execution authority, credential custody, and the limits of retained evidence.