Getting SN Utils Approved in Your Organization

Many organizations centrally manage browser extensions. If SN Utils is blocked on your work device, your IT or security team may need to review and allow the extension before you can use it on a corporate ServiceNow instance.

This guide brings together the standard information needed for that review. It does not bypass your organization's policies or guarantee approval; the final decision always belongs to your organization.

Recommended Approval Path

1. Choose the correct extension version for your ServiceNow domains.
2. Share the review links on this page with your IT or security team.
3. Ask your browser administrator to allow the official store listing and the required site access.
4. Run a limited pilot, preferably in a ServiceNow PDI or non-production instance first.
5. Purchase Pro or request a quote once your organization is comfortable with the deployment.

Choose the Correct Extension

SN Utils is available through the official stores for Chrome, Edge, Firefox, and Safari. Use the install page to select your browser and open the correct store listing.

The two versions use the same product code and provide the same features. Their host-permission scope is different. The regular version is the easiest version to approve when all instances use standard ServiceNow domains.

On Edge, Firefox, and Safari, the regular version also supports *.servicenowservices.com. Chrome does not support those domains with the regular extension. Safari does not have an OnPrem version. See Installing SN Utils for browser-specific details.

Restricting Which Sites a Chrome Extension Can Access

Chrome provides site-access controls on both Windows and macOS:

• Individual browser setting: From the extension's Details page, a user can select On select, On specific sites, or On all sites, unless the organization manages that setting. This is a user-side control over which sites the extension may read or change. See Google's Install and manage extensions guide.
• Managed browser policy: Administrators can enforce extension-specific runtime blocked hosts and runtime allowed hosts on managed Chrome browsers for Windows and macOS. For an allowlist-style restriction, block all hosts (*://*) and add only the approved ServiceNow host patterns as allowed exceptions. An allowed-host entry by itself does not block the extension's other declared hosts. See Google's Prevent Chrome extensions from altering webpages guide and ExtensionSettings policy reference.

These controls can narrow access within the extension's declared host permissions. They cannot grant access to a host that the installed extension version does not support, so the organization still needs to choose the correct regular or OnPrem build.

Information for IT and Security Review

Use these authoritative pages instead of copying information into a separate document that can become outdated:

Important Review Points

• SN Utils runs in the user's browser and interacts with ServiceNow under that user's existing permissions. It does not provide elevated ServiceNow access or bypass server-side ACLs.
• ServiceNow credentials and session tokens are not sent to SN Utils. Core extension features process ServiceNow page content locally. Optional connected features may transmit user-authored content or content the user explicitly submits, such as synced snippets or AI prompts, as described in the linked privacy and data-handling references.
• Pro features can connect to snutils.com for license validation and optional cloud functionality. Users can keep resources and usage data local by changing the documented privacy controls.
• AI features are Pro-only, are triggered by an explicit user action, and can be disabled centrally for a team. Review the dedicated AI data-handling page for the exact payloads and sub-processors.
• ScriptSync can optionally use a local WebSocket connection to 127.0.0.1 for communication with the VS Code helper. Organizations that do not use ScriptSync do not need that workflow.

Managed Browser Deployment

Your browser administrator normally controls the exact deployment process. A typical managed rollout is:

1. Open the official store listing through the SN Utils install page.
2. Record the store URL and extension ID shown by the browser store.
3. Add that official extension ID to the organization's Chrome or Edge extension allowlist.
4. Decide whether installation is optional for approved users or force-installed for a managed group.
5. Apply only the site access required for the organization's ServiceNow domains. For managed Chrome deployment, use runtime host policy to block all hosts and allow only the approved ServiceNow host patterns. Treat the individual browser setting as a supplementary user-side control, not as the centrally enforced policy.
6. Pilot the policy with a small user group before wider deployment.

SN Utils does not provide or recommend a policy-bypass installation. Managed organizations should deploy the signed build from the official browser store using their normal browser-management tooling.

Suggested Pilot

A small pilot keeps the review proportionate and gives your organization evidence from its own environment:

1. Start with one or two ServiceNow professionals.
2. Use a PDI or non-production instance for the first functional check.
3. Confirm the selected extension version only runs on the intended domains.
4. Review optional cloud, usage-data, and AI settings before enabling them.
5. Test the specific SN Utils workflows your team intends to use.
6. Document the browser policy and configuration before expanding the rollout.

Using SN Utils successfully in a personal PDI does not mean it has been approved for a corporate environment. Corporate use must still follow your organization's browser-extension, security, and ServiceNow policies.

Copyable Internal Approval Request

You can adapt the following message for your IT, security, or browser-management team:

Subject: Request to review and approve the SN Utils browser extension

I would like to use SN Utils, a browser extension that improves productivity for ServiceNow professionals.

Requested extension version: [SN Utils regular / SN Utils OnPrem]
Official store listing: [paste the URL from https://snutils.com/install]
Required ServiceNow domains: [list the corporate ServiceNow domains]
Requested users or pilot group: [list the users or group]

The vendor's security, privacy, browser-permission, AI, and procurement information is available here:
https://snutils.com/docs/getting-started/organization-approval

Please review the official store build and, if acceptable, allow it for the pilot group under our standard managed-browser policy.

Do not include ServiceNow credentials, session tokens, production data, or other sensitive information in the request.

If Approval Is Declined

If your organization decides not to approve SN Utils, I would appreciate learning the high-level reason. If you can share it without disclosing confidential information, please create a support ticket and choose Other as the category.

The feedback may reveal a concern I can mitigate through a product change, clearer documentation, or a different deployment option. It also helps me understand the security, privacy, and operational requirements that matter to organizations. Sharing the reason does not create any obligation to reconsider the decision or purchase SN Utils Pro.

Help With Approval or Purchasing

If your organization is genuinely considering an SN Utils Pro purchase, you may always create a support ticket. You can ask for help with:

• Choosing between the regular and OnPrem extension
• Finding the relevant security or privacy information
• Clarifying browser permissions or product data flows
• Working through a blocker in the internal approval process
• Selecting the appropriate purchase or quote route

Choose Other as the ticket category and include your organization, browser, required ServiceNow domains, approximate number of users, and the question blocking approval. Do not include credentials or confidential ServiceNow data.

Purchase Options

• View Pro pricing for individual and standard team subscriptions.
• Request a multi-seat quote when procurement or Accounts Payable needs a formal quote or invoice.
• Create a support ticket when an approval question is blocking a genuine purchase.