Project roles: owner, editor, viewer, follower

Everyone in a project has a role, and the role decides what they may do there. Owner. The person who created the project. There is exactly one, and the role cannot be handed out — you get it by creating the project. Only the owner can delete the project, manage its members (invite, remove, and change a member's role) and change its access level (Members only, Private or Public). In a company project the company owner can do all of that as well, even if they are not a member of that project, so a workspace never gets stuck when a project's owner leaves the team. If the owner is removed from the company or deletes their account, their company projects pass to the company owner automatically. Editor. Full read and write access to the project's content: create, edit, archive, delete and restore memos, manage tags, upload and remove files, rename the project. In a private project, editors can also invite followers by email and revoke invitations that have not been accepted yet. Editors cannot delete the project, change its access level or change who its members are. This is the default role — most collaborators are editors. Viewer. Read-only. Can search and read the project's memos, open their history, see who else is in the project and download attachments, but cannot create, edit or delete anything — not memos, not tags, not files — and cannot share or unshare a memo. Useful for people who should consume the project's knowledge without changing it: a documentation or reference project, a stakeholder who only reads, an AI client you want to keep from writing. Viewers exist in company projects only, and a viewer is a member of the company, so they take a seat. Follower. A reader from outside the project's team. There are two ways to become one: joining a public project through its link, or accepting an email invitation to a private company project. Followers search and read the project's memos and download attachments, from the web and from their own AI client, but they change nothing, and they see less than a viewer: not the member list, not a memo's change history, not deleted memos, and not the project's instructions. A follower takes no seat. You cannot give a follower a role. On a public project followers cannot be removed one at a time (switching the project to Members only removes all of them); on a private project the owner can remove any follower. See "Followers: what they can and cannot do". How to invite a member. Open the project, press "Invite member", find the person, then pick Editor or Viewer before confirming. Editor is preselected. The role applies immediately. How to invite a follower. The project has to be a company project set to Private. Then press "Invite follower" and enter the person's email; they get an invitation to accept. See "Private projects: invite readers from outside your team". How to change a role. Open the project, press "Edit" on the member's card, pick Editor or Viewer, and save. The change applies immediately, everywhere — the web app and every connected AI client. Two exceptions: the owner's role cannot be changed (there is no way to hand the project to someone else), and a follower's cannot either. Who can be invited. In a company project, only people who are already members of the company can become editors or viewers — add them to the team first. People outside the company can follow a private company project by email invitation instead. In a personal project, only your designated family guest (Max plan), and they are always an editor — there is no role to choose. The roles apply everywhere the project is reachable — the web app and any AI client connected over MCP. A read-only member's AI client can read the project's memories, but any attempt to write, delete or share is refused.