What’s New
Enhanced Governance Workflow Stages, Statuses
-
We’re excited to announce support for extended set of granular Governance Workflow stages and statuses. We’re updating Credo AI with enhanced AI Governance Workflow features & best practices to more accurately represent our customer’s real world AI Governance journey. The enhanced Workflow is customizable for your specific AI Governance Process, enables tracking AI Use Cases through multiple governance workflow stages, audit changes to use cases and much more.
-
With this update, you can better track individual evidence gathering, assessments and task assignments across AI lifecycle stages such as Intake, Governance and intermediate stages specific to your organization.
-
API Changes: The “governance_status” field is being deprecated in favor of “workflow_stage_id” and “workflow_stage_step” fields in all Credo AI APIs. “workflow_stage_id” refers to Governance Stage ID, and “workflow_stage_step” to name of statuses ('assessment', ‘evidence_collection’, 'clear')
External User Portal Usability Improvements
-
To better reflect the broader usage of the platform, we’ve renamed the "Vendor Portal" to "External User Portal." This terminology aligns with our vision of enabling collaboration with various external stakeholders beyond vendors.
- The updated URL for External users is https://external.credo.ai. Please note that https://vendor.credo.ai has been deprecated and will redirect to the External user portal.
-
New feature for External Users to submit final responses to Governance Leads: We’re introducing a “Submit” feature for External Users responding to questionnaires on the External User Portal (formerly known as Vendor Portal). This enhancement addresses feedback from Governance Leads regarding the clarity and finality of questionnaire responses. The “Submit” feature will update a date timestamp that tells Governance Leads when the answer was finalized.
Azure SaaS Deployment
-
Credo AI now supports option for deployment on Azure SaaS. Our customer can choose between hosting their Credo AI tenant on AWS or Azure based on their organization’s preference.
SCIM APIs for Bulk User Management
-
We’re excited to announce the rollout of SCIM (System for Cross-domain Identity Management) APIs to our SaaS platform. The SCIM 2.0 compliant REST APIs enable seamless, standardized, and automated user provisioning and deprovisioning for enterprise customers, along with syncing user attributes such as name, email, group membership and others. These APIs are designed to work out-of-the-box with leading IdPs (Identity Providers).
Updates to AI Registry View
-
AI Registry UI filters will persist if user navigates away from and returns to the AI Registry UI within the same Credo AI session.
Policy Packs
-
Updated EU AI Act Policy Packs: We have made updates to several EU AI Act Policy Packs to reflect the latest version of the legal text.
-
Updated OMB Guidance Policy Pack: We have made updates to our OMB Policy Packs, including deprecating our old OMB Guidance for Federal Use of Safety- and Rights-Impacting AI and replacing them with an updated Pack that reflects the latest OMB guidance to U.S. federal agencies.
-
New Kentucky Senate Bill 4 Policy Pack: We have operationalized Kentucky Senate Bill 4, which regulates the use of AI in government in the state of Kentucky, as a Policy Pack. Please contact your Customer Success manager if you’re interested in getting access to this Pack in your tenant.
Bug Fixes
-
Admins can’t edit user information for other users: we fixed a bug where admin users previously had an option to edit user information (i.e. nickname, job title, etc.) for other users, but they couldn’t click “save”; this has been fixed and Admins can now update and save user information.
-
Download & delete buttons for uploaded files are missing for long file names: we fixed an issue where the download and delete buttons next to uploaded files (attachments) were not displaying due to long file names.
-
Pagination fails on the Teams page: we fixed a bug where the Teams page within the Settings section of the platform was only displaying the first 30 entries; now, pagination works such that you can see additional Teams beyond the first 30 in new pages.
-
Manually removing a Policy Pack added by an action breaks all triggers & actions: we fixed an issue where manually removing a Policy Pack added by an automation (an action from a questionnaire trigger) was causing other triggers & actions for that Use Case to stop working.
-
Risk scenarios added via actions don’t revert when the triggering question answer is changed: we fixed an issue where changing the answer to a triggering question didn’t revert the action that answer triggered when the action was related to adding a risk scenario to a Use Case.
-
Link from email notification for adding or removing users from a Use Case leads to 404: we fixed an issue with a broken link in an email notification that users received when they were added to or removed from a Use Case as a stakeholder.