Braze

Braze

Govern Braze with Corma: permission sets, workspace roles and Teams, suspended or deleted users, SAML SSO, SCIM by edition, REST API keys kept after users.

The Corma and Braze integration keeps your Braze dashboard users and their permissions in line with the teams who send your messages. Braze describes itself as the leading customer engagement platform, and the company was called Appboy until November 16, 2017. A Braze contract is built from a Platform Edition, Monthly Active Users and Profiles, and Action Credits, so the governance question is who can reach your audiences and change your messaging.

Key takeaways

  • Braze controls dashboard access with permission sets across all workspaces, roles in specific workspaces and, on contracts that include them, Teams that limit the audiences a user can reach.
  • Suspending a Braze user blocks login but preserves the data associated with the account, and only administrators can suspend or unsuspend company users.
  • Deleting a Braze dashboard user keeps their campaigns, segments and Canvases, but the Created By field of those assets then shows a null value.
  • When a Braze dashboard user is deleted, Braze does not delete the REST API keys that user created.

What stays behind when a Braze user leaves?

Braze's guide to managing company users explains that deleting a dashboard user does not significantly affect the campaigns, segments and Canvases they created, although their Created By field then shows "null". Braze's REST API documentation adds that deleting a user does not delete the API keys that user created. A key's permission scope and allowlisted IPs cannot be edited after creation, and Braze documents no expiry for REST API keys.

Braze describes user management in two ways. The company users guide says administrator permissions are required to add users, while the permissions page says limited users with the "Edit Dashboard Users" permission can create other limited users. Creating and updating API keys depends on the "Edit API Keys" permission. Administrators can download a Security Event report, a CSV of account invitations, removals and login attempts, for internal audits.

How Corma governs Braze

  • Permissions under review: administrators and users holding "Edit Dashboard Users" or "Edit API Keys" go into automated access reviews.
  • Leavers with a key check: a leaver workflow in the IT Workflow Builder asks an administrator to review the REST API keys the person created, then to suspend or delete their dashboard account.
  • REST API keys with an owner: REST API keys are non-human identities, so each one needs a named owner.
  • Contract in view: the Braze contract and its renewal date sit in SaaS subscription management.

Frequently asked questions

Does Braze support SSO and SCIM?

Braze supports SAML 2.0 single sign-on with Microsoft Entra ID, Okta and OneLogin. Its SSO documentation says Google SSO and SAML SSO are available for Pro and Enterprise customers, while the pricing page lists SAML and SSO among the features included in every tier. SCIM provisioning depends on your platform edition, and Braze allows one SCIM integration per company: Okta or Entra ID, which create and delete accounts automatically, or its own SCIM API endpoints. Read what SCIM automates.

How does Corma connect to Braze?

Through Braze's custom SCIM endpoints where they fit, which can look up a dashboard user by email and delete one, but are unavailable alongside an Okta or Entra ID integration, or through Corma's browser-based agents in the Braze dashboard. See also how Corma covers Klaviyo.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to see who can still edit your Braze users and API keys? Book a Corma demo.

Related Integrations

Check out other integrations that could help you on managing your software licences and accesses!