> For the complete documentation index, see [llms.txt](https://docs.spreo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spreo.io/plans/roles-and-licenses.md). # Roles and Licenses Editor, Collaborator and Visitor, and who needs which license on the Team plan. {% hint style="info" %} This page covers the Team plan. If you're on an older plan, your members and guests work as before. See [Legacy Plans](/plans/legacy-plans.md). {% endhint %} On the Team plan you only license the people who need it. Each person joins with one of three roles. | | Editor | Collaborator | Visitor | | ------------------ | --------------------------------------------------- | ------------------------- | ------------------------------- | | **Billed yearly** | $13 per user / month | $3 per user / month | Free | | **Billed monthly** | $16 per user / month | $4 per user / month | Free | | **Usually** | Facilitators, Scrum Masters, team leads and coaches | Your regular team members | Anyone joining a single session | {% hint style="info" %} A team must have at least one Editor. {% endhint %} ### Editor Editors create boards, run retros, plan sprints and host workshops. Usually facilitators, Scrum Masters, team leads and coaches. ### Collaborator Collaborators are the people you work with every week. They sign in, so your team's boards can stay [protected](/boards/share-your-board.md) instead of open to anyone with the link. Collaborators can: * Sign in with their own identity, including [Single Sign-On](/management/single-sign-on.md). * Open their team's boards and folders without a link or an invite. * Be assigned [actions](/boards/actions.md), get email reminders, and track them on the [Action Items dashboard](/dashboard/action-items.md). * Appear with their team picture in tokens and the [Voter gadget](/boards/the-tools.md). * Get notified when someone [mentions](/boards/mentions.md) them. * Connect their own Atlassian account to the [Jira integration](/boards/jira-integration.md), and connect an AI assistant through the [MCP server](/boards/mcp.md). ### Visitor Visitors join a single session, such as a stakeholder at a review, a client in a workshop or a department at an all-hands. They click the board link and join in their browser, with no account and no sign-in. Visitors are free and unlimited, but they can only join boards that are set to **Open**. See [Share your board](/boards/share-your-board.md) to change a board's sharing settings. ### Collaborator or visitor? Visitors and Collaborators can both add sticky notes, vote, draw and answer polls. The difference is what happens before and after the session. * **Visitors** suit one-off sessions, such as a stakeholder review, a client workshop or an all-hands. The board has to be set to **Open**, so anyone with the link can join. * **Collaborators** suit the people who join every week. Your boards can stay protected, the team finds past boards on its dashboard, and actions go to named people who get reminders. ### What each role can do | | Editor | Collaborator | Visitor | | ------------------------------------------------------------- | :----: | :----------: | :-----: | | Join open boards from a link | ✓ | ✓ | ✓ | | Take full part in the session | ✓ | ✓ | ✓ | | Sign in with their own identity, including SSO | ✓ | ✓ | | | Keep the same profile on every board | ✓ | ✓ | | | Open the team's protected boards straight away | ✓ | ✓ | | | See their team's boards and folders automatically | ✓ | ✓ | | | Be assigned actions, with email reminders | ✓ | ✓ | | | Use the Action Items dashboard | ✓ | ✓ | | | Appear with their team picture in tokens and the Voter gadget | ✓ | ✓ | | | Get notified when mentioned | ✓ | ✓ | | | Connect their own Jira account | ✓ | ✓ | | | Connect an AI assistant through the MCP server | ✓ | ✓ | | | Create boards | ✓ | | | | Host sessions | ✓ | | | ### Inviting people * **Editors and Collaborators:** invite them by email, from the board's Share menu or from your team. Each one uses a license. * **Visitors:** set the board to **Open** and share its link. There's nothing to send by email. You can't invite guests by email on the Team plan. Guests are part of the [Enterprise and Consultant plans](/plans/plans-overview.md). ### How many licenses do I need? * One Editor for each person who creates boards or hosts sessions. * One Collaborator for each regular team member. * Everyone else can join open boards as a visitor, for free. One Editor on their own is enough to get started: they can create boards, run sessions and invite any number of visitors to an open board. ### Example costs With yearly billing: * **Solo facilitator:** 1 Editor and unlimited visitors, $13 a month ($16 billed monthly). * **Product team of 8:** 1 Editor and 7 Collaborators, $34 a month ($44 billed monthly). * **Department of 50:** 5 Editors and 45 Collaborators, $200 a month ($260 billed monthly). * **Company workshop:** 3 Editors and 200 visitors on open boards, $39 a month ($48 billed monthly). ### Changing someone's role You can change a person's role at any time, as long as there are seats available. Adding seats updates your bill pro-rata. See [Billing & Subscription](/management/billing-and-subscription.md). ### Visitors and guests Visitors and guests are different. Visitors can only join **open** boards. On the [Enterprise and Consultant plans](/plans/plans-overview.md), and on every legacy plan except Starter, you can invite people from outside your organization, such as clients, as **guests**, so your boards can stay secure. See [Guests](/boards/share-your-board.md#guests). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spreo.io/plans/roles-and-licenses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.