Roles and working together

Understand what each role in Twin is for, and how your team works on the same project.

The three roles

A member can hold more than one role, for example Project Editor, Project User. Roles are picked when you invite someone and can be changed afterwards from Organization → Members. See Inviting and managing members.

What that means in practice

• Organization Owner is the only role that reaches Your organization, so the firm's details, its memory, the subscription and invoices, the members list, the API keys and the connections are all owner territory. Owners work in projects like everyone else.
• Project Editor is the role for the people doing the work: creating projects and clients, adding sources, and writing and editing documents.
• Project User is the role for people who need to follow the work rather than write it.

Admin is not a role. It is a separate flag on an account, shown as an Admin badge in the members list, and it marks a Twin platform administrator. It is not something you hand out when you invite a colleague.

Working on the same project

Projects are shared inside your organization. Everyone with access opens the same project and the same document, so there is nothing to share and no copy to keep in step. Twin has no per-document sharing and no way to give someone outside your organization access to a single project.

Changes appear live. When two of you have the same document open, each of you sees the other's edits without refreshing, and if the assistant rewrites a section while you are typing in it, Twin keeps your own text and says so on screen.

Comments are how a team stays coordinated: a comment stays tied to the section it is about, and the assistant reads unresolved comments the next time it works on that section. See Giving expert feedback on a section.