Administration

Organization and people

• The owner is the person whose email the organization was created for. The first sign-in makes them an administrator; other people are invited by them or by the administrators they appoint.
• Invitations arrive as a link by email and expire; there is no open registration.
• The organization’s region is chosen at creation and never changes: data never leaves the US or RU.

Access keys

For scripts and external systems: access keys (PAT) in the API Keys section, the Access field:

• read: reads; any write request gets 403;
• read, write: full access of the key owner.

The key is shown once when issued. The list and revocation are in the same place. With a key you can export or import the company package and work with the API (reference pages are in Russian).

Agent keys

• A node’s enrollment key is one-time, from the Nodes card; after enrollment the agent keeps a permanent key.
• Agent tokens in chat are stored as hashes; administration shows the first characters, New token and Revoke issue a new one or revoke the current one, and the old one stops working at once.
• Model and channel keys are kept encrypted by the agent; they never reach the cloud.

Audit and runs

The run of every task, what it was started with, what the agent asked the model and what it answered, is visible on the task with keys and tokens masked. Approvals keep who approved or rejected and when. Audit export per organization is in the Business edition.

Snapshots and updates

In the cloud, data snapshots and platform updates are our job. Your export is the company package: roles, scenarios and skills in one file you can keep in git and load into another organization. Agent settings and roles are versioned and rolled back from the panels (see Workforce and HolyAgent).

Editions

Free: up to 5 people and 2 agents; Team: by subscription with SSO through id.holycode.org; Business: dedicated deployment, login federation with your Zitadel, audit export and SLA. Details on the pricing page.