Under Community Review

This is under community review to gather feedback and examples while seeing if there's more interest in this idea.

In terms of read-only fields, how would you or others imagine setting the permissions across the BluePrint for a given Schema?

And would such settings apply at an embedded schema level and/or at the individual field level?

Would there be a use case where an embedded Schema (or its fields) would need different read-only settings based on the Schema its used in?

Sign in to vote on ideas
+9
Sign in to vote on ideas

Read-only fields per Group

Ability to apply security to a field, and read-only to a field for a group of editors.  This would allow us to make more content manageable in the GUI, and would help in translation scenarios where we want to give a translator access to the text content, but not the ability to change the taxonomy keywords for the item.

Also, in the case of products, only a product manager could change the SKU of an item, but nothing else in the Component.

  • 1 comment
  • 0 members are here