Select a linked Assignees lookup field for Assignee permissions
C
Caleb Cook
I love the "Assignee" permissions where someone can only see records that they are assigned to - however I'd love to be able to use a lookup field for this.
As an example:
I have a table called "Projects" that has a field called "Members" - where I can assign specific people. When I use the Assignee permissions that works great - I can ensure only the members have access to their projects.
However - let's say I now have a "Tasks" table - each task is linked back to a project. I have a Lookup field in Tasks that lets me see the "Project Members" for each task. I have a filter that allows me to ensure the user can also only see the tasks for a project that they are assigned to - but I can't select the Assignee field if it's a lookup field in permissions, so it's still possible for that filter to be removed.
Jon Darbyshire
Hello Caleb Cook! I have a few more questions for you:
- Can you provide more details on how you envision the interaction between the 'Assignee' permissions and the lookup field?
- What is the current impact of not being able to select the Assignee field if it's a lookup field in permissions?
- Can you share any specific scenarios where the inability to select the Assignee field in permissions has caused issues or inefficiencies?
C
Caleb Cook
Currently you can restrict access based on an "Assignee+" field if it's directly on the table as a way to limit records, but you can't extend that to lookup fields. In my example, I have these tables:
Projects table
- Assignee Field for project members
Tasks table
- Linked Record to Projects
- Lookup Field linking the project members
Ideally, a user would only be allowed to see a Task if they are associated with that Project. The Lookup field is treated like an assignee field as far as the UI is concerned, but I'm unable to select it as a field.
This would allow permissions to be much more dynamic since you can build any number of customized user groups, update that list in one spot, and have those permissions roll out over the rest of your linked records. As of now there's no way to accomplish this cleanly to ensure that "downstream" records are protected without automations.
Jon Darbyshire