Product Readiness is in beta. It is available for evaluation and early use, but its features, configuration options and API contracts are still evolving and may change, or be removed, before general availability. We recommend against relying on it for business-critical workflows until the full release.
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 Product Readiness permissions
| Permission | What it allows |
|---|---|
| List Readiness | Access the Readiness Configuration list and review existing configurations. |
| Edit Readiness | Create, update, duplicate, enable, disable, and delete Readiness Configurations. Users also need List Readiness to access the configuration screens. |
| List Readiness under API permissions | Access the Readiness Configuration endpoints through the External API. Normal Web API access permissions also apply. |
Access readiness results
Users do not need List Readiness or Edit Readiness to view scores for Products and Product Models they can already access.
Existing Product, Category, Channel, Locale, and Attribute Group permissions continue to determine which entities and values a user can view or edit.
A user can view a readiness score or an unmet requirement without being allowed to open or change the Readiness Configuration that produced it.
Importing and exporting Readiness Configurations also depends on the standard permissions for job profiles and job execution. These actions do not have separate Product Readiness permissions.
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.