Board access overrides

Jake Sawyer

Updated March 23, 2026 11:00

When a user becomes a member of a teamspace, there are three possible member access levels they may be granted: view-level, edit-level, or owner-level access. Normally, a user's member access level defines how they interact with every board in that teamspace.

However, board access overrides allow you to adjust a member's access level to specific boards, or to hide a board all but the teamspace members you specify, granting you finer control over who's capable of what in any given teamspace.

Note: Board access override can't grant someone rights above their workspace role. For example, it can't be used to give a viewer access to a grid, because viewers can never see grids.

Overriding member access levels

A teamspace member with edit-level access to a teamspace can be given view-level access to one or more specific boards via override.

The same is true in the opposite direction: a teamspace member with view-level access can be given edit-level access to one or more specific boards via override.

Note: Only members with the Maker role type can be given edit access via override.

To override a member's access to a specific board:

Open the board you wish to override access to.
In the top right corner, click Share to open the Share menu.
Click the access level dropdown beside a member to override that member's access level to this board. You can use the search bar near the top of the menu to find specific members faster.

Overriding many members' access levels at once

From a board's Share menu, you can use the checkboxes beside each member's name to add them to your selection.

Alternatively, click the checkbox beside the search bar to select all members.

When you're ready, click Change access at the bottom of the menu to apply an override to all selected members.

Making a board private

You can limit visibility of a board to selected users within a teamspace by making it private. This allows you to keep sensitive or in-progress work hidden without moving it out of the relevant teamspace.

To make a board private:

In the top right corner of the board, click Share to open the Share menu.
Enable Make this board private.

When you make a board private, it disappears from the teamspace for everyone except you (and all workspace admins, who always retain board visibility). You can then override the access levels of specific teamspace members (in the same manner as above) to allow them to view or edit the board.

Restoring default access

Once board access has been overridden, a new option called Restore default access will appear at the bottom of the Share menu. Click this button to remove all overrides on this board, causing each member's access level to match the one set for them in the parent teamspace's settings.

Note: Only admins and teamspace owners can restore default access.

Member actions

Here's information on who can do what with board overrides:

Admins, teamspace owners, and makers with edit access are the only ones who can override board access.
If you have view-level access to a board, you can't override that board.
When a user has edit access at the teamspace level, they can duplicate any board, even if they only have view-level access on an overridden board.
When a user has edit access at the teamspace level and view-level access on a board, they can adjust the configuration of the board and save it as a new board, but they can't save their changes to the existing board.

Important behaviors

Here's more information about how exactly board overrides behave:

Board overrides persist until the board access is restored to default.
If a board is private, restoring default access will also remove the board's private status.
When a member has overridden board access and their teamspace access is changed (either upgraded or downgraded), any board-level override persists.
When access levels for members of a board are overridden, teamspace membership continues to be synced.
When moving a board between teamspaces, any board overrides are reset and the new teamspace-wide access level is assumed.
Archiving a teamspace does nothing to the state of board overrides. When a teamspace is unarchived, all its board overrides will remain unchanged.

Popular use cases

You can use board overrides for all sorts of granular authentication needs. Here are two good ones.

Use Case 1: Company wide roadmaps

Maintain the integrity of company wide roadmaps by giving every member of a teamspace view-level access to the board. This means that the filters and configuration cannot be updated for that board, ensuring its integrity.

Use Case 2: Templates

If your PMs have edit-level access to a teamspace, you can override their access to view-level for specific boards that you want them to duplicate for their own purposes. This removes the risk of someone accidentally changing a template.

Use case 3: Secret documentation

You're planning a radical new addition to your platform. The document for this project lives in your Strategic Planning teamspace, but you only want a few people to be able to see it for now, so you make it private and override the access levels of key stakeholders so they're the only ones who know the document exists.

FAQ

What types of boards support access overrides?

You can override access for grids, timelines, columns boards, insights boards, and documents.

Who can override the access a member has to a board?

Admins, teamspace owners, and makers with edit access are the only ones who can override board access.

Can a member with edit access to a teamspace, but view access to a board, override member access on that board?

No. If a user has edit access at the teamspace level but only view access at the board level, they can't add new overrides for that board.