Product Readiness permissions and access
Product Readiness permissions control who can view readiness results and who can create or manage Readiness Configurations.
Administrators assign these permissions through user roles.
Manage Readiness permissions
- Go to System → Roles.
- Open the role you want to update.
- Open the role's permissions.
- Find the Product Readiness permissions.
- Enable the required actions.
- Save the role.
Permission changes apply to every user assigned to the role.
Available Readiness permissions
Depending on your PIM version and edition, Product Readiness permissions may allow users to perform the following actions:
| Permission | What it allows |
|---|---|
| View readiness results | View readiness scores and unmet requirements in the Product Grid and Product Edit Form. |
| View configurations | Open and review existing Readiness Configurations. |
| Create configurations | Create new Readiness Configurations. |
| Edit configurations | Change product selections, contexts, requirements, and other configuration settings. |
| Delete configurations | Permanently remove a Readiness Configuration. |
| Import configurations | Upload Readiness Configurations into the PIM. |
| Export configurations | Download Readiness Configurations for backup or reuse. |
Grant configuration-management permissions only to users who understand how changes can affect readiness scores, exports, and connected workflows.
Access readiness results
Users need permission to view Product Readiness before they can see scores and unmet requirements in the PIM.
When access is granted, readiness information may appear in:
- The Product Grid
- The Product Edit Form
- Product and product model exports
A user may be able to view readiness results without being able to open or edit the configuration that produced them.
Existing product permissions still apply
Product Readiness does not replace or override the PIM's existing access controls.
A user's ability to view or edit product information may still depend on:
- Product and product model permissions
- Category permissions
- Locale permissions
- Channel permissions
- Attribute group permissions
- User group assignments
A user may see that a requirement is unmet but be unable to edit the associated value because of another PIM permission.
Configuration access
Users who can manage Readiness Configurations can define which products are evaluated and what those products must satisfy.
Depending on their permissions, they may be able to:
- Create and duplicate configurations
- Change product selections
- Select channels and locales
- Configure locale fallbacks
- Add, update, group, or remove requirements
- Import and export configurations
- Delete configurations
Editing a configuration can trigger the recalculation of many products. It may also cause products to become ready or not ready in connected systems.
Recommended role setup
Separate configuration management from day-to-day product enrichment whenever possible.
| Role | Suggested access |
|---|---|
| Product contributor | View readiness scores and unmet requirements. |
| Product manager | View results and review configurations. |
| PIM administrator | Create, edit, import, export, and delete configurations. |
| Integration user | Access readiness information through the required API, export, or Event Platform credentials. |
Troubleshoot access
I cannot see readiness scores
Ask an administrator to confirm that:
- Your role includes permission to view Product Readiness.
- A Readiness Configuration applies to the product.
- You have access to the selected channel and locale.
- You have permission to view the affected product or product model.
I can view a configuration but cannot edit it
Viewing and editing configurations are separate permissions. Ask an administrator to review the actions enabled for your role.
I can see an unmet requirement but cannot correct it
Your Product Readiness access may be correct, but another PIM permission may prevent you from editing the associated attribute, locale, channel, category, or product.
I cannot import or export configurations
Importing and exporting may require separate permissions from creating or editing configurations. Ask an administrator to review your role.
Access best practices
- Give contributors access to results without automatically granting configuration-management permissions.
- Limit delete and import permissions to administrators.
- Review permissions when responsibilities change.
- Test significant configuration changes before applying them to large product selections.
- Review access to configurations used by automated publishing or syndication workflows.