Organization roles
There are two roles: Admin and Member.Admins can see every project so that work is never stranded when someone is away. Admins cannot see a member’s personal vault or private conversations with the agent.
Projects
A project groups the vault, matters and conversations for one piece of business: a transaction, a client, a development.
Within a project, the owner manages its settings and members, and members work in it.
Everything in a project inherits its access: its vault, its matters, and the conversations shared in it. A conversation from a private project that is linked to a matter stays hidden from anyone who cannot see that project. They are told only how many linked conversations they cannot see.
Shared Spaces
Shared Spaces have their own, finer-grained model, because they include people outside your organization: buyers, sellers, the other side’s lawyer, the notary, the bank.- People are invited to a space individually, and can be grouped into teams.
- Access is granted per document type and per summary category, as viewer or editor. A person sees only the document types and summary categories they have been given.
- Document types can have owners, responsible for providing them, and reviewers, responsible for approving them.
The agent
The agent has no role of its own. In any conversation it acts as the person who started it, with that person’s organization role, project memberships and Shared Space permissions. Asking the agent cannot get around a restriction that applies to you. See Access control.Good practice
- Keep at least two admins, and no more than you need.
- Use private projects for matters that should be seen by a small team.
- Review members each quarter. Remove people who have left, and check pending invitations.
- Ask everyone to enable two-factor authentication.