Govern Bliro with Corma: Note Taker and Sales Assistant licenses, Admin and Member roles, suspend or delete, SSO without SCIM, an org-wide API scope.
The Corma and Bliro integration keeps your Bliro organization, its licenses and its members in line with the sales teams who use it. Bliro, based in Munich, describes itself as an AI platform for B2B field sales teams whose core product is the voice agents Vicky and Tim. It began as a privacy-first AI notetaker. Bliro is licensed per person, so licenses and recorded calls both need an owner.
Admins have two choices. Bliro's article on data and account deletion explains that suspending a member removes their access right away while their meetings, notes and transcripts stay, and that deleting a member permanently deletes all of them. Bliro documents no way to transfer a departed member's meetings to someone else. Its help articles also disagree on licenses: one says a suspended member's license stays reserved, another says it returns to the pool.
Data and API access are organization-wide. Transcripts are hosted on Microsoft Azure servers in Frankfurt, and only organization admins can set automatic transcript deletion, which keeps summaries and analyses. Bliro's API Access uses OAuth 2.0 client credentials set up by administrators, and a new application gets a single scope, org:calls:read, covering all calls in the organization. Anyone who signs up with an email domain not linked to an organization gets their own new organization with one Note Taker license.
Bliro names Microsoft Entra ID, Google Workspace Identity or Cloud Identity, and Apple as single sign-on providers, and its help center lists SSO under the Enterprise offering. Bliro's SSO article does not mention SAML, and SCIM is currently not supported. Read how to offboard apps without SCIM, SAML or SSO.
Bliro's API reference documents member endpoints, but a newly created client application automatically gets one scope, org:calls:read, so Corma's browser-based agents can handle member steps on the Members page, in an isolated browser session with credentials taken from your password vault. See also how Corma covers Avoma.
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 decide what happens to a Bliro leaver's calls before access ends? Book a Corma demo.
Check out other integrations that could help you on managing your software licences and accesses!