GUIDE2 - Access to a single attribute

WHEN TO USE;  user should access a single cell or attribute. And when not having to create a role with a long list that excludes every other attributes.

E.g. the Factory asset has following sub-assets, which control individual attributes.

If we were to create a role that only allow to edit the factory name, we would create a role that looks like this:

The first permission line of the role entitles a user to read (see) the factory object, i.e. it can be opened in an editor and all attributes will be shown. But, since the write permission is not checked, all attributes will be read-only.

The second permission line adds write permission, but only to the specific attribute ("Factory.Name").