When creating an app for someone, it would be great if they could somehow be limited to only viewing the app, rather than logging in to ArcGIS.com with their username and seeing all of the content behind the app.
My use case that I've created an app in Web AppBuilder with a custom widget. This widget restricts how a user can edit data in a hosted feature layer, only allowing certain options for that user. The feature layer has to be shared with the user for this to work.
Even though I've only given users the URL of the app itself, some users have enough knowledge to directly access the feature layer in AGOL and edit the layer directly, bypassing the editing restrictions
Please we need that functionality as soon as possible.
We have a hosted layer with data on jobs done by contractors and we have a filtered dashboard for each contractor.
But if a contractor logs into AGOL with his username can see the information of other contractors simply by accessing the layer that uses the dashboard.
Is there another solution other than creating 15 views of the hosted layer and 15 identical dashboards?
@BernSzukalski - Sharing to a group does not solve the issue - we need to block people from seeing the ArcGIS.com landing page all together - @MartínGonzález gives a good example of the issue as well. I want a user to only see their app - no other views on ArcGIS.com. If they have a username and search the link given to them for the app instead of putting it in their URL bar- the search result directs them to ArcGIS.com, where they log in and get confused because they don't see their app. They see the dashboard landing screen of ArcGIS.com. @KenBuja also gives a good example.
@DanSmith27 It is possible to completely mask off a contractor or volunteer from all organization content by creating a custom role and placing the contractor in a private group with _only_ what you want that contractor to see and use in that group. I actually just prototyped this the other week for a non-profit that wanted to have a couple of volunteers as members in their org to use Survey123 but did not want them to see any other content within the organization. It does work (though with a couple of minor caveats WRT JSAPI 4.X and public sharing).
Though I've not exercised all possibilities, this should cascade out to what's visible on the Home page and throughout the sharing /Online ecosystem. But public things are public, and always discoverable. I'll see if I can exercise this quickly on my ArcGIS Online Labs home page.
@DanSmith27 I still had the custom role set up for my test user and just took a look at this using my home page. Only public content is visible to this user on my Home page after they sign in, or if I had shared only the content in their private group on the home page they would see that as well. No organization content is visible. This include groups.
And to be clear, I am not opposed to this idea, just trying to find something you might find workable now.
In our case it is not about hiding a layer or not from the logged in user. Rather, it is related to the data in the same layer.
The tractors and machines that work in the field send information that we receive with geoevent and post-process with spatial analysis geoprocesses, generating areas and activities worked. The result of this process is shown in a dashboard filtered by contractor. But we have the security problem that we mentioned in the previous post.
We need a more efficient way to protect each contractor's information.
Unlike the information created in BernSzukalski's example, in our case the information is generated by the server and not by the user. In the case that the information is generated by the user, there are filters in the Feature Layer, so that users can see their own data and not others.
But as I mentioned before, the information is generated by a centralized process in our case and we can't use that option.
It would be great to be able to block user access to the feature layer used by the dashboard, this would protect the information and that it can only be accessed from an app, in our case with ArcGIS Dashboards.
Basically, it creates an ArcGIS Online item that a) points back to the original layer, b) has a username/password saved that can see that layer and c) is limited to only be open-able by URLs you specify.
After you configure the map and app, limit the layer's access to just the app's URL. After that, the map will not display the layer if you open in directly, but the layer WILL show normally in the app.
Once it's configured, the end user sees the new "layer" as an AGOL feature service, but they'll get an error if they try to see the data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
