03-14-2024 10:17 AM
Hi,
Hi,
When I host a WebVI, I need to define the users who can access it and their privileges. I created a "visitor" user who could only view the page without interacting with other things.
In additionr, in order for them to see the page, I need to allow them to access web applications (they can see every WebVI I hosted; I can create a workspace for each WebVI so they only see the WebVI I want, but I need to change every other tag workspace). Moreover, it's not interesting for the "visitor" user to be able to do anything other than viewing the page and its hyperlinks.
If I uncheck any of these privileges, the user can't access the page or can't see the tags being plotted.
These are the only privileges I'm using.
If I'm not mistaken, with SystemLink Cloud, you could do this, where you shared the link and they could only see the pages.
I'm not sure if I'm doing something wrong or forgetting something.
Thanks in advance.
Solved! Go to Solution.
03-18-2024 08:01 AM
Giving more context,
This is what appears, when i open a link from the "visitor" user, after i login with it's credentials.
if i click in web applications, i can see every other one.
03-18-2024 10:23 PM - edited 03-18-2024 10:39 PM
I can create a workspace for each WebVI so they only see the WebVI I want, but I need to change every other tag workspace
If you have multiple workspace support in your installation (a feature of SystemLink Server Advanced Licenses), you should be able to use the Use Workspace VI to have a have the Open Configuration session point to a specific workspace:
That way you can:
For users only using features included with G Web (which does not include multiple workspace support) then the behavior you have seen is expected as there is only a single workspace for the hosted WebVIs. If there are some WebVIs that users do not have the full permissions to use (for example they have not been given permissions for all the tags needed by a specific WebVI), then that WebVI should have good error handling to instruct the user that they do not have the needed permissions and how to request them, etc.