Use
Accounts and roles
Invite-only sign-in, the four roles, removing access and resetting passwords.
Invitations
Sign-in runs inside the API, with accounts stored in your own database. There is no public sign-up: an admin invites people by email with a role, and only invited addresses can create an account. People sign in with an email and password, or with Google, Microsoft or GitHub once you configure them.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including managing other owners. There is always at least one. |
| Admin | Invite people, change roles (except owner), deactivate and reactivate members, and create password-reset links for members and guests. |
| Member | Create and edit tasks, projects, docs and meetings. |
| Guest | Read only, for outside collaborators. Guests can't see teammates' email addresses. |
A role is the most a person can do. Module access then sets which parts of the workspace each person can use.
Removing access
Deactivate signs the person out of every device at once, blocks sign-in and stops syncing their calendar. Their work stays attributed to them, and you can reactivate them later. Their API tokens stop working while they have no active membership.
Forgotten passwords
An admin chooses Password reset link on the member's row. The link is emailed if email is set up, and always shown with a QR code. With email set up, people can also use Forgot password? themselves.
BETTER_AUTH_SECRET encrypts sessions and calendar tokens, so back it up.