> ## Documentation Index
> Fetch the complete documentation index at: https://docs.visotrust.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Inviting Your Team

> Invite users to VISO TRUST, assign Admin, Program Manager, Contributor, or Viewer roles, designate business owners, and set default notification routing.

Getting your team into VISO TRUST early means better coverage, clearer ownership, and fewer gaps in your risk program. This page covers how to invite users, assign roles, and set up default notification behavior.

## Inviting a User

<Steps>
  <Step title="Go to Settings → Users">
    In the left sidebar, select **Settings**, then select **Users**.
  </Step>

  <Step title="Click Add User">
    Enter the user's name and email address, check **Invite to VISO TRUST**, and select their role: **Admin**, **Program Manager**, **Contributor**, or **Viewer**.

    Not sure which role to assign? See [Role-Based Access](/getting-started/roles-and-permissions).
  </Step>

  <Step title="Send the invitation">
    The user receives an email with a link to set up their account. If they don't receive it, ask them to check their spam folder or contact [support@visotrust.com](mailto:support@visotrust.com).
  </Step>
</Steps>

<Note>
  If your organization uses SSO, users will be redirected to your identity provider when they log in. SSO must be configured by an Admin before users can authenticate this way. See [SSO / Okta Configuration](/organization-settings/sso).
</Note>

## Assigning Business Owners and Assessment Leads

Once a user is in the platform, you can designate them as the **Business Owner** or **Assessment Lead** of specific relationships. These are not roles — they are per-relationship designations that grant a Contributor edit access on that relationship. See [Role-Based Access](/getting-started/roles-and-permissions#relationship-designations) for how each designation affects permissions.

To assign a Business Owner or Assessment Lead:

1. Open the relationship from the Relationships page
2. Open the **Relationship configuration** dialog using the gear icon
3. Select a user from the **Business Owner** or **Assessment lead** field

You can also set these designations when creating a new relationship, or assign them across many relationships at once from the Relationships list page using the **Assign assessment lead** and **Assign business owner** bulk actions. Each relationship can have a different person in each designation — the two are fully independent.

## Default Subscribers

A **Default Subscriber** is a user who is automatically subscribed to every relationship in the platform — existing and future. This is useful for centralized risk or compliance teams who need full visibility across the vendor portfolio.

To enable Default Subscriber for a user:

<Steps>
  <Step title="Go to Settings → Users">
    Find the user you want to configure.
  </Step>

  <Step title="Open user settings">
    Click the three-dot menu next to the user and select **Edit**.
  </Step>

  <Step title="Enable Default Subscriber">
    Check the **Default Subscriber** box and select **Save**.
  </Step>
</Steps>

Once enabled, that user is immediately subscribed to all existing relationships and any new ones going forward.

<Warning>
  A Default Subscriber cannot be removed from an individual relationship without first disabling the Default Subscriber setting on their user profile.
</Warning>

You can have multiple Default Subscribers. Good candidates include:

* Centralized risk or compliance teams
* Security operations centers (SOCs)
* Audit and governance teams

## Managing Subscribers on Individual Relationships

Outside of Default Subscribers, you can manually add or remove subscribers on any relationship. Open the relationship, open the **Relationship configuration** dialog using the gear icon, and manage the **Subscribers** list there. To update subscribers on many relationships at once, select them on the Relationships list page and use the **Manage subscribers** bulk action to add or remove users across the selection.

Subscribers receive notifications for:

* Assessment status changes
* Risk advisories and breach alerts
* Remediation requests
* Lifecycle events (expiring documentation, upcoming recertifications)

<Tip>
  Think of Subscribers like "watchers" on a ticket — they stay informed without being responsible for the relationship. Use them to give stakeholders visibility without granting edit access.
</Tip>