As more teams work in the same product data, the question becomes who may change what. In Pimberly, permissions are configured at group level and applied per schema, narrowing to individual attributes and further to specific locales and scopes within them. A team can be given full control of the data it owns and read-only visibility of everything else.
With Pimberly’s role-based access control, you can:
- Assign users to groups, with each group determining which Pimberly features are available to them
- Apply groups at schema level, so permissions are set per schema rather than platform-wide
- Narrow a rule to individual attributes, and further still to specific locales and scopes within one
- Set exactly which actions are allowed on an attribute or schema for each group
- Give a team full control of the data it owns, and read-only visibility of everything else
See how it works in the video below:
