This document explains what end customers need to have in place to install and use the Oversai Chrome extension in a production environment. It intentionally excludes development-only details and focuses on clarity for IT, security, and network teams.
The extension is distributed via the official Chrome Web Store:
https://chromewebstore.google.com/detail/okegfpidgpgamjbdfacikffcgbkiadfa
1. System Requirements
Requirement | Details |
|---|---|
Browser | Google Chrome (latest stable version recommended). |
Operating System | Any OS officially supported by Google Chrome (Windows, macOS, Linux). |
Hardware | No special hardware requirements. Any standard workstation capable of running Chrome is sufficient. |
Installation | Users install the extension directly from the Chrome Web Store. No side-loading or developer mode is required. |
IT note: If your organization restricts Chrome extensions, the Oversai extension must be added to the approved allowlist in your Chrome policies.
2. Configuration Requirements
There is no manual configuration required by end users.
All environment-specific settings (such as backend endpoints and authentication configuration) are already embedded in the production build published in the Chrome Web Store.
From the client perspective: - Users simply install the extension and sign in. - No environment variables, keys, or technical parameters need to be set or maintained by the customer.
This design avoids local configuration errors and simplifies deployment across teams.
3. Network Requirements
The extension requires outbound HTTPS access to specific production services in order to function correctly.
3.1 Required outbound access
Ensure that firewalls, proxies, or secure web gateways allow outbound HTTPS (TCP 443) traffic to:
Purpose | Destination |
|---|---|
Oversai Web Application & Login | https://so.oversai.com/* (or your official Oversai production domain) |
Authentication (Clerk) | Official Clerk authentication domain used by Oversai (e.g. *.clerk.com or a custom Clerk domain) |
Oversai Backend APIs | AWS API Gateway endpoints used by Oversai (e.g. *.execute-api.us-east-1.amazonaws.com) |
Exact domains can be confirmed with Oversai support if your security policy requires explicit allowlisting.
3.2 Proxy and inspection considerations
If your organization uses a corporate proxy, ensure Chrome extensions are permitted to make outbound HTTPS requests.
If SSL/TLS inspection is enabled, it must not interfere with:
Authentication flows (Clerk)
Secure API calls to Oversai backends
Certificate substitution or blocking may prevent users from signing in or retrieving data.
3.3 Inbound traffic
No inbound network access is required.
The extension only initiates outbound connections.
4. Security Requirements
4.1 Chrome extension permissions
The Oversai extension requests only the minimum permissions required to operate:
Host access to Oversai production domains and authentication services.
Local storage to cache session state and user permissions.
Cookies (scoped) for authenticated sessions on approved domains.
Background scheduling for session and state management.
The extension does not request unrestricted access to all websites.
4.2 Authentication and data handling
User authentication is handled via Clerk, using standard browser-based sign-in.
The extension does not store user passwords.
Authorization data (roles and permissions) is retrieved securely from Oversai APIs and cached locally for a short period (minutes) to optimize performance.
All communication uses HTTPS encryption in transit.
4.3 Corporate security considerations
Area | Notes |
|---|---|
Extension approval | Add the Oversai Chrome extension to your approved extension list if policies restrict installations. |
Data in transit | All traffic is encrypted using HTTPS. |
Data at rest | Limited, non-sensitive session data is stored locally in Chrome’s extension storage. |
Compliance reviews | The extension can be evaluated like any standard SaaS browser extension used for internal operations. |
Endpoint protection | No elevated OS permissions or native binaries are installed. |
Summary for IT & Security Teams
Users only install the extension from the Chrome Web Store.
No development, build, or environment variables are required on the client side.
Allow outbound HTTPS access to Oversai, Clerk, and associated API domains.
Approve the extension in Chrome policies if extensions are restricted.
This document is intended to remove ambiguity for security and network reviews and clearly separate client responsibilities from internal development configuration.
Still need help?
Contact us