Filter data on a Dashboard based on logged-in users

Question

Hello everyone,😊

Here we go again with a topic that I have searched for but didn’t get a proper solution to.

I have a table (just a single hosted Table layer) with a list of 400 employees: name, surname, team _id and overwork time and date.

I need to configure a Dashboard in order for the 20 different team leaders to see the overwork time of just their employees, and make better planification of tasks and holidays.

IMPORTANT: the Editor and Creator of the data it’s going to be my username, because I do actualise this table twice a month.

I added an extra column where I store the AGOL username of the leader of that specific employee.

It looks like this:

Team_id

(integer)

Name, Surname

(String)

Overwork_hrs

(Double)

Date

(Datetime)

Leader_username

(string)

1001

Paul, Jagger

12.5

05/03/2025

j.jakobs@esri.com

1005

Mark, Zucker

45.6

05/03/2025

m.silva@esri.com

1001

Emma, Watson

17.2

05/03/2025

j.jakobs@esri.com

1006

Peter, Parker

10.1

05/03/2025

h.ford@esri.com

Is there a way to make a single Dashboard and not to duplicate the dashboard 20 times for the 20 different leaders? I also try to apply the filter with a Definition Query on a Table's View, but is seem not to work for my table layer.😥

I found this solution https://community.esri.com/t5/arcgis-online-documents/display-features-relevant-to-the-current-user/ta-p/1513220 but it does not work for me because I cannot find the option “UpdateDefinition”.

I appreciate your help!! Thanks a lot for any suggestion!

Dory

clt_cabq · Answer

Of course, I wasn't sure if this need was opsec related or just convenience to the end user. There may be someway to obfuscate that information so the team lead never knows what any other person's identifier is but that is going to be hard to manage.

DoZ · Answer

Hello clt_cabq, thanks for your suggestion, I get the point....BUT what if a leader understands that by changing a word in the URL he can access data of a different leader? It is too risky, the table contains personal data of the employees, I cannot risk this. But the hint was good, in other scenarios without sensible data it might work.

Thanks 😁

clt_cabq · Answer

I wonder if URL parameters could help with this problem? I think you might have to somehow embed team leads into a feature layer attribute in some fashion to implement this though. But that way you could give each team lead a url specific to their needs?

URL Parameter Documentation