Data changeset isolationThis article shows the functionality to prevent unauthorised users from seeing data changeset information which is not relevant to them. This allows users to keep segregated roles of access to config. This scenario shows how the functionality is implemented. To test this yourself, you will require: 2 Users2 Roles2 Data path policies2 Dimensions. UserA has access to DimensionA, because it is assigned to a role which contains a policy which give it access to Edit DimensionA and it’s subnodes. UserB has access to DimensionB, because it is assigned to a role which contains a policy which gives access to Edit DimensionB. UserA will see in the dataModel only DimensionA. UserB will see in the dataModel only DimensionB. Therefore 2 dimensions are separate from the users, and the users are not “aware” of the other dimensions. Users: Roles: Policy: Admin View of DataModel: UserA makes modifications to DimensionA, adding nodes, keys & values. These are tracked in their DCS. It’s currently awaiting approval. Within the Incoming screen users now have 3 options: All changesets. Open / New changesets My changesets This is a simple and easy way to track data changesets and how they are being managed. UserB doesn’t have permission to see UserA’s changeset details. UserB is able to see ALL changesets, but the details within them have been restricted. In the below example, clicking on UserA’s changeset doesn’t show any data. The view of UserA shows all details. The view of UserB shows nothing. The best use of the incoming screen is primarily to use My changesets. Giving the quickest and easiest view of your work. For team collaboration use the New/Open changesets and the filter facility to understand the impact of changes the easiest. All changesets is for more experience users who can navigate to their changes quickly or for cross functional users tracking many on going changes. A final scenario might introduce a super user. UserC - who has permissions, authority and enough policy rights to see both dimensions. In this case they might open a changeset which enables changes from DimensionA & DimensionB. UserC creates a new data changeset. UserA scopes into the changeset and makes changes. UserB scopes into the changeset and makes changes. UserA cannot see UserB's changes and vice versa.