Administration

Everything in Aletheia belongs to exactly one organization. That boundary is enforced on every query, so no data is ever visible across organizations.

Members and roles

You invite people by email. An invitation is a single-use link that adds the person to your organization when accepted.

Each member holds a role, and the role determines what they can read and change. Permissions cover reading resources, managing integrations, managing applications and ownership, managing members, reading the audit log, and triggering work.

Members can be deactivated rather than deleted, which preserves the audit history of what they did. A deactivated member can be reactivated later.

The audit log

Mutating actions are recorded in an audit log, written in the same transaction as the change itself. Each entry records who acted, what they did, and when.

In this section

• Organization settings — what an organization is and the boundary it enforces.
• Roles and permissions — what each role grants.
• Members and invitations — adding people and offboarding them.
• Audit log — who did what, and why it cannot be rewritten.

Where to go next

• CI integration for ingest tokens, which are managed here too.