# 2026

## May 20, 2026

### The Cerby API got a boost

We're thrilled to announce a massive expansion of the Cerby API! Our latest updates deliver comprehensive new capabilities, making it simpler than ever to manage items, users, and collections programmatically. We’ve introduced new endpoints for seamlessly sharing accounts with users or teams and a full suite of collection management tools.

These enhancements also deepened the information available in the account schema and introduced robust listing and management for collections and integrations. We're continuously working to give you the most flexible and detailed access to the Cerby platform. For a complete list of all the exciting new endpoints and changes, check out the [Cerby API release notes](/updates-and-releases/cerby-api/2026.md).

### Seamless access with Google SSO

Cerby now supports associating Google single sign-on (SSO) identities with your managed accounts. This enhancement lets you leverage your existing social login configurations to enable secure, fully automated access to your apps.

Whether you have configured Google SSO personally or the account was provisioned by an Identity Provider (IdP) like Okta, Cerby identifies the login method during the authentication flow. Through the Cerby browser extension, you can now autosave these accounts and set Google SSO as the preferred login method, ensuring that future automated logins bypass manual prompts and prioritize your social identity.

**Figure 1** shows the experience in a web browser and the Cerby browser extension.

<figure><img src="/files/bgVxK4YHnvuMppNCQYSe" alt=""><figcaption><p>Figure 1. Account with SSO login added popup of the Cerby browser extension</p></figcaption></figure>

For instructions on how to associate SSO with an account, read the article [Add an account with Google SSO as your preferred login method](https://help.cerby.com/cerby-browser-extension/accounts/managing-your-accounts/add-an-account-with-google-sso-as-your-preferred-login-method).

### Proactive service account health monitoring

Cerby now surfaces service account misconfigurations, such as incorrect credentials or unmanaged MFA, directly in the business hub details page, so you can identify and resolve issues before they disrupt your automations. You can see clear health indicators the moment a service account needs attention, along with the specific reason it was flagged.

When a misconfiguration is detected, Cerby guides you through the resolution with step-by-step instructions tailored to the issue, whether that's updating credentials or enabling Cerby-managed MFA. If you believe the flag was set incorrectly, a **Try Anyway** option lets you override it: Cerby will temporarily lift the flag, re-attempt the job, and only reapply it if the issue persists.

**Figure 2** shows an example of the banners that Cerby displays in the business hub details page when an associated service account has misconfiguration issues.

<figure><img src="/files/TBKcjldG0EoAQ3oH8DtX" alt=""><figcaption><p>Figure 2. Banner for a misconfigured service account in the business hub details page of the Cerby web app dashboard</p></figcaption></figure>

### Fixes

* The issue where guest users' first and last names were not stored in the database upon their first login has been fixed. Because the registration data wasn't being persisted correctly, guest user records appeared without names, affecting audit trails and reporting. Now Cerby correctly stores guest users' names during their initial login, ensuring complete and auditable user records.
* The issue where guest users were unable to log in on the web and mobile in SSO-enabled workspaces has been fixed. Because the routing logic directed guest users to the workspace's identity provider rather than the credential form, they were effectively locked out. Now Cerby correctly redirects guest users to the standard username and password form, regardless of the workspace's SSO configuration.
* The issue with Meta Business Manager asset access not being automatically revoked in some cases after removing team access has been fixed.
* The issue with TikTok business hub invites and member syncs failing during certain role changes has been fixed. TikTok returns "null" values for finance roles that Cerby did not handle, so permissions fell out of sync, and share attempts failed.
* The issue of duplicate configurations being created after swapping the service account for a business hub has been fixed.
* The issue with Meta Business Manager asset-sharing jobs completing successfully in Cerby but not reflecting changes in the Meta Business Suite has been fixed. Now, Cerby ensures that asset-sharing changes are accurately reflected in Meta before marking the job as complete.
* The issue of some teams not receiving asset access when a business hub was shared has been fixed.

### Security fixes

* We hardened the logic that manages workspace roles to prevent owners from accidentally downgrading their own access levels, safeguarding against orphaned accounts.

***

## February 13, 2026

We closed Q4 2025 with a final round of enhancements and a new way of staying in touch. We are excited to announce that our [**Support Portal**](https://support.cerby.com/) is now available for submitting tickets directly to our Technical Support team. This portal enables you to create and track your support requests in a centralized and streamlined way.

If you require visibility into all tickets within your workspace, beyond those you have personally submitted, please reach out to your **Customer Success (CS) manager**. They are also available to assist with any questions regarding new releases between our quarterly updates.

### Security fixes

* We’ve upgraded our login security to further protect customer privacy. Our systems now provide generic feedback during the login process to Cerby, ensuring that sensitive information about your workspace remains invisible to unauthorized parties.
* We enforced our multi-factor authentication (MFA) requirements for guest and local users. Now, they cannot add, view, or update accounts and secrets in any of our client apps (Cerby web app, browser extension, and mobile app) if they haven’t turned on MFA for their Cerby account.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.cerby.com/updates-and-releases/whats-new/2026.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
