Controlling who can see the Vynix widget

You can limit who sees the Vynix widget by controlling when the widget script loads on your site. The safest approach is to show it only to approved users, roles, or environments.

1. Decide who should have access, such as developers, QA testers, admins, or users in a private beta.
2. Add a condition around the Vynix widget install code so it only runs when the current user or environment is allowed.
3. Use your existing access logic where possible, such as logged-in user roles, feature flags, workspace settings, or environment checks.
4. Avoid loading the widget script at all for users who should not see it. Hiding it with CSS is not enough.
5. Test with both allowed and blocked accounts to confirm the widget appears only where expected.

Vynix works by adding a lightweight widget to your website. If the widget script is loaded, users may be able to open it and create annotations. To limit visibility, place the install snippet behind your own access checks instead of adding it globally to every page.

Common options include showing Vynix only in staging, only for signed-in team members, only for admin roles, or only when a feature flag is enabled. For example, your app can check the current user's role before rendering the Vynix snippet.

For production sites, use server-side or application-level checks when possible. This helps prevent the widget from being sent to users who should not have access. Client-side checks can be useful for convenience, but they should not be your only control if access is sensitive.

If you are using a tag manager, make sure the tag trigger follows the same rules. Do not publish the Vynix tag on all pages unless everyone who can visit those pages should see it.

For the latest install options and configuration details, see the Vynix documentation at https://vynix.in/docs.