1. Problem Statement Currently, all users who can upload images to the DAM—regardless of their role—are able to toggle the checkbox “Enable search engine indexing” on an asset. This creates a governance and security risk because:

Some images are intended for public-facing websites and should be indexable.
Other images are intended strictly for intranet use and must never be indexed by search engines.

Because all roles can toggle this setting, users who do not understand the implications may unintentionally expose internal assets to external search engines, or hide assets that should be indexable.
Today, even low permission users can make indexing decisions that should be governed by a specific group (e.g., Admins, Creators, or DAM Managers).

1. Desired Outcome / Feature Description We would like the ability to control visibility and editing permissions for the “Enable search engine indexing” setting based on user role. Specifically, we need:

The option to hide the checkbox entirely for users who should not manage indexing.
The ability to restrict this setting so that only designated roles (e.g., Admins and Creators) can view or change the indexation status.
A configuration option at instance/tenant level to map which roles can manage indexation.

In short:
Only selected roles should be able to decide whether an asset becomes indexable. All other users should not see this option at all.

1. Business Value / Rationale This feature supports security, compliance, and brand governance in environments where both public and internal-only assets coexist in the same DAM. Benefits include:

Preventing accidental exposure of intranet or sensitive internal images to search engines
Ensuring consistent and controlled SEO/indexing behavior for public-facing asset libraries
Eliminating user errors by removing unnecessary decisions from non-expert users
Supporting enterprise governance by limiting indexing decisions to authorized roles
Reducing risk of data leakage and compliance breaches

This aligns with common DAM best practices where search engine indexation rights are restricted, similar to publishing permissions in CMS platforms.

We suggest the ability to configure which roles can see the “Enable search engine indexing” checkbox.
Ability to configure which roles can edit the indexation setting.
For users without permissions, the control must be completely hidden (not greyed out).
Default behavior should maintain backward compatibility.

Related support ticket: #1836823

1. Priority & Urgency Priority: High Reason: Incorrect handling of indexation presents a data exposure risk, particularly for internal/intranet content. Role-based control is essential before onboarding more users and expanding asset usage.