While there is a way to limit invitations to the application, is there a way to block or prevent a workspace from inviting someone to a board?
Example: Department A (workspace) has a project and built a board in Monday. They would like a resource from Department B (workspace) to complete work/tasks. The resource from Department B needs supervisor approval - is there a way to prevent Department A from inviting that resource? Department A still needs to be able to invite others to projects.
From my knowledge short answer is no: Not in a fully automated / “hard block per workspace” way with the current monday.com permissions model. But you can get close with a combination of user setup and permission controls.
Here’s what’s possible and what’s not:
There is no native setting that says:
“Users in Workspace A cannot invite Person X, but can invite everyone else.”
Board-level permissions (Owner / Admin / Member / Guest) control what people can do after they’re on a board, not which specific users can be invited.
Workarounds to try?
1. Use account-level invite restrictions - If you’re an admin, under Admin > Security / Users, you can:
Restrict who can invite new users to the account (e.g., only admins).
Restrict external guests by domain.
This doesn’t stop colleagues from different workspaces inviting each other, but it centralizes control over new people joining.
2. Use Teams + process-based approval
For “Department B resources,” you can:
Put them in a specific team (e.g., “Dept B Resources – Requires Approval”).
Communicate a process:
Department A may only invite teams (not individual Dept B users) to boards, and
An admin or Dept B supervisor controls which team members are added to that team.
Anyone not added to the “approved” team won’t be available to invite via that route. This isn’t a hard technical block, but behavior can be strongly guided by policy and how you train people to share boards.
3. Lock down board creation / ownership
Limit who can create boards/workspaces to managers or admins.
Make it policy that only these owners invite cross-department resources, and they must get supervisor approval first.
Use board permissions so “regular” users can’t change subscriber lists once the board is configured.
4. Use separate accounts (strongest technical separation)
If your org is large and the risk is high, the only real “hard block” is:
Separate monday.com accounts (e.g., Dept A has one, Dept B another), and
Connect them only through tightly controlled guest access or integrations.
This is heavy-handed and usually overkill, but it’s the only way to truly prevent a different department from directly inviting a given internal user.
Bottom line:
There’s no built‑in feature that blocks Department A from inviting a specific user while still allowing them to invite others. You’ll need to combine:
account‑level invite restrictions,
a team/role structure,
and a clear approval process (possibly enforced by limiting who can create/own boards).