1
Field's Editability control across the platform limited to Workflows and API
Source: twentyhq/twenty#14728 · opened by @kyrpav
Hi , the goal is to be able to block a field from being editable for all users.
So the fields should be only controlled by workflows or the api.
Current solution
Currently you can go to all of the roles in the system and block each role to edit the record.
Expected behaviour
To control user access to the field for the complete platform from inside the field configuration.
If you have 10-15 roles it is not so practical to go in each one and redo the same setup.
So the fields should be only controlled by workflows or the api.
Current solution
Currently you can go to all of the roles in the system and block each role to edit the record.
Expected behaviour
To control user access to the field for the complete platform from inside the field configuration.
If you have 10-15 roles it is not so practical to go in each one and redo the same setup.
No pledges yet. Be the first to back this.
Comments
Similar requests
Support workflow variable binding for the Send Email action's Attachments field
1 vote · 0 comments
I created a Twenty MCP Server - Looking for Feedback!
3 votes · 0 comments
Feature request: Allow admins to lock shared workspace views so users can filter temporarily without saving changes
2 votes · 0 comments
Mandatory Fields
6 votes · 0 comments
Feature Request: Error Nodes for Workflows
1 vote · 0 comments
No comments yet.