> For the complete documentation index, see [llms.txt](https://attr.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attr.sygnal.com/sa5-data/data-sources/user-info-data-source.md).

# User Info Data Source

{% hint style="danger" %}
Webflow has announced the deprecation of **Webflow User Accounts**. This data source will continue working until it is fully deprecated. 
{% endhint %}

{% hint style="success" %}
This functionality is available when you are using [SA5's User Info](/sa5-user-accounts/get-logged-in-user-info.md) library.
{% endhint %}

If you are using **Webflow User Accounts** and [SA5's User Info library](#user-info), then SA5 constructs a User Info object whenever a user is currently logged in. 

The details of that object can be data-bound. 

* `$user.name`
* `$user.email`

[User Info Data Source](/sa5-data/data-sources/user-info-data-source.md)

## Custom User Fields 

[Custom user fields](/sa5-user-accounts/get-logged-in-user-info/custom-user-fields.md) can also be accessed, under `$user.data.your-field-name`.

You can use this in element data-binding, with the 

```
{{ $user.data.your-field-name }}
```

{% hint style="success" %}
**Shortcut.** `@` can be used as a shortcut in place of `$user.`, for example `@name` is equivalent to `$user.name` 
{% endhint %}

## Examples

wfu-bind = $user.data.link-field

{{ $user.data.link-field }} 

If you are using **Webflow Memberships** and **SA5's User Info library**, then SA5 constructs a User Info object whenever a user is logged in.

The details of that object can be data-bound. e.g.;

* `$user.name` - Gets the current user's name
* `@email` - Gets the current user's email

They can be used with `wfu-bind`, or within template macros within `wfu-bind-content`, e.g.

```
Hello {{ $user.name }}! Welcome to our site.  
```

## Available DSD's

Prefix any of these with `$user.` They can be used with wfu-bind, or within templates  wfu-bind-content. 

{% hint style="success" %}
**Shortcut.** `@` can be used as a shortcut in place of `$user.`, for example `@name` is equivalent to `$user.name` 
{% endhint %}

<table><thead><tr><th width="233">$user.</th><th></th></tr></thead><tbody><tr><td><code>name</code></td><td>The user's name, as they've specified in account info</td></tr><tr><td><code>email</code></td><td>The user's email address</td></tr><tr><td><code>name_short</code></td><td>A pseudonym, composed from the email's <code>name@</code> portion</td></tr><tr><td><code>name_short_clean</code></td><td>The name_short pseudonym, without the <code>@</code></td></tr><tr><td><code>name_short_tcase</code></td><td>The <code>name_short_clean</code> pseudonym, title cased</td></tr><tr><td><code>user_id_alt</code></td><td>A unique ID for the User. This is <em>not</em> the Webflow Membership's ID, and cannot be used with Webflow's API - but is equally usable for 3rd party system integration and tracking.</td></tr><tr><td><code>data.</code><strong><code>FIELD-NAME</code></strong></td><td><p>data contains a map of the user's custom fields. Specify the field you want in place of <strong>FIELD-NAME</strong>. </p><p>These are named using Webflow's internal data field names, which is based on your individual user field slugs.</p></td></tr></tbody></table>

## Demo

{% embed url="<https://webflow.com/made-in-webflow/website/current-user-info>" %}


---

# 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:

```
GET https://attr.sygnal.com/sa5-data/data-sources/user-info-data-source.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.