Files
upstream-mirror 240db4e2a7
Some checks failed
Server CI / Postgres (shard 0) (push) Has been skipped
Server CI / Postgres (shard 3) (push) Has been skipped
BuildEnv Docker Image / build-image (push) Failing after 4s
BuildEnv Docker Image / build-image-fips (push) Failing after 4s
Migration Review & Release Notes / Generate migration review & release notes (push) Failing after 3s
Server CI / Build Environment (push) Failing after 3s
Server CI / Postgres (shard 1) (push) Has been skipped
Tools CI / check-style (mattermost-govet) (push) Failing after 4s
Server CI / Postgres (shard 2) (push) Has been skipped
Tools CI / check-style (mmgotool) (push) Failing after 3s
Server CI / Elasticsearch v8 Compatibility (push) Has been skipped
Server CI / OpenSearch v2 Compatibility (push) Has been skipped
Server CI / Postgres FIPS (shard 0) (push) Has been skipped
Tools CI / Test (mattermost-govet) (push) Failing after 3s
Server CI / Postgres FIPS (shard 1) (push) Has been skipped
Server CI / Postgres FIPS (shard 2) (push) Has been skipped
Tools CI / Test (mmgotool) (push) Failing after 3s
Server CI / Postgres FIPS (shard 3) (push) Has been skipped
Server CI / Run mmctl tests (push) Has been skipped
Server CI / Run mmctl tests (FIPS) (push) Has been skipped
Server CI / Merge Postgres Test Results (push) Has been skipped
Server CI / Merge Postgres FIPS Test Results (push) Has been skipped
Server CI / Check backport migrations (push) Has been skipped
Server CI / Check generated files (push) Has been skipped
Server CI / check-style (push) Has been skipped
Server CI / Vet API (push) Has been skipped
Server CI / Build mattermost server app (push) Has been skipped
Server CI / Server CI Complete (push) Failing after 2s
Server CI / Server CI Artifacts (push) Has been skipped
Server CI / Sentry Upload (push) Has been skipped
Server CI / Server CI Report (push) Failing after 5m1s
Server CI Nightly Race / Race Detector (push) Has been skipped
CodeQL / Analyze (go) (push) Has been cancelled
CodeQL / Analyze (javascript) (push) Has been cancelled
Webapp CI Cache Warm / Warm Webapp node_modules Cache (push) Has been cancelled
E2E CI Cache Warm / Warm E2E npm Registry Cache (push) Has been cancelled
API / build (push) Has been cancelled
Web App CI / check-types (push) Has been cancelled
Web App CI / check-lint (push) Has been cancelled
Web App CI / check-i18n (push) Has been cancelled
Web App CI / check-external-links (push) Has been cancelled
Web App CI / test (platform) (push) Has been cancelled
Web App CI / test (mattermost-redux) (push) Has been cancelled
Web App CI / test (channels shard 1/4) (push) Has been cancelled
Web App CI / test (channels shard 2/4) (push) Has been cancelled
Web App CI / test (channels shard 3/4) (push) Has been cancelled
Web App CI / test (channels shard 4/4) (push) Has been cancelled
Web App CI / upload-coverage (push) Has been cancelled
Web App CI / build (push) Has been cancelled
YAML Lint / yamllint (push) Has been cancelled
Push mirrored docker images / cd/Push mirrored docker images (push) Has been cancelled
docs-cd / Build and deploy docs (push) Has been cancelled
Docs CI / build (push) Has been cancelled
E2E Cache Warm: Cypress deps / Warm Cypress deps cache (push) Has been cancelled
Scorecards supply-chain security / Scorecard analysis (push) Has been cancelled
Server CI Weekly / Postgres FIPS (push) Has been skipped
Server CI Weekly / Run mmctl tests (FIPS) (push) Has been skipped
Server CI Weekly / Postgres with binary parameters (push) Has been skipped
Server CI Weekly / Build Environment (push) Failing after 1s
Server CI Cache Warm / Warm Go Module and Build Cache (push) Failing after 2s
Server CI Nightly Race / Build Environment (push) Failing after 1s
snapshot of https://github.com/mattermost/mattermost.git (master, 2026-09-16; blobs > 131072B omitted)
2026-09-16 00:29:55 +05:00

