Feature Request: Share Space but restrict entity views

[Illusory]

I broke down our current Fibery Permissions Setup in another thread if interested in reading.

@Illusory

Definitely looking forward to trying out share with groups, though it probably won’t solve much for us. Currently, we are creating 2 spaces for each use case.

e.g.

• Projects Admin
• Projects

Projects Admin has no access to all at Space Level and only Database level access for each user as “Submitter”.

In Projects, users have Access. Then, we create views to display items from Projects Admin.

Projects Admin/ (no access)
├── Database_1/ (only Submitter)
|    └── Fields/
|        ├── Person (share access by person)
|        └── Relation (share access by group through Person lookup field in Team space)
├── Database_2/ (only Submitter)
|    └── Fields/
|        ├── Person (share access by person)
|        └── Relation (share access by group through Person lookup field in Team space)
└── Database_3/ (only Submitter) 
     └── Fields/
         ├── Person (share access by person)
         └── Relation (share access by group through Person lookup field in Team space)

Projects/ (full access)
├── View 1/
|   └── Projects Admin/ (only submitter access)
|       └── Database_1.table (now can see entities if shared via person, related group's person lookup or submitted)
├── View 2/
|   └── Projects Admin/ (only submitter access)
|       └── Database_2.table (now can see entities if shared via person, related group's person lookup or submitted)
└── View 3/
    └── Projects Admin/ (only submitter access)
        └── Database_3.table (now can see entities if shared via person, related group's person lookup or submitted)

The biggest issues with this setup:

• Requires two spaces to manage permissions effectively
• Tedious and complex
• Notification issues (had to create rules to notify in some cases since user does not have access to Admin space.

Just sharing our setup in case it is helpful for anyone else.