Set Widget Visibility Before Installing The Snippet
Mark
Set Widget Visibility before Installation
Description:
Allow users to choose who can see the Marker.io widget before installing the snippet. This will enable customers to restrict widget visibility to specific users from the start.
Use Case:
Currently, the widget is visible to everyone by default after installation, requiring manual adjustments to limit visibility. Allowing visibility settings before installation will enhance security and user experience by ensuring only intended users have access immediately.
Benefits:
- Control who sees the widget before installation.
- Improve security by limiting access from the start.
- Simplify installation, reducing the need for post-installation adjustments.
This feature will make the Marker.io widget more user-friendly and secure, meeting customers' visibility preferences from the beginning.
Log In
m
markus
Hi Gary. I think a better way to phrase this feature request would be the ability to set up default project settings when creating a new project. Right now we have no control over this and each project has to be updated individually based on our preferences when it is created.
One of the options I would like to preset would be the Visibility options and always having the hidden option selected (accessible by ?bug).
The reason I want to default to hidden is I work on live sites and production sites that are then pushed live within a short time frame.
I've already had a few instances when launching a new site or when first installing the widget that the visibility settings hasn't been updated and the widget is visible on the live site which I want to avoid at all costs.
In order to prevent this I would prefer to just be able to set my own default settings for projects that adhere to my preferences. Please also note you can't even edit visibility settings until the widget itself has been verified. So you have to create the project -> install the widget -> verify the widget -> update visibility settings. That's a lot of steps just to adjust this one setting and sometimes it gets missed unfortunately.
By allowing for default settings you can essentially skip this whole process and have it function better right out the gate.
Hopefully that all makes sense, please let me know if you have additional questions, happy to provide additional insight as needed.
Gary Gaspar
markus: Thanks a lot for your feedback! This is useful context and everything makes sense and goes in line with what we want to build.
Gary Gaspar
Hey Mark, I have some questions around your need to hide the widget from all your site.
1- Why do you hide it? Even more so, why do you hide it when it's installed on a staging URL?
2- How do you trigger Marker.io if the widget is hidden? Do you use a the secret URL parameter (?bug)? or the keyboard shortcut? Something else?
Our assumption is that people don't need to hide the button is most case. So curious to learn more