Skip to Content
Enterprise domain restrictions

Enterprise domain restrictions

If your company runs an enterprise ChatGPT workspace, your admins can control which third-party connectors your people are allowed to use — and they can restrict each connector to your company’s own email domain (for example, only people with an @acme.com address). Voris now supports this, so Voris can be approved and listed for enterprise ChatGPT.

This page explains what that means for you, what you’ll see when you connect, and exactly what is — and isn’t — shared.

What “domain restriction” means

Enterprise ChatGPT lets an admin say, in effect: “Only people on our company email domain may connect Voris.” To enforce that, ChatGPT needs to confirm, at the moment you connect, that you’re signing in with a company email — for example that you’re a real @acme.com user and not a personal account.

For ChatGPT to check that, the connector has to tell ChatGPT your verified email during sign-in. Until now Voris couldn’t do that, so ChatGPT wouldn’t list Voris for enterprise workspaces. Voris now provides your verified email during the connect handshake, which is what unlocks enterprise approval.

What you’ll see when you connect

When you connect Voris from ChatGPT, you sign in with your Voris account as usual. Before anything is shared, Voris shows you a consent screen that clearly states your email address will be shared with the connector. Nothing is shared until you approve on that screen.

After you approve:

  • If your email is on a domain your company’s ChatGPT admin has allowed, you’re connected.
  • If it isn’t, ChatGPT declines the connection. That check happens inside ChatGPT, using the email Voris confirmed — Voris doesn’t decide who’s allowed; your own company’s ChatGPT settings do.

Your Voris email counts as verified because of how you sign in to Voris in the first place — by magic-link or with Google or LinkedIn — so there’s nothing extra for you to verify.

What is shared — and what is not

Connecting shares only your own identity: your email address and the fact that it’s verified. That’s the entire purpose — to let your company confirm you’re on an approved domain.

Connecting does not expose any of your analytics. Your visits, visitors, conversions, top pages, AI visibility — none of your dashboard data is shared by the act of connecting. Sharing your email to satisfy a domain restriction is completely separate from giving an assistant read access to your data, and one never implies the other.

If you also want an AI assistant to read your analytics (a normal, read-only connection), that’s a separate choice you make when connecting — see Connecting AI assistants. Even then, the assistant only ever gets read-only access to the one site you pick, and never your settings or billing.

Connecting AI assistantsPrivacy modes