idea AGOL “View As User” Mode for Role-Based Testing in ArcGIS Online Ideas

AGOL “View As User” Mode for Role-Based Testing

vmnblack_wsp — Tue, 05 May 2026 16:20:13 GMT

A “View As” capability in ArcGIS Online that allows creators to preview apps, maps, and Hub sites as specific users or roles (e.g., mobile worker, viewer, external user). This would simulate group memberships, permissions, and licensing without altering configurations or requiring access to real users.

This is especially important for complex deliverables with security and role-based behavior, where content (e.g., pop-ups, widgets, tracks, and tools) varies significantly by user type. Currently, proper testing often requires involving real users or temporarily adjusting licenses and permissions, which is not always feasible within project timelines or budgets.

A “View As” mode would allow administrators and developers to fully validate the end-user experience—including restricted content, missing widgets, licensing differences, and error states—ensuring that applications function as intended for each audience before being shared.

Re: AGOL “View As User” Mode for Role-Based Testing

MichaelVolz — Tue, 05 May 2026 20:16:48 GMT

Excellent suggestion!!!

Re: AGOL “View As User” Mode for Role-Based Testing

Daniel_Conn — Fri, 08 May 2026 20:16:32 GMT

This functionality to 'view as' another user can allow managers to be proactive in their deployments. The current state of reactionary feedback from clients and colleagues in the field can be made much less painful. This widget/feature would greatly improve the confidence of scalability.

Re: AGOL “View As User” Mode for Role-Based Testing

Nick_Creedon — Thu, 14 May 2026 15:26:46 GMT

This is a great idea. I have created a test account that I use to view applications and hub sites with restricted permissions. The test varies, so I will change group permissions on this account to reflect what a user would hypothetically see.

I have our organization set up with all our data shared privately, so we use groups to enable permissions for viewership and to edit data.

To enable a "View as user", should group privileges be at the role level? Should roles be renamed by the type of user they are and the data they need to see?

Example:

Electric Staff sees the electric and data that is shared organizationally. Police Staff sees police data, etc.

This is how it's set up in our Asset Management.

The new options could look like:

Licenses Type: Creator, Mobile Worker, etc

User Type: Viewer, Creator, custom types, etc

Role (where group permissions are assigned): Police Staff, Parks Staff, City All, etc.