Account, Tokens, and Audit Log

Protect access to working data. Give colleagues separate accounts, enable a second factor, and do not give integrations your password.

Keys and tokens

• An export token allows reading selected exports in permitted formats.
• An API key allows management of resources available in the workspace, or read-only access. It is tied to a user, workspace, and expiry.
• An agent token belongs to service infrastructure and does not replace either of the above.

Values are shown only when created. Keep them in secure server-side configuration. Do not include them in page code, URLs, screenshots, shared chats, or a repository. Revoke a lost or exposed key and create another.

Permissions and sessions

Grant colleagues permissions for their tasks. Check both permission for a section and access to a particular site. When an employee leaves, remove their membership and integration access. Review active sessions and the second factor in personal settings.

Audit log

The action log shows who changed settings or started operations. For charges, use the billing log; for collection errors, the run log; for data transfers, delivery history. These sources answer different questions. When requesting help, include an object identifier, time, and error text, but never access secrets.