Configure allowed domains to control where Pointer can be used.
Pointer only works on domains you explicitly approve. This ensures your widget is used securely and only on your authorized websites.
Configure your allowed domains in the Pointer dashboard:
Outside of local development environments, Pointer automatically blocks requests from domains that are not explicitly allowed. This security measure prevents:
When adding domains to your allowed list, include:
yourdomain.com
)staging.yourdomain.com
)When you add a domain like yourdomain.com
, all subdomains (such as app.yourdomain.com
, docs.yourdomain.com
, etc.) are automatically allowed. You don’t need to add each subdomain separately.
localhost
and local IP addresses are automatically allowed during developmentLocal development environments (localhost, 127.0.0.1) are automatically allowed and don’t need to be explicitly added to your domain list.
Behavioral controls are available for users on the Growth plan and above.
Growth plan users can selectively disable guides (second cursor walkthroughs) on any of their allowed origins. This provides fine-grained control over where interactive guidance appears.
Common use case: If you want to add Pointer to both your product and documentation site, you may only want guides to appear in your product interface, not on your documentation pages.
Pointer automatically disables guides in the following scenarios:
docs.
(e.g., docs.yourdomain.com
)/docs
in the path (e.g., yourdomain.com/docs/getting-started
)For custom domain setups or specific requirements:
You can mix and match guide settings across different domains. For example, enable guides on app.yourdomain.com
while keeping them disabled on docs.yourdomain.com
. In the case above, we’ve disabled guides on pointer.so
and docs.pointer.so
, but left them enabled on app.pointer.so
.
Use specific domains
Add only the exact domains where you deploy Pointer:
Test configuration
Verify domain settings work correctly:
Regular maintenance
Keep your domain list current:
If the Pointer widget fails to load on your website:
http://
and https://
versions may need separate entriesexample.com
vs anotherdomain.com
) need separate entriesAlways test widget functionality after adding or modifying domains in your allowed origins list.