BrightEdge User Management API Guide

Auth method: Not documented

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: Not documented

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Not documented

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No publicly documented webhook system for user-management events was found.

• Alternative event strategy: User provisioning is managed manually via the BrightEdge admin UI or through SSO/IdP integrations (Okta, Entra ID, OneLogin) at the Enterprise tier.

• SCIM available: No
• SCIM version: Not documented
• Plan required: Enterprise
• Endpoint: Not documented

Limitations:

• No public SCIM endpoint documented by BrightEdge.
• The Okta integration catalog does not list SCIM provisioning as a supported feature for BrightEdge.
• User lifecycle management appears to require manual admin action or SSO-only (JIT provisioning) at the Enterprise tier.
• Confirmed absence of SCIM support based on available public documentation as of research date.

Three scenarios cover the realistic surface area for BrightEdge user management. For provisioning, JIT via SAML SSO (Okta, Entra ID, OneLogin) creates an account on first login - but role assignment still requires a manual step in the BrightEdge admin UI post-login.

For deprovisioning, revoking IdP access blocks SSO login but does not remove the BrightEdge account; a separate manual deactivation in the admin UI is required. For bulk operations, no public API exists - all bulk changes require manual UI work or direct coordination with BrightEdge support.

Provision a new user via SSO (JIT)

1. Configure SAML SSO with your IdP (Okta, Entra ID, or OneLogin) through the BrightEdge Enterprise admin settings.
2. Assign the user to the BrightEdge application in your IdP.
3. User logs in via SSO for the first time; BrightEdge creates the account via just-in-time provisioning.
4. Admin assigns roles/permissions within the BrightEdge UI after first login.

Watch out for: JIT provisioning only creates the account on first login; deprovisioning must be done manually in BrightEdge or by revoking IdP access (which blocks login but may not delete the account).

Deprovision a user

1. Revoke the user's access to BrightEdge in your IdP to block SSO login.
2. Log in to BrightEdge admin UI and manually deactivate or remove the user account.
3. Confirm removal of any shared reports or dashboards owned by the departing user.

Watch out for: Without SCIM, deprovisioning is not automated. Revoking IdP access alone does not remove the BrightEdge account; manual admin action is required.

Bulk user management

1. Contact BrightEdge account team or support to request bulk user import/export options.
2. Use the BrightEdge admin UI for individual user role changes.
3. No API-based bulk operation is publicly documented.

Watch out for: No public bulk user management API exists. All bulk operations require manual UI work or coordination with BrightEdge support.

Engineering teams evaluating BrightEdge for automated identity workflows should treat the absence of SCIM and a user management API as a hard constraint, not a roadmap item - there is no public indication either is forthcoming.

If your stack is managed through an MCP server with ~100 deep IT/identity integrations, BrightEdge will sit outside that automation layer entirely, requiring a manual exception process. Any SEO data API access is a separate engagement with BrightEdge account teams and is unrelated to user lifecycle management.