Permission Rules determine what a User Role is allowed to do in KatanaPIM.
While User Roles define who someone is (for example: Sales Team or Content Manager), Permission Rules define what that role can access and manage.
Permissions are always configured on the role level — not per individual user.
Permission Rules control access to different entities within KatanaPIM.
Examples of entities:
For each entity, you decide what a specific User Role is allowed to do.
To configure permissions for a role:
Repeat this process for each entity that the role needs access to.
If you want to restrict access to a specific entity, simply do not create a permission rule for it.
What it is:
The role this permission rule applies to.
Example:
Content Manager
Sales Team
Marketing Team
This rule will apply to all users assigned to this role.
What it is:
The system object the permission applies to.
Examples:
You create separate permission rules per entity.
What it is:
Defines the scope of the permission inside the selected entity.
In most standard setups, this is set to:
Depending on your configuration, this field may allow more specific rule types (for example, limiting access to certain subsets).
If you select All, the permission applies to the entire entity.
What it is:
Specifies the exact value or condition the rule applies to.
In your example screenshot, since the rule is All, the Value field is not used.
What it is:
Defines the access level granted to the selected User Role for the specified entity.
Available levels:
Example from your screenshot:
This means:
All Content Managers can view and edit all Products.
After creating permission rules, you can review them in the overview:
On the Add New Permission Rule page, you can also see an overview panel on the right-hand side showing existing rules for the selected role.
