Filter operations dashboard based on AGOL login / username

[DataOfficer]

It would be very useful to be able to filter the operations dashboard based on the users AGOL login (username). For example, our business use case consists of a large number of staff and volunteer surveyors carrying out wildlife monitoring. We have an operations dashboard they can access to interact with the monitoring programme results, with various filters. The ideal scenario would be a button we could configure ('view my records') that filtered solely based on their AGOL logon, without the need for the user to type it in or select it from a list. 
We have a workaround in place which requires us to anonymise users with a unique ID, and for the user to then select that ID from a dropdown. Users are anonymised for data protection purposes.

An alternative workaround would be to enable a filter where the user has to type in their username, but it does not form part of a drop down list and does not autocomplete, to protect the identity of other users. Is this currently supported?

[jessneuner]

We had a similar need arise this week for our City Marshal’s Office. They use survey 123 to log their patrolling activities and interactions with the public. The City Marshal would like his team to be able to review their own reports but not filter the dashboard to show any other single Marshal’s/Ranger’s data. 

[WilliamRockwell1]

You might be able to do this with URL parameters. But I think the permissions might be tricky.

So hypothetically you could have a URL to a dashboard that would be like: https://(ORG).maps.arcgis.com/apps/dashboards/blahblahblah#USER={username}

If this is not super secret data, and people aren't going to intentionally type in another persons user name in the URL, this is probably going to give you what you want. The problem(s) would be: that this URL might be viewable to other users unless the permissions were setup where only select people can see it. 

Example of two employees: Bob's URL will be https://(ORG).maps.arcgis.com/apps/dashboards/blahblahblah#USER=bob.jones and John's URL would be https://(ORG).maps.arcgis.com/apps/dashboards/blahblahblah#USER=john.doe, there's nothing keeping Bob or John from manually typing in the different user name at the end of the URL to see the other's data. If that's not a realistic concern, give it a shot. 

Another solution I have used would be to create a view layer of the data that is filtered by that persons username. So you could have a layer called "123XYZ" and its really just john.doe's data, and perhaps it's owned (not shared) with anyone else so only that user can see it. I have done this for ~70 users but if you have a lot of users, it might not be doable.