> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/design/user-experience/account-creation.md).

# Account creation

Your users must establish their UR identity and link it to their account on your platform before they can access account features. This process does two things: account creation mints the [on-chain credential](https://docs.ur.app/api-reference/smart-contracts#account) that represents the UR account and Know Your Customer (KYC) identity, and account linking connects your platform identity to that UR account.

### Two authentication paths

Offer one of two ways to authenticate during account creation.

#### Google Sign-In (recommended)

Google Sign-In is the fastest path. It leans on Google's own authentication and security, so your users skip the CAPTCHA and one-time password (OTP) and never fumble with a verification code.

```mermaid
flowchart LR
    A[Continue with Google] --> B[Account created on UR]
```

#### Email authentication

Email authentication works for anyone, with no Google account needed. It takes a few more steps, where you might need to build a CAPTCHA to prevent bots and then an OTP screen to prove email ownership. In exchange, you get more control by not relying on Google Sign-In.

```mermaid
flowchart LR
    A[Continue with email] --> B[CAPTCHA to prevent bots]
    B --> C[Email OTP verification]
    C --> D[Account created on UR]
```

{% hint style="info" icon="figma" %}
Figma reference:\
[**Account creation**](https://www.figma.com/design/WKbdwKpCGPRaAN43tGXHiN/Partner-UX-Guide?node-id=55-6395\&t=4YF7ojkFUmbkiA7z-1)
{% endhint %}

### URID

The URID is the unique identifier generated when a user creates a UR account. It works like an account number, but it is the `tokenId` of the user's Account NFT on-chain, so anyone can verify it. This makes it the primary identifier for customer support and internal operations: support agents look users up by URID, and it cross-references partner systems against UR infrastructure. Because every URID is unique across all partners, it stays stable no matter which platform the user came through.

#### Technical background

Each UR user is represented on-chain by an Account NFT, and the URID is the `tokenId` of that NFT. That makes it the canonical on-chain identity for the user, not merely a database key: it is a verifiable, immutable identifier rooted in the blockchain.

To understand how Account NFTs are structured and managed, see the [Account section in Smart contracts](https://docs.ur.app/api-reference/smart-contracts#account).

#### Recommended placement

{% columns %}
{% column %}
Your users rarely need the URID in normal operations, but it must stay accessible for support scenarios.

Give it low visual priority so it does not compete with high-priority information or actions.
{% endcolumn %}

{% column valign="bottom" %}

<figure><img src="/files/QIupvvvkwoDKLgkBVW3q" alt="" width="375"><figcaption><p>Example of low-priority but always accessible placement of the URID</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}


---

# 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://docs.ur.app/design/user-experience/account-creation.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.