When building integrations with external data sources, we often store external IDs in content nodes created by the integration (for instance crmId). Having the value visible in Content Studio is helpfull, but in a lot of cases, we would like to disable the option to edit this field when editing the node.
This is an often requested feature which has been in our Roadmap for some time (see here and here).
The reason why it’s taking a while to implement is that we want it to cover all possible requirements. Some want to be able to hide some inputs completely, some want to always show them as readonly, some (like you) want to disable them only for specific roles (for example, disable for Content Editors but enable for Content Managers or Admins).
We will definitely look at this in the nearest future.
Thanks for the reply. We have ways to solve this outside of Content Studio now (with event listeners), but from a user perspective its best to get it in CS, so they can see that a field is disabled/locked.
Hi. We have researched this topic, and come up with a solution where you will be able to specify read/write permissions on a per input and role basis. This will enable high flexibility, and for your use-case you could simply deny both read and write for your users as required. this will also be reflected in the APIs.