Set access rights on product attributes – THRON Guide

Access rights on attributes allow you to define, group by group, who can view and who can edit each product field. This way different teams, marketing, logistics, IT, work each on their own data without risking accidental changes to critical fields.

Prerequisites

Have the "Data Model Management" permission
Rights are assigned per user group, not per individual user. Make sure the relevant groups already exist in the platform before proceeding.

The two access modes

Specific groups only

Use this mode to limit visibility and editing to only the groups you explicitly specify. For each group, you assign one of two levels:

Level	What the group can do
Can view	Sees the value in the product sheet, but cannot edit it
Can edit	Can edit the value. Automatically includes Can view

Constraints:

You must add at least one group before saving
You cannot add the same group more than once

Anyone in the organization

Use this mode to make the attribute visible to all users with access to Products, including those not assigned to any group. Then you can choose whether to:

Limit editing to specific groups: select the groups with Can edit permission
Leave editing open to everyone: in this case you cannot add additional groups

Recommended Configuration

For most multi-team catalogs, use Specific groups only as the default mode. Assign Can edit only to the teams that actively populate that attribute (e.g. Marketing for descriptions, ERP for technical codes) and Can view to other teams that only need to consult it.

Reserve Anyone in the organization for truly transversal attributes, such as SKU.

Configure rights on an attribute

Go to Platform Settings → Products → Attributes
Open an existing attribute or click New Attribute
In the form, find the Access rights section
Select the mode: Specific groups only or Anyone in the organization
If you chose Specific groups only: click Add user group, select the group, and assign the level (Can view or Can edit)
Repeat for each group to add
Click Create and configure (on a new attribute) or Save to confirm

Monitor and filter from the attributes list

In the attributes list you will find the Access rights column, which summarizes the active configuration of each attribute, for example "Everyone can edit", "Specific rights", or "No one can view". Use it to get a quick overview without opening every single attribute.

To check the status of a specific group, use the Access rights filter at the top of the list: select the group and the permission type (Can view / Can edit) to get the filtered list.

Edit rights on an existing attribute

Go to Platform Settings → Products → Attributes
Open the attribute from the list
In the Access rights section you will find the active configuration
Change mode, add or remove groups, modify assigned levels
Click Save to confirm

Technical notes and impacts

Scenario	Behavior
Initial state	Upon release, all existing attributes start in "Anyone in the organization" mode. Configure rights attribute by attribute: bulk editing is not yet available.
Can edit includes Can view	It is not possible to assign editing without viewing. The platform applies this automatically.
Attribute not visible	A user without Can view does not see any placeholder in the product sheet: the field is completely absent, not empty.
XLSX Import	Values imported for attributes where the user does not have Can edit are silently ignored, without an error message.
XLSX Export	Attributes without Can view are not included in the export columns.
API	Writing to an attribute without Can edit returns an explicit error, to help integrated systems detect incorrect configurations.
Completeness Markers	A group without Can view on an attribute included in a marker cannot use that marker: a percentage calculated on only partially visible attributes would be partial or inaccurate. With Can view but without Can edit, the group sees the marker but cannot bring it to 100%, because the missing field cannot be filled in and values uploaded via XLSX import are discarded without warning.
Channel delivery	Connectors to external channels, such as Shopify, operate by impersonating a platform user: the attributes that reach the channel are only those visible to that user. If you restrict rights on an already published attribute, verify that the user used by the connector maintains Can view, otherwise that data stops being transmitted.

## Additional articles
- Completeness Markers: what they are and how to configure them
- Channel Activation

Need help?

For technical issues, contact support@thron.com

Products and Assets Data Model