Back
Teams & Enterprise // Security & Sign-in
Security & Sign-in
Docs › Teams & Enterprise › Security & Sign-in
Security & Sign-in
Verified domains, single sign-on and automatic provisioning. Set up by owners and admins on the dashboard's Security page.
How people sign in
- Everyone uses their NOVA account: GitHub or Google, as usual, in NOVA, NOVA CLI and the dashboard.
- With single sign-on on, people at your verified domains can choose Continue with SSO on the sign-in page and enter their work email; NOVA sends them to your identity provider and back.
- With Require it on, people at your domains can only sign in through SSO. Other sign-ins are refused with a message explaining what to do.
- Accounts are matched by email, so someone who signs in through SSO keeps the same NOVA account, projects and history.
Verify your domain
1
Add the domain
Security › Verified domains: enter your company domain, for example
acme.com, and select Add domain.2
Add the TXT record
At your DNS provider, add a TXT record on the domain itself with the value shown, which looks like
nova-verification=….3
Verify
Select Verify. DNS can take a few minutes to update. Once verified, turn on Auto-join if colleagues should join automatically when they sign in.
A domain can be verified by one organisation only. Public email domains (gmail.com and similar) can't be used.
Single sign-on
| Provider | Plans | What you enter |
|---|---|---|
| Google Workspace | Teams, Enterprise | Nothing: only Workspace accounts on your verified domains are accepted |
| Microsoft Entra ID | Teams, Enterprise | Your directory (tenant) ID or tenant domain, like acme.onmicrosoft.com |
| SAML (Okta and others) | Enterprise | Your identity provider's entity ID, sign-in URL and signing certificate |
Setting up SAML
- In your identity provider, create a SAML app for NOVA using the Entity ID (audience) and Single sign-on URL (ACS) shown on the Security page, or its metadata URL.
- Send the email address as the NameID.
- Paste your provider's entity ID, sign-in URL and signing certificate into NOVA, turn on Single sign-on, and Save.
- Test with one person before turning on Require it.
Automatic provisioning with SCIM (Enterprise)
- Security › Automatic provisioning: Turn on and make a token. Copy the SCIM base URL and the token (shown once) into your identity provider's provisioning settings.
- People assigned to the NOVA app are added to your organisation; unassigning or deactivating them removes them, and their projects are handed over as usual.
- Only addresses at your verified domains can be provisioned, and only while you have seats. The owner can't be removed by SCIM.
- Making a new token stops the old one. Turn off stops provisioning.
Data and privacy
Bridgeye doesn't train models on your code. Each request goes to the model provider that answers it, under that provider's terms; the privacy policy lists everyone involved. Invitation links, SCIM and usage API tokens are stored only as fingerprints. Enterprise customers can also choose where NOVA itself runs.
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.