Skip to content
Documentation

Inviting users to complete a DISC assessment

DISC profiles are created by inviting users to complete a short assessment. This assessment is provided by a dedicated psychometric provider.

This page explains how invitations work, what data is involved, and how the results become available to SotsAI.

How invitations work (high level)

Section titled “How invitations work (high level)”

The invitation flow is simple:

  1. An organization admin selects one or more users
  2. SotsAI sends a secure email invitation
  3. The user completes a DISC assessment
  4. A psychometric profile becomes available to your organization via API

Each completed assessment consumes one DISC credit.

Who can be invited?

Section titled “Who can be invited?”

You can invite any user for whom you want a psychometric profile, for example:

  • employees
  • managers
  • collaborators
  • external stakeholders (if relevant)

The only required identifier is an email address.

No application account or login is required on your side.

Invitation constraints

Section titled “Invitation constraints”

To keep the system predictable and abuse-resistant:

  • invitations are sent by email only
  • up to 20 invitations per request
  • invitations are idempotent per user per organization
  • completing an assessment consumes exactly one credit

If a user is invited twice and has already completed the assessment, no additional credit is consumed.

What the user experiences

Section titled “What the user experiences”

From the user’s perspective:

  • they receive an email invitation
  • they complete a short DISC questionnaire
  • they receive an email from SotsAI containing a secure link to access their DISC report
  • no SotsAI account is created for them

SotsAI does not expose raw results back to the user.

What data is stored

Section titled “What data is stored”

SotsAI stores only what is required to fetch and reuse the psychometric profile:

  • a deterministic external identifier derived from the organization ID and a one-way hashed email
  • no raw assessment answers
  • no free-text input
  • no personal metadata

How this integrates with your LLM

Section titled “How this integrates with your LLM”

Invitations are typically triggered when:

  • profiles are missing
  • a feature requires behavioral reasoning
  • you want to pre-equip teams before rollout

A common pattern is:

  1. Detect missing profile(s)
  2. Invite the relevant user(s)
  3. Handle the current request without calling SotsAI
  4. Enable SotsAI-based reasoning once profiles are available

For detailed fallback strategies, see:

Next steps

Section titled “Next steps”