# RACI MATRIX Space Idea

**URL:** <https://community.fibery.io/t/raci-matrix-space-idea/5034>\
**Category:** Get Help\
**Created:** [August 29, 2023, 4:25pm UTC](https://community.fibery.io/t/raci-matrix-space-idea/5034 "2023-08-29T16:25:15Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [August 30, 2023, 6:01am UTC](https://community.fibery.io/t/raci-matrix-space-idea/5034/2 "2023-08-30T06:01:00Z")

</div>

Such an RACI Matrix will be much more easy with the upcoming new relationship entity that the fibery team currently is working on ([References Reloaded](https://community.fibery.io/t/references-reloaded/4879)), because now we are still working with read-only lookup fields. This now means that if you create lookup fields for each RACI database item related to a user, you cannot edit the values in the table.

Here is a workaround:

Create an ‘RACI entry’, ‘Sector’, ‘Activity’ databases.  
In the RACI entry database, create relation fields to Sector and Activity, plus as many multi-select fields as you have team members. The multi-select fields all have the same options (R, A, C, I)  
Name=formula=entity ID, or a custom code you use for the responsibility.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5afe5c3d20105f19f168a3bad8ae105373e0607b.png)

---

_[View the full topic](https://community.fibery.io/t/raci-matrix-space-idea/5034)._