Publishing an AI Card Without a Request

Introduction

If you need to proactively share an AI Card with a Cranium user, you can publish it without waiting for a request. Cranium facilitates the publication of an AI Card directly from an AI System or via the AI Manager Quick Actions, allowing for the selection of specific artifacts for sharing. This guide outlines the steps to publish an AI Card to any external organization.

Preconditions

AI System Created

You must have an AI System created before you can publish an AI Card. If you haven't added one yet, go to the AI Manager and click Create AI System to get started.

Bills of Materials & Documentation Attached

To publish artifacts with an AI Card, they must first be attached to the AI System. After generating a Bill of Materials, you must attach it to the AI System. Similarly, Documentation must be attached to the AI System after it is uploaded to your Document Library. You can attach these artifacts using the Add Artifacts button in the AI System Details.

Vulnerability Reports Generated

To attach a Vulnerability Report to an AI Card, you must first generate the report from the Vulnerability Assessment tab in the AI System. Once generated, it becomes available as an artifact that can be added to the AI Card.

Compliance Frameworks Completed

To attach a Compliance Framework to an AI Card, all fields in the framework must be completed. Only fully completed frameworks are eligible for inclusion as artifacts.

Entry Points

AI System Manager

From the AI Manager, click the Publish AI Card button in Quick Actions to begin the publishing process.

AI System Card

From the AI System Card, locate the relevant AI System and click the Publish button on the card to begin the publishing process.

AI System Details

From the AI System Details page, click the Publish New AI Card button and select To Organization to begin the publishing process.

Instructions

The AI Card publishing process consists of three straightforward steps. First, you’ll select the recipient organization to receive the AI Card. Next, you’ll configure attachments by selecting which artifacts from the AI System to include, such as Bills of Materials, Documentation, Compliance Frameworks, and Vulnerability Reports. Finally, you’ll review your selections and confirm the details before publishing the AI Card to the chosen recipient.

1. Select Recipient Organization

Select the Recipient Organization from the dropdown and click the blue Add button.
If this is your first time publishing to a particular organization, scroll to the bottom of the Recipient Organization dropdown and select the blue Add new recipient organization text.
The form will expand, allowing you to input the organization's name and the contact details of the user who will receive the AI Card.
Click the Continue button to move on to the card configuration.

2. Configure AI Card Attachments

The AI System field is pre-populated with the current AI System.
Enter a unique Published Name for the AI Card.
Select the Compliance Framework(s), Bill(s) of Materials, Vulnerability Reports, and Additional Documentation to attach to the AI Card.
Once you have completed the configuration, click the blue Continue button to move on to the last step.

3. Review & Publish

For the last step, review the published version of the AI Card prior to submitting.
The dialog will display the recipient organization's contact information and the attached artifacts.
Once you have reviewed the AI Card, click the blue Publish button to publish the AI Card.

Next Steps & Related Actions

Recipients with Existing Cranium Accounts

If the recipient of your AI Card has an existing Cranium account, they will receive an email notification that the card has been shared.

Recipients without Existing Cranium Accounts

If the recipient of your AI Card does not have an existing Cranium account, they will receive an email notification that the card has been shared and instructions on how to create an account to accept the card.

Outdated AI Cards

When you first share an AI Card, its status is marked as Up-to-date in the Published Cards tab. Once you make any changes to the published artifacts (i.e., change framework responses or rescan a BOM) the status will change to Out-of-date.

Did this answer your question?