Cortex Search refresh history: MONITOR privilege grants access (Pending)¶
Attention
This behavior change is in the 2026_07 bundle.
For the current status of the bundle, refer to Bundle history.
Access to the CORTEX_SEARCH_REFRESH_HISTORY
table function is expanding to roles with the MONITOR privilege on a Cortex Search Service.
This change provides read-only access to refresh history without requiring the broader OPERATE
privilege.
- Before the change:
Roles with the
OWNERSHIPorOPERATEprivilege on a Cortex Search Service could accessCORTEX_SEARCH_REFRESH_HISTORY. TheMONITORprivilege didn’t grant access.- After the change:
When the 2026_07 behavior change bundle is enabled in your account, roles with the
MONITOR,OPERATE, orOWNERSHIPprivilege on a Cortex Search Service can accessCORTEX_SEARCH_REFRESH_HISTORY. This change is additive: no existing access is revoked.
What you should do¶
No action is required for roles that already have the OPERATE or OWNERSHIP privilege.
To grant read-only observability access to refresh history without granting the broader OPERATE
privilege, grant MONITOR on the Cortex Search Service:
To see which roles have privileges on the Cortex Search Service:
To revoke the MONITOR privilege:
For information about who can grant privileges, see Access control requirements.
To grant MONITOR automatically on new Cortex Search Services in a schema, use a future grant:
Additional notes¶
MONITORprovides read-only access to refresh history.OPERATEis required to suspend, resume, refresh, or change a Cortex Search Service.MONITORalso grants access to Cortex Search request logs whenREQUEST_LOGGINGis enabled. Access toCORTEX_SEARCH_REFRESH_HISTORYdoesn’t requireREQUEST_LOGGINGto be enabled.
Ref: 2411