Forum Discussion
MCFNeil
7 years agoQrew Captain
Setting up an "Open to the Internet" or a "single sign-on" is a good way to help share information with clients.
However, you want to make sure that user experience is good for them so they feel confidence in you and your product. The especially comes into account for mobile users (one area where native QB falls short).
If you want to 'log' who uses it, I'd suggest that the 'landing page' be a very simple form that they fill out as a passage. Then once saved it redirects them to the report or dashboard that you want them to see.
(Using linkaway is helpful here)
Also sometimes a better user experience is to hide the QB headers, and/or use an <iframe> on your website.
Keep in mind that users have 100% access to any code pages, or dashboards you have in the app, so you will want to be cautious of things you have in the app and feel comfortable with their 'access'
However, you want to make sure that user experience is good for them so they feel confidence in you and your product. The especially comes into account for mobile users (one area where native QB falls short).
If you want to 'log' who uses it, I'd suggest that the 'landing page' be a very simple form that they fill out as a passage. Then once saved it redirects them to the report or dashboard that you want them to see.
(Using linkaway is helpful here)
Also sometimes a better user experience is to hide the QB headers, and/or use an <iframe> on your website.
Keep in mind that users have 100% access to any code pages, or dashboards you have in the app, so you will want to be cautious of things you have in the app and feel comfortable with their 'access'