Skip to main content
Back to Help

IT allowlisting and network access

Most teams can use Nomic from a standard browser with no special network setup. If your organization uses a restrictive firewall, proxy, VPN, SSL inspection tool, or email security gateway, share this checklist with your IT team before a kickoff or pilot.

Web access​

Allow browser access over HTTPS (443) to:

  • Your Nomic tenant, for example <your-org>.drive.nomic.ai (Business and Enterprise)
  • app.nomic.ai (Individual plan)
  • docs.nomic.ai, if your users need access to the public docs

Nomic uses long-lived HTTPS connections while Assistant and workflows stream progress back to the browser. If responses appear to hang, stop mid-answer, or only update after a refresh, ask IT to confirm that proxies and browser security tools are not buffering or blocking streaming responses from your tenant.

Authentication email​

If your organization uses email login codes or invite links, allow mail from:

  • no-reply@nomic.ai

If multiple users do not receive invites or login codes, the messages may be filtered before reaching individual inboxes. For larger rollouts, SSO is usually more reliable than email codes.

SSO​

SSO is available on Business and Enterprise. If your organization uses SSO, confirm:

  • Users are assigned to the Nomic application in your identity provider.
  • The email address in the identity provider matches the email invited to Nomic.
  • Users are signing in through your company identity provider, not a personal email flow.

Connected file systems​

For integrations such as SharePoint, Egnyte, Autodesk Forma, or other file systems, users also need access to those systems. Nomic respects the source system's permissions and cannot show a user files they could not otherwise open.

If a connected system is behind a company network policy, confirm with your Nomic account team whether any additional integration-specific setup is required.

What to send Nomic Support​

If login works but Assistant or workflows do not stream reliably, send:

  • Your tenant URL
  • Browser and operating system
  • Whether the issue happens only on VPN, office Wi-Fi, or a managed device
  • A screenshot of the frozen or delayed run
  • The approximate time the issue happened

This helps separate product issues from network filtering or proxy behavior.