monday.com Board Permissions: Who Sees What and How to Automate It

monday.com decides who can see and change work in five layers: the account, the workspace, the board, the items on it and its columns. Dashboards and docs follow the boards they draw on. Most of the routine work can be automated: the monday.com API adds and removes board users, invites guests and sets board roles, and Enterprise accounts can hand the user lifecycle to their identity provider. This guide shows which setting does what, which plan has it, and how to automate the parts that repeat.
Show the parts for
How monday.com permissions fit together
Short answer: the board type decides who can reach a board. Board, item and column rules decide what people can do there, and on Enterprise, account and workspace permissions cap all of it. When the layers disagree, the strictest rule applies, and board owners bypass board permissions.
Account
Every person has an account role: admin, member, viewer or guest, plus custom roles on Enterprise.
- Admins manage the whole account: users, security, billing and boards.
- Members create and edit boards and items, and see every Main board.
- Viewers are read-only. They see Main boards and the boards they’re invited to, can’t edit or post updates, and can’t use the API. They don’t count toward billing.
- Guests are people outside your organization. They see only the Shareable boards they’re invited to, and they start on the Standard plan.
- On Enterprise, account permissions let admins allow or block actions by user type, such as creating boards, inviting guests, exporting to Excel, generating API tokens and creating automations. Admin privileges can be delegated for specific areas.
Workspace
- Enterprise accounts choose open or closed workspaces. Any team member can join an open workspace and see its Main boards; a closed one needs an invite or approval, and its Main boards are visible to workspace members only.
- On Enterprise, workspace owners set workspace permissions for what members can do there. A workspace can’t grant more than the account allows.
Board
- The board type decides who can reach it: Main, Private or Shareable.
- The permission set, or on Enterprise the board role, decides what non-owners can do there.
- Only admins and members can be board owners, and owners bypass board permissions.
Items
- Only edit assigned items (Pro and above) lets non-owners edit only the items and subitems assigned to them in a People column you choose.
- On Enterprise, owners can limit View items to the items a person created or is assigned to. The rule is board-wide: it applies to every role except owners.
Columns
- Owners can restrict column editing or restrict column view for chosen people or whole teams, but not both on one column.
- Board owners are never restricted, and the Tags column can’t be view-restricted.
Dashboards and docs sit beside the layers. A dashboard shows each viewer only the widget data they can already see on its source boards. Docs can be Main, Private or Shareable, and a doc can also get a read-only public link.
The strictest rule, step by step
- Account Member: can create and edit boards and items
- Workspace Open workspace: can join and see its Main boards
- Board View and comment: can view items and post updates
Result: this member can open the board and post updates, but can’t change item fields or the board’s structure. The board’s rule is the strictest of the three, so it wins.
Where to find each setting
- Board permissions: the board’s three-dot menu (upper right) › Permissions.
- Board owners: the board’s Invite icon › the grey crown next to a person’s name (it turns blue).
- Column permissions: the column’s three-dot menu › Settings › Restrict column editing or Restrict column view.
- Workspace permissions (Enterprise): the workspace name dropdown › Manage workspace › Permissions.
- Account permissions (Enterprise): your profile picture › Administration › Permissions.
- Your own permissions: anyone can open the permissions centre on a board they can access to see what’s allowed and why; owners select See your own permissions.
Pick your board setup: type, permission set or role
Short answer: pick the board type first, then the permission set. Private boards need Pro or Enterprise, Shareable boards (the only kind guests can join) need Standard or above, and Enterprise replaces the permission sets with board roles you can tailor.
| Board type | Who can reach it | Guests | Plan |
|---|---|---|---|
| Main | Every team member in the account (in a closed Enterprise workspace, its members only) | No | All plans |
| Private | Only people invited to the board | No | Pro and Enterprise |
| Shareable | Only people invited to the board, team members or guests | Yes | Standard and above |
Permission sets (below Enterprise)
On plans below Enterprise, a board owner picks one permission set for the whole board. It applies to everyone except the board’s owners.
| Permission set | View the board | Edit items | Change structure (columns, groups, views) |
|---|---|---|---|
| Edit everything | Yes | Yes | Yes |
| Only edit content | Yes | Yes | No |
| Only edit assigned items (Pro and above) | Yes | Only items and subitems assigned to them | No |
| View and comment | Yes, and post updates and replies | No | No |
Board roles (Enterprise)
On Enterprise, owners assign roles and then tailor what each role can do by category: items, subitems, general, updates, columns, groups, views and forms. A role is a ceiling: you can remove actions from it, not add actions above it. People who join a board start with the default role set under General access.
| Role | What it can do by default |
|---|---|
| Owner | Full control; bypasses board permissions |
| Editor | Create and edit items and subitems, post updates and manage structure (columns, groups) unless the owner restricts it |
| Contributor | Add and edit items and subitems and post updates; can’t add or remove columns by default |
| Assigned contributor | Edit only the items assigned to them in a chosen People column; otherwise like a Contributor |
| Viewer | View the board and post updates and replies; can’t change item fields or structure |
Column permissions: restrict editing or viewing
Column permissions protect sensitive fields such as budgets, pay or approvals. Open the column’s menu, choose Settings, then Restrict column editing or Restrict column view, and add the people or teams who keep access. Board owners always keep access, a column takes an edit restriction or a view restriction but not both, and the Tags column can’t be view-restricted. Changes take effect shortly after you save them.
Plan check: monday.com’s Column permissions article lists Pro and Enterprise, while its Permissions overview lists Enterprise. Check the column menu in your own account before you plan around it.
How to set a board’s permissions
- Open the board, select the three-dot menu in the upper-right corner and choose Permissions.
- Pick a permission set, or on Enterprise, the role you want to adjust.
- Review the categories along the top (Items, Subitems, General, Updates, Columns, Groups, Views, Forms) to confirm what it allows.
- Select Save, check the summary window, then select Save again.
- For Only edit assigned items, select Customize next to Edit items and pick the People column that defines the assignment.
When you duplicate a board, its board permissions are duplicated too, so a template board set up once keeps its rules in every copy. Organizing boards well helps here: see our monday.com folder structure guide.
Can this person do it? Check a permission
Short answer: pick an account role, a board type and a permission set to see what monday.com’s documented rules allow on a board below Enterprise, and which rule decides it.
The checker runs in your browser. Without it, use the tables above: the board type decides who can reach a board, and the permission set decides what non-owners can do there.
On Enterprise, board roles take the place of the permission sets, and account and workspace permissions can block more. The strictest rule still applies.
Based in Canada · Clients across North America and Europe
Map who should see what
In a free 30-minute call, we map your boards, roles and guests and show which access steps can run on their own.
- Certified monday.com Partner
- Free 30-minute call
- Reply within 2 business days
- We sign an NDA
Automate board access with the monday.com API
Short answer: the API adds and removes board users and teams, invites people, sets board roles and changes a board’s type. Column permissions have no mutation. A personal token can do only what its user can do in monday.com itself.
Before you write the first call:
- The token decides what you can do. A personal token mirrors its user’s permissions and has every scope; an app (OAuth) token can call only the scopes the app was granted, such as
boards:write. Admins, members and guests can use the API (guests through OAuth or a short-lived token, not a personal token); viewers and deactivated users can’t. - Send the version header. ,
update_teams_board_roleand need API version 2026-10 or later, the current version (headerAPI-Version: 2026-10). - Mind the daily call limit: 1,000 calls a day on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise.
create_boardandduplicate_boardalso allow 40 calls a minute. - Invites are pending until the person accepts them.
Board access
add_users_to_board
Adds people to a board as subscribers or owners (kind: subscriber or kind: owner).
mutation {
add_users_to_board(board_id: 1234567890, user_ids: [123456, 234567], kind: subscriber) {
id
}
}Watch out: guests can join only Shareable boards, and someone you just invited stays pending until they accept. Add users to board in the API reference · Client onboarding playbook
delete_subscribers_from_board
Removes people from a board.
mutation {
delete_subscribers_from_board(board_id: 1234567890, user_ids: [12345678, 87654321]) {
id
}
}Watch out: it removes board access only, one board per call. To take someone out of the whole account, deactivate them with or deprovision them through SCIM. Delete subscribers from a board in the API reference · Contractor offboarding playbook
add_teams_to_board
Adds whole teams to a board, as subscribers by default or as owners.
mutation {
add_teams_to_board(board_id: 1234567890, team_ids: [654321], kind: subscriber) {
id
}
}Watch out: giving boards to teams instead of people means a new hire needs only one step: joining the team. Add teams to board in the API reference · New-hire access playbook
Roles and board type
update_users_board_role
Changes the board role of people already on the board (role_name: editor, contributor or viewer). update_teams_board_role does the same for teams.
mutation {
update_users_board_role(board_id: 1234567890, user_ids: [11111111, 22222222], role_name: editor) {
successful_user_ids
failed_users { user_id error }
}
}Watch out: it doesn’t grant access, so add people with first. Up to 200 users per call, and the assigned contributor role isn’t supported yet. Update users board role in the API reference
set_board_permission
Sets a board’s default role (basic_role_name: contributor, editor or viewer).
mutation {
set_board_permission(board_id: 1234567890, basic_role_name: viewer) {
edit_permissions
failed_actions
}
}Watch out: it works only for a board owner on an Enterprise plan, so the token must belong to one. Set board permission in the API reference
change_board_kind
Switches a board between Main, Private and Shareable (kind: PUBLIC, PRIVATE or SHARE; public is a Main board).
mutation {
change_board_kind(board_id: 1234567890, kind: PRIVATE) {
id
board_kind
}
}Watch out: Private boards are a Pro and Enterprise feature, and Shareable boards start on Standard. Change board kind in the API reference
Users and invites
invite_users
Invites people to the account as guests, members or viewers (user_role: GUEST, MEMBER or VIEW_ONLY).
mutation {
invite_users(emails: ["client@example.com"], user_role: GUEST) {
invited_users { id name }
errors { message code email }
}
}Watch out: invited people stay pending until they accept, and a guest needs an email domain that isn’t your organization’s. Invite users in the API reference · Client onboarding playbook
deactivate_users
Deactivates people in the account, so they lose access to it.
mutation {
deactivate_users(user_ids: [54321, 12345]) {
deactivated_users { id name }
errors { message code user_id }
}
}Watch out: it also deactivates the integrations and automations those people created, so move them to a new owner first. You can’t deactivate yourself. Deactivate users in the API reference · Contractor offboarding playbook
Add and remove users at scale: SCIM (Enterprise)
On Enterprise, SCIM provisioning lets your identity provider manage monday.com users, so people get access when they join and lose it when they leave. monday.com documents a setup for Okta and a custom SCIM setup. It supports provisioning and deprovisioning users and teams, renaming teams and assigning users to teams. Deprovisioned users become inactive and don’t count toward your user count. Move their boards, automations and integrations to a new owner before the identity provider deactivates them.
Zapier and Make (formerly Integromat) run on the same API. Check that your connector offers a permission action before you plan around it; if it doesn’t, a custom integration can call these mutations directly.
Playbooks: onboarding, offboarding and new-hire access
Short answer: the three access jobs that repeat are bringing a client in, taking a contractor out and giving a new hire the boards their role needs. Each playbook shows the steps in order, with a path that needs no code and a path through the API.
Client onboarding
- Trigger Deal marked Won
- No-code Board created from a template
- API Client invited as a guest
- Wait Invite pending until accepted
- API Client added to their Shareable board
- Done Client sees only that board
No-code path
- A monday.com workflow creates the client’s board from a template or duplicates a template board (how to duplicate template boards automatically). Board permissions come along with the copy; custom automations don’t.
- Make it a Shareable board, the only type a guest can join.
- Invite the client from the board’s Invite icon. They get an email and join once they accept.
- Hide internal columns, such as a budget, with Restrict column view.
API path
- with
user_role: GUESTinvites the client; they stay pending until they accept. duplicate_board, orcreate_boardwithboard_kind: share, creates their board.- adds the client to it as a subscriber.
- sets their role, for example
viewer, once they’re on the board.
Contractor offboarding
- Trigger Project marked Complete
- API Removed from each board
- Admin Boards and automations moved to a new owner
- Admin User deactivated
- Done No access left behind
No-code path
- If the contractor stays in the account for other work, remove them from the project’s boards only.
- If they leave the account, an admin opens Administration › Users › Board ownership and moves all their boards to a new owner in one step, then does the same on the Automation ownership tab.
- The admin deactivates them. monday.com offers to move their integrations during deactivation and warns that their automations and integrations are deleted otherwise.
- Dashboards they own are listed under Administration › Content directory, filtered by owner.
API path
- for each project board, or
delete_teams_from_boardandremove_users_from_teamwhere access came through a team. - with
kind: ownergives a board a new owner where the contractor was the only one. - (admins only) once ownership is moved.
- On Enterprise with SCIM, deprovisioning them in your identity provider makes them inactive in monday.com.
New-hire access by role
- Trigger New hire starts
- API Added to their role’s team
- Done Team already on the right boards
- API Role set on each board
No-code path
- Give each role a team, and invite the team to that role’s boards; teams can be named in column restrictions too.
- Add the new hire to the team: they get every board the team has.
- See how this fits your wider setup in our workflow management best practices.
API path
add_users_to_teamputs the new hire in their role’s team.- gives the team any new board.
update_teams_board_rolesets the team’s role on a board it’s already on.- On Enterprise with SCIM, assigning users to teams in your identity provider does the first step for you.
Based in Canada · Clients across North America and Europe
Automate board access through the API
TaskRhino builds custom monday.com integrations, including user and board access steps.
- Certified monday.com Partner
- Free 30-minute call
- Reply within 2 business days
- We sign an NDA
Watch out: where data can leak past your permissions
Short answer: board and column rules don’t cover every way out. Shared board views, public doc links, open forms, exports and API tokens can each reach people your permissions don’t include.
Shared board views and embeds
Board owners can share a board view through a public link or an embed code. Hidden columns and filtered-out items don’t show, but monday.com warns that “filtered data (items and columns) can still be accessed through the shared views by technical savvy users although it is hidden.”
Close it: share views only from boards with nothing sensitive on them, and stop a share from the view’s Share settings once it’s no longer needed. On Enterprise accounts with the HIPAA feature on, sharing views is turned off.
Public doc links
A doc can get a read-only public link that anyone with the link can open without an invite.
Close it: keep sensitive docs Private, and check which docs have a public link.
Forms anyone can fill in
A WorkForm accepts answers from anyone with its link until you turn on Require login (Share form › Sharing permissions).
Close it: require login on forms that write to boards with internal data.
Exports to Excel
Viewers can export boards to Excel, so a read-only person can still take a copy of the data.
Close it: on Enterprise, account permissions can block exporting to Excel by user type, and the Audit Log records board data exports.
API tokens
A personal token carries every right its user has, on every board they can reach.
Close it: on Enterprise, account permissions decide who can generate API tokens. For critical integrations, monday.com offers service accounts, so they don’t depend on one person’s account.
Not a leak: connected columns and dashboards
Connect Boards and Mirror columns show nothing from a board the viewer can’t access, and dashboards show only widget data the viewer can already see on the source boards.
No action needed: these follow the source board’s permissions.
Track who did what: the Audit Log (Enterprise)
On Enterprise, admins can open Administration › Security › Audit to see when people logged in and out, from which device and IP address, plus failed logins, attachment downloads and board data exports. Filter by the person or by the event type; times show in GMT. Developers can read the same events through the audit event catalogue in the API reference. For the wider picture, see monday.com data security and compliance.
What can and can’t be automated
Short answer: most access work can run through the API, SCIM or a workflow. Column permissions, the permission sets below Enterprise and moving automations to a new owner stay manual.
| Task | How | Route |
|---|---|---|
| Create a project board from a template | A workflow (Create from template or Duplicate board), or duplicate_board and create_board |
No-code, API |
| Change a board’s type | The board’s settings, or | Manual, API |
| Give a person access to a board | The board’s Invite icon, or | Manual, API |
| Give a team access to a board | Invite the team, or | Manual, API |
| Invite a guest or a new user | Invite by email, or (pending until accepted) | Manual, API |
| Set a person’s or team’s board role | The board’s Invite list, or and update_teams_board_role |
Manual, API |
| Set a board’s default role | General access, or | Manual, API, Enterprise |
| Choose a board’s permission set (below Enterprise) | The board’s Permissions menu | Manual |
| Restrict editing or viewing of a column | The column’s Settings menu | Manual |
| Remove a person from a board | The board’s Invite list, or | Manual, API |
| Give a leaver’s boards a new owner | Administration › Users › Board ownership, or with kind: owner |
Manual, API |
| Move a leaver’s automations to a new owner | Administration › Users › Automation ownership | Manual |
| Deactivate a user | Administration, (admins), or SCIM deprovisioning | Manual, API, SCIM |
| Add and remove users and teams from your identity provider | SCIM provisioning (Okta or a custom setup) | SCIM, Enterprise |
| Review logins, failed logins and exports | The Audit Log, or the audit events in the API | Manual, API, Enterprise |
Frequently Asked Questions
Can any tool automate monday.com board permissions?
Yes, any tool that calls the monday.com API can. It has mutations to add and remove board users and teams, invite people, set board roles and change a board’s type. Column permissions are the exception: they’re set by hand on the board.
Is monday.com planning to add permission automation?
It’s already in the API. API version 2026-10, the current version, added , update_teams_board_role and , alongside older mutations such as and .
What if I use OAuth to build a custom integration?
An app token can call only the scopes the app was granted, such as boards:write for and workspaces:write for workspace users. A personal token has every scope, but it can do only what its user can do in monday.com.
Can I hide some items from some people on the same board?
On Enterprise, yes: a board owner can limit View items to the items a person created or is assigned to in a People column, and the rule applies to every role on the board except owners. Below Enterprise, Only edit assigned items (Pro and above) limits editing, not viewing, so the usual way to hide rows is a separate board per client.
What about Shareable Boards? Can I automate guest access?
Yes, through the API. with user_role: GUEST creates a pending invitation the guest must accept, and adds them to the Shareable board. Guests can only join Shareable boards they’re invited to.
Why do teams still manage permissions by hand?
Some steps have no API: column permissions, and the permission sets on plans below Enterprise, are set on the board. Permission changes are also sensitive, so many teams keep a person approving each grant and removal even where the API could do it.
Do board owners have to follow board permissions?
No. Board owners bypass board permissions and column restrictions, and on Enterprise they see every item even when View items is limited. Only admins and members can be board owners.
If I’m managing 100+ projects per year, how do I scale permissions?
Give boards to teams instead of individual people, create project boards from a template with a workflow (board permissions come along with the copy), use Shareable boards for clients, and automate invites and removals through the API. On Enterprise, connect SCIM so users and teams follow your identity provider.
Where to start
Admins
set each board’s type and permission set, then restrict the few columns that need it.
Developers
start with , and , and send the
API-Version: 2026-10header for the newer role mutations.Agencies
one Shareable board per client, with internal columns restricted, keeps clients apart.
IT and security
connect SCIM, set account permissions for guests, exports and API tokens, and review the Audit Log.
Based in Canada · Clients across North America and Europe
Need help with your monday.com setup?
TaskRhino has implemented monday.com for 110+ clients. Get a free consultation.
- Certified monday.com Partner
- Free 30-minute call
- Reply within 2 business days
- We sign an NDA
Last verified against monday.com API version 2026-10 and monday.com’s help centre on October 30, 2026.
Sources
- Permissions on monday.com Board types, permission sets, Enterprise roles, column, dashboard, doc, workspace and account permissions
- Board permissions Owners, permission sets, the strictest rule, Only edit assigned items, duplicated boards
- Board permissions on Enterprise Board roles, General access, item visibility
- Column permissions Edit and view restrictions, teams, the Tags column, plans
- The difference between board types Main, Private and Shareable boards
- User types explained Admins, members, viewers, guests, board owners
- Workspace permissions Workspace roles and permissions on Enterprise
- Account permissions Allowing and blocking actions by user type
- What to do when a member leaves your account Board, automation, integration and dashboard ownership; deactivation
- SCIM provisioning of users and teams with Okta Provisioning, deprovisioning, inactive users
- SCIM provisioning: custom setup Supported SCIM capabilities
- The Audit Log What it records, filters, time zone
- How to share a board view publicly Shareable links, embeds and the hidden-data warning
- Connect Board and Mirror Column permissions explained Connected data follows the source board’s access
- WorkForms settings and permissions Require login
- Users (monday.com API reference) add_users_to_board, delete_subscribers_from_board, invite_users, deactivate_users
- Boards (monday.com API reference) set_board_permission, update_users_board_role, update_teams_board_role, change_board_kind, rate limits
- Teams (monday.com API reference) add_teams_to_board, add_users_to_team
- Authentication (monday.com API reference) Token permissions and scopes
- API basics Who can use the API
- Rate limits Daily call limits by plan
- API versioning 2026-10 is the current version








