Search

Auto-ISAC Supplier Instance Creation

Users can create a new supplier instance directly from the TRACK instance, without needing to submit a support ticket. This article provides an overview of how to create a supplier instance, the automatic actions triggered during the process, and the safeguards in place to prevent duplicate suppliers or instances.

This article covers the following topics:

 

Creating a Supplier Instance

  1. From the TRACK instance, go to the Vendor module. 
  2. Click Create Instance. Create Supplier Instance_1.png
  3. In the Create Instance window, enter the following information:
  • Supplier Name (required) — start typing to search for an existing vendor in your instance. Create Supplier Instance_2.png
  • Primary Contact (required) — this person becomes the supplier's admin user. Enter their First Name, Last Name, and Email. Create Supplier Instance_3.png
  • Additional Contacts (optional) — click Add Additional Contacts to enter First Name, Last Name, and Email for any other contacts. Each additional contact can be removed using Delete Additional Contact.Create Supplier Instance_4.png
  1. Click Create Instance. This button stays disabled until all required fields are filled out. Create Supplier Instance_5.png

Note: This feature is property-controlled and is only available in BlueVoyant TRACK instance.

Monitoring Supplier Instance Creation Status

After the user clicks Create Instance, a toast notification tracks the status of the instance creation process. You can expand, minimize, or close the notification — it stays expanded until you close it. You'll see one of the following statuses:

  • In Progress — "[Supplier Name] instance creation in progress." Monitoring Supplier Instance_1.png
  • Completed — a checkmark and the supplier name. Monitoring Supplier Instance_2.png
  • Error — "[Supplier Name] instance creation was unsuccessful. Please try again. If the issue persists, contact support."

Supplier Instance Activation

Once a supplier instance is created successfully:

  • The Primary Contact and any Additional Contacts receive a registration email inviting them to complete a custom Auto-ISAC registration screen, which includes the MNDA as the company's agreement.  Email.pngRegistration.png
  • The Primary Contact and Additional Contacts are added as users under the new supplier company. Supplier Users.png
  • The supplier is added as a Vendor in the Vendor Connect instance, with the Primary and Additional Contacts added as contacts on that Vendor record.
  • You (the user who created the instance) receive a confirmation email letting you know the instance is ready and that you can publish the assessment.

The new supplier instance is automatically configured with the modules and settings your organization uses for Track Program suppliers, including Portal Assessments, Answer Library, Issues, File Library, and Analytics.

Duplicate and Conflict Safeguards

A few safeguards help prevent duplicate suppliers, instances, and contacts:

  • Existing users: If the Primary Contact or any Additional Contact already has a guest CENTRL account or already belongs to a subscribed company, clicking Create Instance displays an error and blocks instance creation: "The following users either have an existing guest CENTRL account or already belong to a subscribed company. Remove them and try again."
  • Existing vendor records: If the supplier you enter already exists as a Vendor in your instance, a warning appears: "[Vendor Name] already exists in your company. We'll create their instance, replace the existing primary contact, and merge any additional contacts into the existing record." You can still proceed — the system merges the new contacts into the existing Vendor record instead of creating a duplicate. If a contact you entered already exists under that Vendor, it's skipped rather than duplicated.
  • Mismatched contact domains: If an Additional Contact's email domain doesn't match the Primary Contact's domain, a warning appears on that contact: "This contact's email domain doesn't match the primary's domain ([primary.domain]). Confirm you intend to add this contact before proceeding." This warning appears for each Additional Contact with a mismatched domain, but you can still proceed with instance creation.