Manual column 'Role' keeps resetting in Users Table

Ask for Help
1

Hello!

I’m experiencing an issue where the Role column in my Users table — which is used to distinguish between “Store” and “Customer” users — is repeatedly being cleared or reset to blank.

:wrench: How it’s currently set up:

  • The Role column is a basic text column in the Users table.
  • I am using User Profiles, tied to this same table.
  • The Role is initially set in one of two ways:
    1. Via a Choice component bound to User Profile → Role (initially tried but removed after I thought the Choice component was causing a reset).
    2. Via a button workflow using Set Column Values → User Profile → Role = "Store" or "Customer"
  • This value is written directly into the user’s row (confirmed via User ID), and works at first.

Observed behavior:

  • After successfully setting the Role, it will occasionally disappear (reset to blank), even without further input or overwrite actions.
  • Other user data in the same row (e.g. Full Name, Email) persists correctly.
  • The issue occurs across sessions and screen transitions, without a clear pattern.
  • When I implemented a temporary workaround by duplicating the Role column into a Temp Role or Locked Role column, that value persisted briefly — but it has since also exhibited similar reset behavior.

Steps I’ve already taken:

  • Confirmed that User Profiles are enabled, and the screen is filtered by User ID = signed-in user.
  • Verified there are no duplicate user rows in the Users table.
  • Confirmed that all actions use Set Columns → User Profile → Role — not “This item”.
  • Avoided use of Form Containers for role assignment (which might create new rows).
  • Ensured the Role column is not computed, not part of a template, and not overwritten by any lookup or relation.
  • Added debug fields to display User ID, Role, and This Item → Role for live testing.

What I need:

  • Clarity on what might be triggering the reset of this specific column.
  • Recommendations on how to prevent Glide from overwriting or blanking this column, assuming no workflows are actively changing it.
  • If this is a known bug or edge case, I’d greatly appreciate any timeline or workarounds.

Thank you for your help — I’m happy to provide app access, screenshots, or screen recordings if needed.

Thank you,
Samir

2

This is the expected and documented behaviour. Glide does not allow users to directly set roles for security reasons.

To change or set a users role, you have 3 options:

  • manually via the Data Editor
  • via a server side workflow
  • via the Glide API
1 Like
3

Thank you @Darren_Murphy!

For the purposes of my table, which needs to identify a costumer vs. a store, should I set a column with a non-conflicting name (e.g. User_Role) so it doesn’t get mixed up with the default Role column?

4

The name doesn’t matter, what matters is whether or not it’s configured as the Role column in your User Profiles. If you’re not actually using Roles as Row Owners, then you can just remove that configuration.

1 Like