# User Data Not Staying Saved **URL:** \ **Category:** Ask for Help\ **Created:** [November 30, 2023, 10:04pm UTC](https://community.glideapps.com/t/user-data-not-staying-saved/68276 "2023-11-30T22:04:17Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [December 1, 2023, 7:34am UTC](https://community.glideapps.com/t/user-data-not-staying-saved/68276/9 "2023-12-01T07:34:35Z")
Just to clarify a little here… The only real reason to use User Profile Roles is if you want to use the named roles as Row Owners - either in the same table or other tables. This is a way to restrict which _rows_ of data will be available on each users device, and it allows you to group users together so that they have access to the same set of data rows. For example, consider a business hierarchy where a CEO should have access to all users data, and functional managers should have access to the data of only their direct reports. Roles as Row Owners is a good way to secure data in this scenario. Have a read of the below for a more detailed explanation: > [@Row owners and roles in the same time?](https://community.glideapps.com/t/row-owners-and-roles-in-the-same-time/45691/5): > > No, the users being managed wouldn’t have any role at all. They would just have their own email address as an owner row, which means they would only see their own data. Only the Managers would be given the Manager role, and as a Manager would be set as a Row Owner for every user, they would have access to all data. This might be easier to explain with a picture. Consider the following example: In the example above, the first 3 users are Managers. Each… When using User Profile Roles, there are general rules about when a role can be set: - when a user is created, the role can only be set if the creator has the same role as the one they are attempting to set - when a user record is being edited, the role value cannot be changed under any circumstances. - in both of the above cases, you might see the change made initially, but as soon as the builder syncs with the Glide back end the change will be reverted (which explains your experience). There are two workarounds to each of the above: - manually edit/set the role via the data editor - use the Glide API However, if your goal is to just to use “roles” to control tab/screen/component visibility, then it is not necessary to use User Profile Roles. Instead you can use what I like to refer to as pseudo roles. In this scenario you can have a Role column in your User Profiles table, but you don’t set it as such in your User Profiles Configuration. When using pseudo roles, there are no restrictions on setting/changing values. As long as the user making the change has access to the row, they can set the value. --- _[View the full topic](https://community.glideapps.com/t/user-data-not-staying-saved/68276)._