BlandAI

BlandAI

Govern Bland AI with Corma: owner, admin, operator and viewer roles, enterprise SSO without SCIM, restricted API keys that outlive members, usage billing.

The Corma and Bland AI integration keeps your Bland organization and its members in line with the teams who build and run your AI phone agents. Bland describes itself as an enterprise voice AI platform for high-volume, regulated and complex phone workflows, used by healthcare networks, insurance carriers, financial services firms and logistics operators. Bland charges for the resources consumed across voice, SMS and other interactions, so the governance question is who can launch calls and change your agents.

Key takeaways

  • Bland's member API accepts four permission values, owner, admin, operator and viewer, and adds or removes members by user ID, phone number or email.
  • Only an owner or admin of a Bland organization can create an API key, and a Bland API key works until it is deleted.
  • A restricted Bland API key keeps working after the member who created it leaves the organization, changes role or is banned.
  • Bland supports OIDC and SAML 2.0 single sign-on for enterprise workspaces, while SCIM is on its roadmap and users are provisioned just in time.

What keeps working after a Bland member leaves?

Restricted keys outlive their creator. Bland's API key documentation states that a restricted key can only call the endpoints its permissions cover, and that it keeps working when the member who created it leaves the organization, changes role or is banned. Bland suggests restricted keys for contractors, CI jobs and integrations. Bland documents no rotate endpoint for API keys, which work until deleted, while OAuth client access tokens last one hour.

Call data needs the same attention. Bland's organization settings set call-recording retention through recording_lifespan_days, between 1 and 1,825 days, or -1 to disable retention, and new phone numbers have recording enabled by default. Audit logs are an enterprise feature not yet available for all accounts. On the pricing page, SSO sits on the Enterprise plan, next to a BAA and data residency.

How Corma governs Bland AI

  • Owners and admins under review: owners and admins, who can create API keys, go into automated access reviews.
  • Leavers with a key check: a leaver workflow in the IT Workflow Builder asks an owner or admin to review and delete the API keys the person created, then to remove them from the organization.
  • API keys with an owner: API keys and OAuth clients are non-human identities, so each one needs a named owner, starting with restricted keys handed to contractors.
  • Usage in the budget: Bland's usage-based charges count as AI spend, which AI spend management helps you budget and forecast.

Frequently asked questions

Does Bland AI support SSO and SCIM?

Bland supports OIDC and SAML 2.0 single sign-on for enterprise workspaces, with identity providers such as Okta, Azure Active Directory, Google Workspace and Auth0, and users are provisioned just in time on first login. SCIM support is on Bland's roadmap. Bland's SSO page gives two different default roles for users without a matching group, viewer and operator. Read what just-in-time provisioning covers.

How does Corma connect to Bland AI?

Through Bland's Update Organization Members API where it fits, which adds or removes members by user ID, phone number or email, or through Corma's browser-based agents in Bland's organization settings. See also how Corma covers AI platforms such as OpenAI Platform.

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 every Bland leaver's API keys reviewed before they go? Book a Corma demo.

Related Integrations

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