Board Level Update Option for Board Only Communication / Collaboration

As the admin of our boards and manager of most of the individuals using those boards I think it would be great if there was an “Update” feature that allows board owners to communicate / collaborate with all subscribers and guests of a board about the board rather than within individual pulses.

Monday.com is evolving quickly so our boards are also always evolving as new features are added. Because of this there are many instances when an update about the board (not pulses) for changes / revisions of all kinds, issues, or added features would be very helpful. Personally I try to avoid email and funnel as much correspondence as possible through the Monday.com platform.

Sometimes I add a pulse to a board and communicate with subscribers / guests using that pulse for board level correspondence, however that particular pulse really doesn’t sync with everything else happening on the board, also not always easily visible or easy to understand for board subscribers / guests.

Examples of pulse for board communication…



Thanks in advance for taking the time to have a look!

Hello @Aksalano,

In a similar scenario, I usually create a dedicated group for a chat within the board that may be used to provide also updates about the project to all team members. It stays on the top with only one activity so it can be easily accessible.

1 Like

Good to know others do the same type of work around, will probably copy what you are doing for some boards. The ideal solution would still be if Monday integrated as part of the platform.

2 Likes

I think it shouldn’t take much time to happen.

2 Likes

Actually to add to the topic…we have an entire board committed to messaging, rather than send emails we try to categorize our correspondence and drive communication / collaboration through a single board. It takes time to move people off a platform like email but can be more productive than traditional email and keeps people on the same platform while they work.

1 Like

I would like to see the update capability added for both boards and for groups. For illustration, if a board is a project, sometimes (as others have said) the whole team subscribed to the board needs to communicate about the board / project as a whole. And then, if groups represent project phases, the same need applies there for group communication.

2 Likes

I do that to put a pulse for general communication. so many times we have conversation that is not relevant to pulses in a board. wold like to see that feature. @PedroM any news about that?

1 Like

Hello @nikolamujdzic. No, no news yet.

I assume the goal to this issue would be that the messaging capabilities of monday.com become a real alternative the services like Slack.
At the moment monday.com could not replace Slack at our company. But it would have the possibilities to achieve this in the future.

If Monday.com would adopt the Slack system it could be something like this:
Slack channels = Monday boards
Slack threads = Monday groups or pulses
Slack DM = Monday DM

But to compete with Slack is a rather high goal. Monday than would also have to include nativ calls & nativ screensharing. (And maybe giphy integrations :wink:
I’m curious to see what Monday will coming up with regarding the communication tools…

@Sven.H,

I have not used Slack so not sure. Updates for pulses work great for our team and how we use the platform, an obvious “Updates” feature at the board level is missing unless you use the workaround which is to create a group / pulse to Update (message) board subscribers.

1 Like

This is how we get around the board comms thing too - but it would be great to have a native function!

1 Like

I agree, for now we have added group titled “Board Chat” to every board, not ideal but allows group discussion about the board rather than individual pulses.

1 Like

Funny to see we are doing same workaround. In addition to the post, I would say that this is required not only for board owners but for all people allowed to write updates in the board items already

I’d also like to throw in another use case which isn’t just relegated to the idea of an in-board chat system, since I’m worried that gets more conflated with actually competing with something like Slack.

I’ve been wanting a board-level update system for a while now (and also more recently maybe a Group level one). It would be nice if the board level allowed you to dive down to updates on any particular Group or Item as well, but ultimately I just want the ability to have updates on a board for the sake of Notes.

Currently, If I want to take notes on the overall status of things all together within a board, I either need to create a dashboard and use a widget, the overall board description, or I need to create separate Groups/items within the board purely for the sake of notes, links, and changelists. And honestly that last item is really my primary goal and desire. We iterate on our boards fairly consistently, and it would be nice to have a place where the overall changelist could be stored and accessed by members of the team so that they can see what changes are happening (or have happened).

We’re currently sort of using the description field for this in some boards, but long term that is going to amount to a lot of changes, and I’d rather not fill up and clutter the board’s general description space. I’ve thought about using the dashboard and text widget method, and that may end up being the next go-to, as well as about creating a wholly separate board to track a general status of each of our boards, and their changelists overtime in the subitems. However, these could all be simplified by just having the same functionality on the Board level as on the Item level.

  • That said, while typing this out, I thought of another possible implementation (at least for my needs of changelist if not able to use updates and info boxes at the board level) of having a secondary tab within the Description for ‘Board Notes’ or something… but really to solve my issue as well as the others in this thread, adding update functionality would be the simplest catch-all… unless that spot inside the description is where the update/conversation system was implemented.