# Value in User Table "Disappears"

**URL:** <https://community.glideapps.com/t/value-in-user-table-disappears/87608>\
**Category:** Ask for Help\
**Created:** [August 22, 2026, 11:04pm UTC](https://community.glideapps.com/t/value-in-user-table-disappears/87608 "2026-08-22T23:04:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![BLA\_68](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@BLA\_68](https://community.glideapps.com/u/BLA_68)\
**Post date:** [August 22, 2026, 11:04pm UTC](https://community.glideapps.com/t/value-in-user-table-disappears/87608/1 "2026-08-22T23:04:03Z")

</div>

For sometime now, I’ve had an issue with a particular column in my user table. I have a form that an admin can use to add a user. For some reason, the value that is added to “role” (typically “user”) will initially appear in the table in the data editor. But after some time (sometimes as little as a few seconds, some times many minutes later) that value disappears.

I now see from the helpful “your topic is similar to…” feature that this is seemingly addressed here:

> [@Users table "Role" column values disappear](https://community.glideapps.com/t/users-table-role-column-values-disappear/61692/2):
>
> That’s correct and expected behaviour. Roles can only be assigned when the user record is created, and only if the creating user has the same role. Other than that, roles can be assigned via the Data Editor, or via the Glide API.

and is an expected behavior.

The link that Darren provides is dead now but the current version of the “roles” doc doesn’t indicate that a form cannot be used to set a user role unless the user has the same role. Is this still true?

If so, I’m very curious why? And is there a workaround other than the API…

---

<div class="post-metadata">

**Author:** ![BLA\_68](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@BLA\_68](https://community.glideapps.com/u/BLA_68)\
**Post date:** [August 22, 2026, 11:24pm UTC](https://community.glideapps.com/t/value-in-user-table-disappears/87608/2 "2026-08-22T23:24:43Z")

</div>

Now that I’ve tested this further, I’m maybe even more confused about what the magic is of a text column that happens to have the name “role”. I created a second column called NotRole and wrote the value there as well and it sticks.

To the extent you are using “role” to define either visibility conditions or row ownership or both it seems like you can achieve 90% or more of the same functionality using a column not called “role” but using it in exactly the same fashion. Am I missing something?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [August 23, 2026, 4:49am UTC](https://community.glideapps.com/t/value-in-user-table-disappears/87608/3 "2026-08-23T04:49:26Z")

</div>

When a column is assigned as a role column in your user profile configuration, you can only assign it if the user adding the row has the same role. Otherwise you need to use a server side workflow to assign it.

It has nothing to do with the the name of the column. A role column relies on actually assigning that column as a role column in the user profile configuration.

Also keep in mind that using a non role column as a role column does not provide the same data security as a role column with row owners. Using a pseudo role with a filter just hides data. It does not protect it.

> [@CRITICAL BUG: Race condition between Native Forms, Choice Components, and Row Owners causes silent data loss (bypassing 'Required' flag)](https://community.glideapps.com/t/critical-bug-race-condition-between-native-forms-choice-components-and-row-owners-causes-silent-data-loss-bypassing-required-flag/87539/6):
>
> This is a known and documented security restriction to prevent backdoor access to unowned data. Your original question mentioned an issue with assigning a Row Owner column with a role value. There was no mention of assigning a Role column with a role value. Two very different scenarios that I could have clarified very quickly if you had answered the questions in my first reply. In any case, a role can only be assign via client side actions or workflows if the user setting the role possess th…

---

<div class="post-metadata">

**Author:** ![BLA\_68](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@BLA\_68](https://community.glideapps.com/u/BLA_68)\
**Post date:** [August 24, 2026, 4:08pm UTC](https://community.glideapps.com/t/value-in-user-table-disappears/87608/4 "2026-08-24T16:08:54Z")

</div>

Sorry for asking something that had been covered before but glad to have that info.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [August 31, 2026, 4:09pm UTC](https://community.glideapps.com/t/value-in-user-table-disappears/87608/5 "2026-08-31T16:09:03Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
