Skip to content

Members and invitations

Members are managed at Administration → Members (/admin/members).

Invite by email address, choosing the role they should hold. Aletheia produces a single-use invitation link.

An invitation:

  • Is single-use. Accepting it consumes it.
  • Expires. An expired invitation cannot be accepted; issue a new one.
  • Can be revoked before it is accepted.
  • Carries the role you chose, so the person lands with the right access rather than being fixed up afterwards.

Accepting an invitation creates the person’s account and adds them to your organization in one step. They set their own password; nobody else ever sees it.

The members screen lists invitations that have not been accepted, with who sent each one and when it expires. Revoke any of them from there.

A member’s roles can be changed at any time. The change takes effect on their next request — there is no re-login and no cache to wait out.

A member can hold more than one role, and the effective permission set is the union. See Roles and permissions.

Members are deactivated, not deleted. A deactivated member:

  • Cannot sign in, and their existing sessions stop working.
  • Still appears in the audit log, on the changes they made, and wherever they are recorded as an owner.
  • Can be reactivated later, keeping their identity and history.

This is deliberate. Deleting the account would either destroy the record of what that person did or leave dangling references to a user that no longer exists. Neither is acceptable in a system whose main job is telling you who changed what.

For the same reason, offboarding someone is one action: deactivate them, and every credential they held stops working at once.

The organization must keep at least one active platform administrator. Removing the last one is refused with last_admin rather than leaving an organization nobody can administer.

Promote someone first, then deactivate.