Users and permissions
You can invite users to your company and decide what they reach. Permission is not a UI checkbox: what you did not assign, that user cannot decrypt.
Inviting
The invitation goes out by email with a single-use link. Whoever accepts it sets their own password, which never passes through you or the server.
How many users you get depends on the plan. On individual plans, users and logins are the same number.
Permissions by folder or by server
They are edited from both sides: from the user, choosing what they reach, or from the folder or server, choosing who reaches it. Same information, two views.
Permissions inherit like everything else: what you grant on a folder reaches what is inside, and the most specific wins.
Why hiding the button is not enough
Each user has their own key pair, generated in their browser. A folder key is wrapped once for every user with access. If someone stole the entire database, they still could not open what was never assigned to that user.
Removing someone
Revoking their access also cuts whatever they have open at that moment: consoles, file explorers and Ansible runs are closed, not left alive until they time out.
