Skip to main content
With single sign-on connected, people in your organization sign in to the Valar console through your identity provider, such as Okta, Microsoft Entra, or Google Workspace. With SSO sign-in for ValarCode on, engineers sign in to their coding tools the same way, without a coding key.

Connect your identity provider

Only admins can set up SSO, and you need admin rights in your identity provider.
  1. Open Settings → Sign-in & SSO (under Access).
  2. On the Single sign-on row, click Set up SSO. A setup page opens.
  3. Pick your identity provider and follow the steps on the page. They tell you what to create in your identity provider and what to paste back.
Once the connection is active, the Single sign-on row reads Connected. To change or disconnect it later, click Manage SSO on the same row.

Who can sign in

Anyone your identity provider lets in on one of your verified domains joins your organization the first time they sign in, even without an invite. Two settings under Settings > Sign-in & SSO control what happens next:
  • Approve new SSO members: newcomers wait until an admin approves them under Settings > Team members.
  • Role for new SSO members: the role newcomers get, Member (the default), Read, or ValarCode Viewer. People who are already members keep their role.
To have your directory groups set everyone’s role instead, see Roles from directory groups.

Next steps

  • Connect your directory so Valar sees your groups, and a deactivation in your identity provider ends a person’s access.
  • Turn on SSO sign-in for ValarCode so engineers sign in to their coding tools through your identity provider instead of holding a coding key.