Demo Scenario:
I have a Retool application that includes a table component with the following columns:
- Task
- Remark
- Assigned (indicating which user the task is assigned to)
Goal:
I want to configure the table or the application logic so that:
Each row can only be edited by the user whose account matches the value in the Assigned column.
For example, if a row has Assigned = "john", then only the user logged in as john@example.com should be able to edit that row.
Other users should only have view access to rows not assigned to them.
This is a demo use case, but I intend to apply the same logic to a real-world scenario.
Question:
Is it possible to implement this kind of row-level permission logic in Retool?
If yes, what would be the best way to set it up?
If not, is there a different way I can think about implementing something like this?
