# Messages From Multiple Inboxes into Task Database - Extra Columns

**URL:** <https://community.fibery.io/t/messages-from-multiple-inboxes-into-task-database-extra-columns/4350>\
**Category:** Get Help\
**Created:** [April 20, 2023, 8:54pm UTC](https://community.fibery.io/t/messages-from-multiple-inboxes-into-task-database-extra-columns/4350 "2023-04-20T20:54:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joe\_H](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/joe_h/32/6575_2.png) [@Joe\_H](https://community.fibery.io/u/Joe_H)\
**Post date:** [April 20, 2023, 8:54pm UTC](https://community.fibery.io/t/messages-from-multiple-inboxes-into-task-database-extra-columns/4350/1 "2023-04-20T20:54:00Z")

</div>

Howdy,

I have setup inboxes for specific departments that create tasks & reference back to the original message. I’m running into an issue adding in new departments where each relation creates a column, but now I have several “messages” columns in the same tasks table and all but 1 of them are empty for a given task (and they all show up when viewing the entity in detail form).

The reason for the different inboxes is access control – not every department needs to see messages for the other departments, but I still would like to centralize the tasks.

What would be the best way to go about simplifying the columns in the task database? I was thinking it would be to create a new database that just compiles the messages, but upon further thought I am thinking that still will have the access issue, as the relation would be to the new database & not the original one. This may be something that I can solve once the entity permissions are rolled out.

---

<div class="post-metadata">

**Author:** ![Joe\_H](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/joe_h/32/6575_2.png) [@Joe\_H](https://community.fibery.io/u/Joe_H)\
**Post date:** [April 25, 2023, 3:46pm UTC](https://community.fibery.io/t/messages-from-multiple-inboxes-into-task-database-extra-columns/4350/2 "2023-04-25T15:46:17Z")

</div>

I figured out my work-around for this. I’m just going to have the departments utilize tables within the relevant work-spaces (which won’t have the additional tables displayed) rather than the catch-all table.