We have different schemas in place used by different groups of colleagues. We would prefer to have schema separation in place to improve the usability of the system for users.
As key functionality (eg channels) requires Account Admin rights to be given to most colleagues, we have found ourselves in a "everyone can see everything" situation. This doesn't feel safe from a data security perspective but it also means that key administrative sections such as attribute set-up (just for one very basic example) is open and editable by virtually all of our users.
In the Attribute screen, for example, we have all attributes across all schemas. We've had to put in place a naming convention for attributes which feels clunky and the user feedback is that there is too much information that relates "to the other schemas"
Ideally, the schema separation would be in full from top to bottom. Nothing is visible on any screen/section if it doesnt relate to the schema(s) you are assigned to.
Comments
Please sign in to leave a comment.
Another example that falls within schema separation:
There is a currently a default attribute set (called "Core" in our instance) - this is shared across our schemas.
We have a schema with a unique requirement for a specific attribute (that is unique to one of the schemas) to be in this default attribute set. We can't make this simple edit as this would impact the other schemas.
Ideally, the default attribute set needs to be schema-specific.