> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/loyalty-engine/users/get-started-with-users.md).

# Get started with Users

Each user account represents a member of your loyalty program. A user account consists of several key components:

* [**Profile**](/product/loyalty-engine/users/user-data-attributes-and-flags.md)**:** Contains the user’s profile information, attributes, and flags, providing key details about the individual.
* [**Wallet**](/product/loyalty-engine/users/user-wallet.md)**:** Holds the user’s points balance, current tier, and any vouchers they have earned or been given.
* [**Consents**](/product/modules/marketing/consents.md)**:** Stores information about the consents the user has given, if you are using the Consents module.
* [**Badges**](/product/modules/badges.md)**:** Displays the badges the user has earned as part of gamification efforts in your program.

Additionally, every user:

* has an **event stream**—a log of all events associated with that user.
* can belong to **audiences**, which are segments of users created from custom criteria such as profile data or activity history.
* can be **given or purchase rewards**. These rewards come with associated benefits, which represent the tangible value of the reward. Once a reward is given or purchased, its benefit is linked to the user and available for redemption.

***

## Creating users in the Loyalty Engine

User accounts are created in the Loyalty Engine using the [Register a New User](https://docs.whitelabel-loyalty.com/rewards.html#users-users-collection-post) API endpoint. 

The timing and method for calling this endpoint vary depending on your implementation, and whether you loyalty program is an **embedded** or **standalone** program.

See [Creating users](/product/loyalty-engine/users/creating-users.md) for more information.

***

## Viewing & managing users in the Loyalty Console

Users are managed in the Loyalty Console in the the **Members** screen.

The **Members** screen allows you to:

1. see a list of all users which exist in your loyalty tenant
2. filter the list of users by a user's name, email address or other user profile information (this is useful for finding a specific user's profile)
3. [export the user list to CSV](#user-content-fn-1)[^1]
4. view, edit & delete a specific user

***

## Viewing a user's activity

To see a specific user's activity, navigate to their profile in the Loyalty Console.

From there, you can see a user's:

* Event stream in the **Events** tab
* Purchased but not yet unredeemed benefits in the **Wallet** tab
* Expired benefits in the **Expired Benefits** tab
  * This only applies to Voucher-type rewards which you have set an expiry period on as explained in [Reward availability](/product/loyalty-engine/rewards-and-points/rewards/reward-availability.md)
* Redeemed benefits in the **Redeemed Benefits** tab

[^1]: The export button will export the list of users, up to the most recent 1000, with any filters applied.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kbase.whitelabel-loyalty.com/product/loyalty-engine/users/get-started-with-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.