We’d like the ability to have different column setups for each group within the same board. Currently, all groups on a board share the same columns, but our workflows vary between groups, and being able to customize columns by group would help streamline processes and reduce clutter.
For example, one group might need a “Recontact Date” column, while another group does not. Allowing column customization at the group level would make boards more flexible and tailored to the needs of different teams or projects.
Welcome to the monday Community, Jordan! Shannon here with the monday team. Thank you so much for your feedback! I’ve moved your post to this existing feature request to ensure that we are accurately counting votes for all submissions tied to customizing board columns.
This post has been really helpful and with some great suggestions and workaround. I think the easiest and most straight forward one is to have all required columns on the board and use filters to set up views that align with requirements of each group.
Not sure if the view column restriction will be helpful as this will mean anyone who isn’t down as a board owner won’t see the restricted columns.
A feature that will be beneficial though is being able to hide views. this way users can hide views they don’t need. I guess they could always pin it to the front of other views.
The idea of a Dashboard is also great. This is how my team view the multiple boards they are involved with. Each board table can be set to what columns are needed.
Hi Michael! Thanks for submitting your feature request! I wanted to follow up and share the update left in this feature request:
Your requests align, so I thought it’d be helpful to provide you with an update. In May, our Product team shared this:
With this said, if you’d like me to merge your request with the linked request, please let me know. This way, we can ensure that votes for this feature request are accurately counted should our Product team prioritize the feature on the Product Roadmap!
Hi! I would love to be able to create columns for items or sub items that are specific to only ONE group. For example, in the early stages - we may need a point of contact related to the Contract Signing but later, in other groups, there is no need for that column. It would be great if we could select the groups where columns are used and not have to see them in others.
Having a lot of columns makes for additional and unnecessary scrolling.
Hi! I would love to be able to create columns for items or sub items that are specific to only ONE group. For example, in the early stages - we may need a point of contact related to the Contract Signing but later, in other groups, there is no need for that column. It would be great if we could select the groups where columns are used and not have to see them in others.
Having a lot of columns makes for additional and unnecessary scrolling.
Hi Elizabeth! Thanks for submitting your feature request! I wanted to follow up and share the update left in this feature request:
Your requests align, so I thought it’d be helpful to provide you with an update. In May, our Product team shared this:
With this said, if you’d like me to merge your request with the linked request, please let me know. This way, we can ensure that votes for this feature request are accurately counted should our Product team prioritize the feature on the Product Roadmap!
Current Limitation:
All groups within a monday.com crm board share the same set of columns. While it’s possible to add group-specific columns, the column headers remain global across all groups. This leads to:
Excessive columns across the board, with many left blank for most groups.
A messy and cluttered board that’s harder to navigate.
Difficulty managing different workflows within a single board effectively.
Example:
In a complex workflow, one group might need financial columns (e.g., budget, cost codes), while another group requires technical specifications or approvals. Currently, these extra columns apply everywhere, even where irrelevant.
Proposed Solution:
Allow columns to be independent per group, so each group can have its own unique set of columns without impacting others.
Columns irrelevant to a group are not displayed.
Boards remain clean and easy to manage.
Workflows become more flexible and better aligned with real-world needs.
Key Benefits:
Significantly reduces visual clutter by eliminating empty columns.
Improves usability and workflow management for boards with diverse processes.
Reduces the need for multiple boards, keeping all data in one place.
Minimises redundant automations since everything stays on a single board.
Enhances reporting by consolidating data without duplication.
Hi! Welcome to the monday Community! Thank you for submitting your feature request! As your request aligns with this existing one, I’ve merged your request to ensure we accurately count votes for this particular feature.
Currently, this feature is not on our long-term roadmap. You can read more about this update from our Product team, here:
However, your submission will help us to continue prioritizing the feature on the Product Roadmap. All updates for this feature will be shared in this thread with everyone!
Hi Community! We really appreciate your continued feedback–it really helps us understand your needs and evaluate for potential improvements. While this specific feature isn’t currently on our roadmap, it’s a request we’re actively reviewing and your input plays a big role in that process.
In the meantime, you check out the different ways to manage and organize your board data in this thread through the use of board views and filters, dashboards with customized Table Widgets, or the Portfolio Solution for higher visibility on the Enterprise Plan. We’d also love to keep hearing how you’d use this functionality in your day-to-day, so feel free to share more use cases!
I wanted to share here about a new feature that we started releasing gradually, which allows you to hide your Main Table:
While it doesn’t allow saving conditional coloring or filters to the main view, it does allow hiding it, and with the ability to unpin the main table and pin other views on the board, you can achieve a similar goal to the one described in this discussion