User Metadata
On this page
This page describes how to manage user metadata for an authorized App Services App user using Atlas Device SDK. For more information, refer to Authentication Provider Metadata in the App Services documentation.
Atlas App Services can read user metadata from authentication providers,
such as Google or Facebook. Then, App Services exposes each user's metadata in
a field of their User object. For example, you might want to access a
user's name, email, birthday, or gender. This is read-only data that comes
from the third-party authentication provider.
This is distinct from maintaining your own, editable custom user data. If you'd like to define your own user data fields, or have the ability to directly update user data, use Custom User Data.
Important
Configure Metadata in Atlas
Before you can work with metadata provided by the authentication provider, you must configure metadata for the authentication provider.
Read User Metadata
User metadata options vary depending on which provider you're using and which metadata fields you enable.
Warning
User Metadata May Be Stale
Atlas App Services fetches the most recent version of user metadata when a user logs in. If the user changes their email address or profile photo with a login provider, for example, those changes do not update in user metadata until the user logs in again. Because we cache credentials and enable you to bypass the login flow, user metadata may become stale unless you force the user to log in again.
Serializable User Metadata
Some of the SDK languages provide serializers for user metadata.