197 lines
10 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Share and collaborate on boards"
---
import useBaseUrl from '@docusaurus/useBaseUrl';
<PlanAvailability slug="entry-ent" />
## Board permissions
Boards belong to teams and any member of that team can be granted access to a board.
If your boards workspace looks different, you may be on an earlier version of boards. In earlier versions, boards are tied to channel workspaces and board membership is determined by channel membership. In this case, roles and permissions won't be applicable to you.
## Roles
<table>
<colgroup>
<col style={{width: '32%'}} />
<col style={{width: '17%'}} />
<col style={{width: '17%'}} />
<col style={{width: '17%'}} />
<col style={{width: '17%'}} />
</colgroup>
<thead>
<tr>
<th>Board permissions</th>
<th>Admin</th>
<th>Editor</th>
<th>Commenter</th>
<th>Viewer</th>
</tr>
</thead>
<tbody>
<tr>
<td>Modify permissions</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Share a public board</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Delete board</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Rename board</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Add, edit, and delete views</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Add, edit, and delete cards</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
</tr>
<tr>
<td>Comment, delete my comments</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
</tr>
<tr>
<td>Delete any comment</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td>View</td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
<td><img src={useBaseUrl('/img/ui/checkmark.svg')} alt="Yes" className="theme-icon" /></td>
</tr>
</tbody>
</table>
The level of access to a board is determined by a user’s assigned board role. Individual board membership always gets precedence, followed by highest (most permissive) group role.
- **Admin**: Can modify the board, its contents, and its permissions. By default, board creators are also admins of the board.
- **Editor**: Can modify the board and its contents.
- **Commenter**: Can add comments to cards.
- **Viewer**: Can view the board and its contents but can't comment or edit the board.
### System admin access
System admins can access any board across the server provided they have the board's URL without having to request permission or be manually added. When a system admin joins a board, their default role is admin. System admins will have an **Admin** label assigned to their name on the participants list.
### Team admin access
Team admins can access any board within their team provided they have the board's URL without having to request permission or be manually added. When a system admin joins a board, their default role is admin. Team admins will have a **Team admin** label assigned to their name on the participants list.
### Manage team access
Board admins can manage team access to their board by selecting **Share** in the top-right corner of the board. On the dropdown next to **Everyone at… Team** option, select a minimum board role for everyone on the team. You can also easily assign the new roles to the entire team and/or to individual team members.
Minimum default board roles reduce permission ambiguity and prevent security loopholes. The minimum default role means that board admins can't assign individual board members a role lower than the team role. If the team role is set to **Editor** then the board admin will only be able to assign the **Editor** or **Admin** role to individual team members. Lower roles will not be available for selection unless the admin changes the minimum board role.
Depending on the role selected, everyone on the team will have access to the board with a minimum of the permissions from the role selected. Users can get elevated permissions based on their individual board membership. The default team access for a newly created board is **None**, which means nobody on the team has access to the board.
### Manage individual board membership
Only board admins can manage user permissions on a board, including adding, changing, and removing members.
To add individual users from the team as explicit members of the board, open the **Share** dialog on the board, search for individual team members, then assign a role to set their permissions for the board. The role for individual board members overrides any role specified for team access.
- To change a board member’s role, open the **Share** dialog, select the role dropdown next to the user’s name, then select another role from the list.
- To remove a member from a board, open the **Share** dialog, select the role dropdown next to the user’s name, then select **Remove member**.
Board admins can also add individual members using the autocomplete list from @mentions and the person properties. To add an individual from the autocomplete list, type their username in an @mention or in the **Person** or **Multi-person** properties, then assign a role to the user from the confirmation dialog, and select **Add to board**.
On boards with team access, board members with **Editor** or **Commenter** roles can also add individuals to the board from the autocomplete list. Board members added in this manner will be assigned the default minimum board role.
### Channel role groups
Board admins can add a channel to a board to grant all its members Editor access. To do this, select **Share** in the top-right corner of the board, search for the channel name, and add it to the board as a user. The default role is Editor. Doing so also [links the board back to the channel](/end-user-guide/project-management/navigate-boards#link-a-board-to-a-channel), where the board will appear on the channel RHS.
To unlink the channel from the board, open the **Share** dialog, select the role dropdown next to the channel’s name, then select **Unlink**.
<Note>
A board can only be linked to one channel at a time. Linking another channel to the same board will automatically remove the link from the previous channel.
</Note>
## Guest accounts
From Mattermost Boards v7.4, [guest accounts](/administration-guide/onboard/guest-accounts) are supported in Boards. Guests can:
- Access boards where they're added as an explicit member of the board. [Team access](#manage-team-access) and [channel role groups](#channel-role-groups) don't apply to guest accounts.
- Access existing boards, but not create new boards. Guests don't have access to the template picker and can't duplicate an existing board.
- Search for boards where they're currently an explicit member.
- Be assigned the Viewer, Commenter, or Editor roles, but not the board Admin.
- Only @mention current members on the board.
If you're not able to access this functionality, you may be on an earlier version of Boards.
## Share a board
Boards can be shared internally with your team or published externally with limited accessibility.
### Share a board internally
To share a board with team members internally, select **Share** in the top-right corner of the board, then select **Copy link** from the **Share** tab below. Paste the copied link in a channel or direct message to share the board with other team members. Only team members who have permissions to the board will be able to open the board from the shared link.
### Share a board publicly
Sharing boards publicly is disabled by default. This means that the **Publish** tab is not available from the **Share** dialog. To enable public board sharing:
1. Go to **Product menu \> System Console \> Products \> Boards**.
2. Set **Enable Publicly-Shared Boards** to **true**.
3. Select **Save**.
Once enabled, board admins can share a read-only link online with anyone:
1. Select **Share** in the top-right corner of the board.
2. Toggle to the **Publish** tab.
3. Switch to the **Publish to the web** option.
4. Select **Copy link**.
Paste the link anywhere you want to share the board. Anyone with the link will be able to view the board, but they won’t be able to edit the board.
Select the **Regenerate Token** icon in the URL box if you want to invalidate all the previously shared links. Confirm the action to regenerate the token.
## Share cards on Channels
Cards can be linked and shared with team members directly on Mattermost Channels. When you share a link to a card within Channels, the card details are automatically displayed in a preview. This preview highlights what the card is about at a glance without having to navigate to it.
To share a card, you'll need to copy the card link first:
- Open a card and select the options menu **(...)** at the top right of the card, then select **Copy link**.
- Alternatively, you can open the board view and hover your mouse over any card to access the options menu **(...)** for the card and select **Copy link** from there.
After you've copied the link, paste it into any channel or direct message to share the card. A preview of the card will display within the channel with a link back to the card on Boards.