JUjumpcloud
Access Certification

Update access certification settings

Creates or replaces your access certification settings. Send the full settings object — partial updates are not supported.

Use this endpoint to:

  • Enable or disable Access Certification (featureEnabled)
  • Configure notification platforms and which lifecycle events each destination receives

Disabling Access Certification (featureEnabled false) requires that no campaigns are Active. When disabled, all Scheduled campaigns with config.enabled true are set to inactive (config.enabled false) and will not auto-start until manually re-enabled after the org feature is turned back on.

API operations for listing and viewing campaigns, finalizing runs, remediation, reassign, and audit download and sign-off remain available while Access Certification is disabled. Only creating and activating campaigns (and reviewer notifications) are blocked.

The Admin Console may prompt you to re-enable the feature; that experience is separate from API behavior described here.

Notification destination IDs reference channels configured in JumpCloud Notifications.

Required permission: accesscertification (Full Access)

put/api/v2/access-certification/settings

Request

Request body

featureEnabledboolean required

Master switch for Access Certification. When false:

  • Reviewer notifications are paused and User Portal campaign access is hidden
  • Creating and activating campaigns returns 409 Conflict
  • All Scheduled campaigns with config.enabled true are set inactive on disable
  • Disabling returns 409 Conflict while any campaign is Active
  • Viewing campaigns, finalizing runs, remediating, reassigning, and downloading or signing off audit reports remain available while the feature is disabled
  • Re-enabling does not auto-activate previously disabled Scheduled campaigns

Response

Updated access certification settings

featureEnabledboolean required

Master switch for Access Certification. When false:

  • Reviewer notifications are paused and User Portal campaign access is hidden
  • Creating and activating campaigns returns 409 Conflict
  • All Scheduled campaigns with config.enabled true are set inactive on disable
  • Disabling returns 409 Conflict while any campaign is Active
  • Viewing campaigns, finalizing runs, remediating, reassigning, and downloading or signing off audit reports remain available while the feature is disabled
  • Re-enabling does not auto-activate previously disabled Scheduled campaigns

Changes

No recorded changes to this operation across all 1 revision of this API.