Members and roles
Inviting people by email or join code, what each role may do, and the roster, profiles and activity behind a vault.
A synced vault is an organization on the server, and the people in it are its members. Vault Settings, Members and access is where they are invited, promoted and removed.
Roles
| Role | What it may do |
|---|---|
| Owner | Everything, including deleting the vault, billing, and resetting anyone's access |
| Admin | Manage members and access, and the vault's own settings. May reset a plain member or themselves |
| Member | Read and write what they have been given, and read the roster. Vault settings are read-only |
Inviting people
- By email. Invite people takes addresses as chips, with a role and an access level for the invitation, and sends each person a pending invitation.
- By join code. A code can be redeemed by anyone you give it to, which is the path when the server has no email transport configured.
If a self-hosted server has no outbound email set up, invitations are shared as a link instead of being mailed, and password reset and sign-up verification are not offered.
The roster
The members table lists each person with their role, their access level and when they were last active, which is stamped at most every ten minutes. Each row also records who invited them, taken from the latest accepted invitation for that address. The owner and anyone who joined by code have none.
A person's profile
Opening a member gives three tabs inside Vault Settings, with a back link to the roster.
Personal info- Name, email, role, when they joined and who invited them, last active, and whether they are online or away, taken from vault presence.
Access- That person's access, as a checkbox tree or as a three-column board. This is where per-folder grants are given and taken away.
Activity- Their recent events: joining, notes created, notes edited collapsed to one per note per day, and access they were granted.
Removing someone
Remove from vault ends their membership. Their readable set empties at once rather than waiting for a token to expire, every document they held is disconnected, and their local copies of what they lost are moved to that device's trash rather than left behind as a readable copy.
This page is written from docs/specs/04-team-collaboration.md and CHANGELOG.md in the repository. Those documents go further, and they are the ones that change first.
Read it on GitHubWas this page helpful?