Authorization Requirement
Updates sync on a per-user basis. Each person who posts updates must individually authorize SIMB to sync their comments. If a user’s updates aren’t appearing on other boards, it almost always means that user hasn’t yet completed authorization.Authorization is a one-time action per user. Once a team member authorizes SIMB, all of their future updates on shared items sync automatically across every connected board.
How to Authorize

Click Authorize
Click the Authorize button. A new browser tab opens with the monday.com OAuth consent screen.
Check Authorization Status
To verify whether a specific user has authorized the app:- Open any shared item and go to the Same Item Multiple Boards tab.
- Click the Settings icon (gear icon) in the top corner of the SIMB panel.
- Go to Account Settings → Authorization. The current authorization status for that account is displayed here.
Invite Team Members to Authorize
If you manage a team and need to prompt others to authorize, SIMB provides two options:Send Invite via Email
Inside the SIMB item view, click the Send Invite button (the mail icon). This sends an email to the selected team member with a direct link to the authorization screen.
Share the OAuth Link Directly
Copy and share this link directly with anyone who needs to authorize: Authorize SIMB
Block Updates From Syncing
Sometimes you want certain updates to stay on one board only — keeping internal discussions off a client board, or limiting sensitive project notes to a specific team. You can configure this using SIMB automation recipes in the monday.com Integration Center.Open the Integration Center
Go to the board where you want to block updates and click the Automate button at the top.
Search for Same Item Multiple Boards
Type Same Item Multiple Boards in the search bar to surface available SIMB recipes.
Choose a blocking recipe
Select the recipe that matches your needs:
- Block all updates: “When update is posted, do not add it to other boards.”
- Block updates to a specific board: “When update is posted, do not add it to [specific board].”
Common Use Cases for Blocking Updates
Internal vs. Client Boards
Keep internal team discussions, notes, and decision logs private while still sharing item progress with clients on an external board.
Departmental Boards
Share only the updates relevant to a specific department. Prevent cross-departmental noise when the same item is tracked by multiple teams.
Confidential Projects
Protect sensitive project information — budget discussions, personnel decisions, or legal notes — from appearing on shared boards.
Multi-Team Collaboration
Ensure each team sees only the updates relevant to their stage of the workflow, keeping boards focused and noise-free.
Troubleshooting
If updates aren’t syncing as expected, start here:- Updates not appearing on other boards: The user posting the update likely hasn’t authorized SIMB. Follow the authorization steps above or send them an invite link.
- Updates blocked unexpectedly: Check whether a blocking recipe is active on the board. Remember — the recipe still runs even if its toggle appears off. Delete the recipe to fully remove the block.
- Partial sync (some users sync, others don’t): Authorization is per-user. Check each team member’s authorization status individually via Account Settings → Authorization in the SIMB panel.