> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/updates-and-releases/cerby-web-app/2026.md). # 2026 This article describes the newest features, enhancements, and bug fixes to improve your experience using the Cerby web app. ### September 21, 2026 #### New features and enhancements * Admins can now update an IdLCM integration's name and business ID directly from the integration settings page. Previously, these values were immutable after the integration was created. * The dialog box for editing a role on a business hub now supports secondary roles for integrations that assign users more than one role at a time. Role changes for multi-role users are applied correctly to all assigned roles. This functionality was supported in the classic view, and now is supported in the new view. * The **Business Hubs** page now displays a clear error screen when a user does not have permission to view a resource or when the resource fails to load, instead of a blank page. * The **Replace account** button in a business hub is now disabled for users who are not **Owners** of the currently associated service account. An info banner communicates the restriction clearly, preventing a confusing failure state where users could start the flow but hit an opaque error. * We improved the access reliability for re-invited users in a business hub. If a user is re-provisioned shortly after being removed, Cerby now ensures invitations and access permissions process in the correct sequence. Re-invited users will seamlessly keep their access without unexpected revocations or invitation conflict errors. #### Fixes * We fixed an issue where the **Copy** button for a password occasionally became unresponsive in the account details page. * We fixed an issue where automations for granting access to Facebook Business Manager assets could get permanently stuck when a permission was matched to a Cerby identity but access was never confirmed on the app side. Jobs now correctly re-attempt the access grant or fail visibly. * The **Activity** page now correctly attributes manually triggered password rotations to the user who triggered them. The affected account is also identified in the activity event. * We fixed an issue where TikTok account cards displayed random credential type values instead of the username. *** ### August 21, 2026 #### New features and enhancements * Dynamic fields in the dialog box where you share access to a business hub now support multi-select. When a field accepts multiple values, you can select multiple options, addressing a gap for integrations that use dynamic fields with multi-value inputs. * The account details page now shows whether the last password rotation was triggered manually by a user or run automatically by a policy. The record includes the rotation date and the name of the person who initiated it. When the rotation was automated, Cerby is shown as the actor. This distinction makes it straightforward to separate policy-driven rotations from user-initiated ones during access reviews or incident investigations, without having to cross-reference the **Activity** view. * The version history was added for server-generated RSA key bundles. Admins can now view version history for an account's server-generated RSA key bundle (public key, private key, passphrase), matching the existing password-history feature. * Self-deleting secrets now support an expiration window of up to 60 days, with 30 days as the default. Previously, the maximum expiration was 30 days. #### Fixes * Disabled users (for example, when deactivated through Okta) are no longer shown in team member listings or account member listings. These users are now filtered from these listings by default. If a disabled user is reactivated, their membership is automatically restored. * The Cerby web app no longer crashes with browser-native translation enabled. * User names now display correctly in search results when a query returns user-type records. * The infinite loading issue that occurred when some users attempted to log in to a business hub was fixed. *** ### July 17, 2026 #### New features and enhancements * The **Automation Log** page is now the default experience for all workspaces. The legacy dashboard has been deprecated. * Workspace **Admins**, **Super Admins**, and **Owners** can now view deleted secrets on the **Secrets** page using the new **More filters** > **Deleted secrets** option. These items are displayed with the **Deleted** chip. * The dialog box for matching a business hub user now displays an error when the process couldn't be completed because the user already had a matched record. Business hub **Owners** and **Managers** must use the re-link flow instead. * When a business hub **Owner** or **Manager** changes a user's role in an external app through Cerby, the web app now shows a message with the **View activity** button for opening the Automation Log instead of displaying a success message box. It now correctly reflects that the role change is processed as an automation job. * Users with the "Pending user claim" status no longer show the **Manage access** or **Manage assets** options in their action menu in the business hub and asset user tables, reducing confusion for admins managing unclaimed accounts. * The Automation Log now shows the identity source for password rotation reverts — for example, if they were triggered by a user or by an automated process. * The following enhancements were released for the Azure Key Vault feature: * When an Azure Key Vault key is rotated, or a decryption failure occurs, the **Vault management section** in the **Privacy and security** tab of the workspace settings now loads and displays a status indicator instead of returning an error. This allows IT admins to see which vaults need attention without the entire page becoming unavailable. * Cerby now supports updating the key ID on Azure Key Vault credentials, which is required after completing a key rotation. * Azure Key Vault decryption now falls back to older key versions when the current version cannot decrypt stored data. For example, after a rotation where the prior wrapping key was disabled. * When a user is removed from a business hub, Cerby now correctly downgrades (rather than fully revokes) their access on assets where they have a direct external app assignment. Users retain **Collaborator** access on those assets instead of losing all access. * Entitlement roles are now automatically updated during sync when an external app's role configuration changes. Previously, entitlements retained stale roles until they were manually recreated. * API-based asset invites now grant business hub-level access in Cerby regardless of whether the invite to the external app succeeds. Users are no longer left without access when an invite fails on the first attempt. * Rate limit retry logic now applies to the automation jobs for adding, removing, and updating user roles, improving resilience during high-concurrency provisioning operations. * The **My Connected Accounts** tab in the business hub details page has been redesigned. When no accounts are connected, the section shows an **Add account** button; when accounts are present, the section displays a **Your connected accounts** section with separator lines between accounts. #### Fixes * The issue where the **App access** column showed empty values in the **Business Hubs** tab of the user details page was fixed. Now, Cerby displays **Full access**, **Partial access**, or **No access**, enabling accurate permission audits. * The issue with business hub **Managers** being unable to be added as users in the **Users** tab of the business hub details page was fixed. **Managers** and external users are now correctly treated as separate roles and can both be invited. * The issue with displaying the incorrect login type flag for Meta Business Manager in the business hub details page was fixed. For example, **SSO** is displayed for Meta Work accounts, and **Username and password** is displayed when using Facebook profiles, fixing broken invite links for users. * The issue where the **Collaborator** role wasn't applied to all eligible users after a business hub sync in workspaces with multiple user assignment types was fixed. * The issue where some users couldn't see Meta Business Hub assets they had access to was fixed. Affected users will see their assets restored after the next sync. * The issue with an infinite loading spinner being displayed when users attempted to log in to a business hub was fixed. * The issue where business hub account cards incorrectly redirected to the classic view instead of the new UI was fixed. * The issue where **Collaborator**-level users who clicked the **Assets** tab in a Google Ads or DV360 business hub were incorrectly redirected to the **Settings** tab was fixed. * The issue where the **Business ID** and **Username** columns in the new business hub view displayed the same values for Google DV360 and Google Ads integrations was fixed. * The issue where guest users lost their workspace role when their user account was disabled, making them non-functional after re-enabling, was fixed. *** ### May 20, 2026 #### New features and enhancements * We’ve optimized Meta Business Manager sync performance by up to 90% using a new user-centric fetching approach that significantly reduces API calls. * Ad accounts can now be shared directly during the team invitation flow in TikTok, eliminating the need for users to manually claim assets after being invited. * The user sync process for Meta Business Manager now handles large-scale accounts more reliably, using a smarter fetching strategy and automatic retry logic to ensure all users are retrieved. #### Fixes * The issue where an account was automatically removed from a collection due to server timeout was fixed. This error happened when trying to update the entire account list instead of just adding the newly created account. * The issue with the Azure Key Vault details page failing to load when credentials expired was fixed, enabling users to update expired credentials without being locked out. * The issue with account notes and custom fields not appearing in the account details page was fixed. * The issue with screenshots not being rendered correctly in the **Automation Log** page using Safari was fixed. * The issue with business hub **Owners** being unable to promote already-assigned users to the **Manager** role was fixed. The dialog box for assigning a new role did not support changes for existing members; therefore, **Owners** had to delete and re-add users just to change their role. * The issue with the service account selection list for business hubs being limited to 50 results was fixed. Now, Cerby displays the full list of owned accounts in the selection dropdown. * The issue with shared Google Ads Manager assets not appearing for guest users was fixed. Now, Cerby displays shared assets through a new **Assets** tab in the business hub details page. * The issue with the **Business ID** field of a business hub rejecting special characters like “@” was fixed. This restriction was affecting business hubs with email-based identifiers. *** ### February 13, 2026 #### New features and enhancements * We disabled the **Rotate password** button on the account details page for accounts that use Google single sign-on (SSO) for authentication. * We now display chips in the list of apps within the **App setting restrictions** page to indicate which restriction types were activated. #### Fixes * The issue with being able to assign the **Team Admin** role to a **Guest User** via an API request was fixed, matching the behavior in the user interface (UI). * The issue with being able to downgrade the role of a workspace **Super Admin** to an **Admin** was fixed. * The issue with Snapchat Ads assets not being correctly shared with IdP-managed teams was fixed. * The issue where automation job error logs would display broken image links for non-existent screenshots was fixed. We now validate that error screenshots are successfully stored before generating access links in the Automation Log. * The issue where accounts would still be displayed as orphaned in the Security Hub even after a new owner was assigned and the page was refreshed was fixed. The orphan flag is now automatically updated upon owner assignment, ensuring accurate real-time reporting of account security status. * The issue of not removing access to assets in an external app after a team member’s removal from a business hub was fixed. * The issue where some account names are missing from the table of messages in the Shared Inbox was fixed. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.cerby.com/updates-and-releases/cerby-web-app/2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.