User Profiles

User profiles lets you choose a specific table where data about your users (Name, Email, Image etc) lives. When a user profiles table is set, you can use that data in lots of different ways.

The name, email & avatar of the signed-in user also shows up in the app menu

User data in a User Profiles table is very often private and needs to be kept secure. You should therefore add Row Owners to your User Profile's table. โ„น๏ธLearn about Row Owners here. โ€‹

Setting the User Profiles Table

To use user profiles, your app needs to use Public with Email or Allowed Email List.

By default, no user profile table is set. To set one, create a new table with columns for Name, Email, and Photo. You can add more later, depending on the properties of your users.

Next, open your app's menu and click 'Sign In'. The right panel will now show User Profile settings. Choose the table with your users and connect the Name Email and Image to the correct columns.

Using The User Profiles Table

A user can have many more properties than Name, Email & Photo. These don't have to show in the app, but can be used in many different ways. Below are some basic examples ๐Ÿ‘‡

Editing Conditions

Let's say you wanted to give users different levels of access in your app. For example, editors and users. Editors can edit & delete items whereas users can only view items.

You can achieve this by creating a new column in your users table called (for example) 'Access Level'. Then in this column you can put 'Editor' or 'Viewer' for each user.

Next, you can add a condition on editing which allows only users with 'Editor' in the Access Level column to be able to edit items.

Component Visibility

You could also add properties to your User Table which could be used to hide & show components. In this way, you would be able to show some content to some users and hide it from others.

Instead of using text based conditions, you could create a TRUE or FALSE column. If a user has bought a subscription to your app, you could make this column TRUE and if they haven't, leave it FALSE.

Next, you could set visibility conditions on some of your components using this column. This way, you could hide 'premium' content in your app to free users and unlock it for paying customers.

Visibility conditions, hidden tabs, and removed components are not security featuresโ€”they are merely changes to the appearance of your app. Do not rely on changes to the appearance of your app for security.

Computed columns

You can also use User Profile data in computed columns like the Template Column. For example, you could create a message that welcomed the user and referred to them by name.

In the image below, you can see that as we Preview As different users, the name in the Template column changes. This column can then be assigned to a text component on a welcome screen.

If you have enabled User Profiles you will see the user profile columns in many different places in Glide: Filters, Edit Conditions, Component Visibility conditions and Computed Columns.

Roles

Now that you understand User Profiles, checkout our guide to Roles โ€“ a way to assign different roles to users and build your app around those roles. ๐Ÿ‘‡

โ€‹