Skip to content
English
  • There are no suggestions because the search field is empty.

Set up your team

Summary

This onboarding step completes when a teammate you invite accepts, or when you connect your AI provider key, whichever fits where you are right now. It completes for your whole organization, whoever does it. Both live under People & access and Integrations respectively, and either one is enough to mark the step done.

Before you start

Inviting a teammate needs the Manage Users permission, and you need to know their email address and which role to give them. Connecting an AI provider key needs the Manage Tenant permission and an API key from your provider (currently Anthropic).

Available on every plan: nothing in this step depends on your subscription.

Option A: Invite a teammate

  1. Go to People & access → Users.
  2. Enter the person's email address and choose a role for them.
  3. Send the invite.

They receive an email invitation and can sign in once they've accepted it. You can resend or revoke a pending invitation, and disable or re-enable a user, from the same page; each action asks for confirmation first.

Know which action actually removes access. Revoking stops a pending invitation working. Once someone has accepted, the invitation can't be revoked, so Revoke isn't offered on their row. Disable the user to stop them signing in; that ends their active sessions immediately. Deleting is separate again, and cannot be undone.

Resending issues a fresh accept link and stops the previous one working. If someone has two invitation emails, only the newest link works.

Set who may register, and how long sessions last

Go to People & access → Sign-in & domains to set the organization-wide policy:

  • Anyone from our domains: anyone with an email from an allowed domain can sign in and auto-register. People outside those domains still need an explicit invite.
  • Invite only: nobody self-registers; every account starts as an invitation.
  • Allowed email domains, comma-separated.
  • Session timeout, 1-720 hours. It applies on next login, so changing it does not shorten sessions already running.

The domain list does two jobs. As well as dashboard self-registration, it governs which employees can self-enroll an endpoint sensor: and it does that regardless of registration mode. Keep it current even in invite-only, or endpoint self-enrollment will be rejected. See Add your first device.

Option B: Connect your AI provider key

Use this option instead if you don't have a teammate to invite yet, or if setting up assistive features (drafting DLP rules, classifying content, generating compliance narrative drafts) is the more useful first step for you.

  1. Go to Integrations → AI provider.
  2. Enter your API key.
  3. Test the key before saving: this confirms it's valid without committing to it yet.
  4. Save.

Once connected, you can optionally choose which model handles each supported AI task. An inference policy lets you narrow how the key is used (restrict to self-hosted models only, or disable a use entirely): it can only narrow what your plan permits, never widen it. The key itself is encrypted at rest; if you come back to check it later, you'll see a short fingerprint rather than the full value. You can disconnect it at any time.

Confirm it worked

  • After inviting a teammate: they appear in the Users list with a Pending or equivalent status until they accept, then move to active.
  • After connecting a key: the AI Provider section shows it as connected, with the fingerprint visible in place of the full key.

If it didn't work

  • Invite not received: check the email address for typos first; resend the invite from the Users list rather than sending a new one, then make sure they use the newest email.
  • They accepted but still can't sign in: check whether the account is disabled. A disabled account cannot sign in regardless of the invitation's state.
  • Revoke isn't offered for someone: they've already accepted their invitation. Disable the user instead.
  • Someone can't self-register: check the registration mode first: in invite-only nobody self-registers, whatever the domain. If it's self-service, confirm their exact domain is on the allowed list.
  • Key test fails: the most common cause is a key that's been revoked or rotated on your provider's side since you copied it. Generate a fresh key from your provider and try again.
  • Can't find these settings at all: this usually means your role doesn't include Manage Users (for invites) or Manage Tenant (for the AI provider key). Ask whoever administers your organization to grant it, or to complete this step on your behalf.

Related

  • Add your first device