New user cannot edit report filters even with Admin permissions

MikeAtSedron

Hello, I have a new employee and have setup her Smartsheet account just as we do with all new employees. I gave her a license and added her to a few user groups to give her access to workspaces and "Editor - can share" permissions. She is unable to edit the filters of some commonly used reports. I verified she has permission to edit the report by sharing the workspace where the report is located directly with her, but Smartsheet says she already has equal or higher permission level. I then gave her Admin level permission for the workspace, she still cannot edit report filters for reports within that workspace. We have tried a few different reports and found that some reports she can edit filters, and others she cannot. I verified that she is using the correct account and didn't create a duplicate account by accident, her account indicates she has Admin permissions for that workspace. What would cause a user with Admin level permissions to not be able to edit filters in a report?

Louis1

Hi M, Check the permission levels the new user has on the sheets where data is being sourced from. It seems like their permission may be set to view only for some sheets and edit+ for others, thus why they can and cannot change filters in reports. Hope this helps.

L.

MikeAtSedron

Hi Louis, The odd thing is that she has all the same permission as any other regular employee. We give our permissions through groups in the group management tool within the admin center. I added her to the same groups as all our other employees who have access to these reports. We also give permissions in the groups based on workspace so that any report or sheet added to the workspace automatically gives everyone in the group the correct permissions. I will check again with the new employee today to see if she is still having the issue. Thanks for your input!

MikeAtSedron

New development, I checked with the employee today and she now can see the filters within the reports. Not sure what changed but it seems waiting a couple of days did the trick. I would say if someone is having a similar problem to ensure the user has all the correct permissions and then wait 24-48 hours to see if it is resolved on it's own.