> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.noticeable.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# End User Authentication 🔑👤 ✅

When one of your end user leaves for instance a comment via a Noticeable widget, knowing their identity and having their email address is beneficial for effective responses. Noticeable's end user authentication process confirms the genuineness of a user's identity, safeguarding sensitive data and features from unauthorized access.

Noticeable utilizes _Single Sign-On_ (SSO) tokens for its end user authentication.

| End user authentication is optional but recommended. You can learn more about the different identification methods we support [here](/en-us/article/end-user-identification-64wjm/).

# Authentication with Noticeable Widgets

## How it works

1. On your server side, you create an SSO token per end user (using a secret we share).
2. You pass this SSO token with our Javascript SDK before rendering any widget.
3. That's it! Your end user is authenticated with Noticeable widgets.

### Creating an SSO token

The SSO token is a digital key that is encrypted and contains data attributes about your end user. This token must be created on your server. 

Browse to the next page for examples about how to create an SSO token in various programming languages:

https://dashboard.noticeable.io/end-user-sso#widgets


### Passing your end user SSO token with our SDK

This simply consists in calling `noticeable.identify(...)`. The first parameter is your project ID on Noticeable and the second your end user SSO token:

```
noticeable.identify('YOUR_PROJECT_ID', 'YOUR_END_USER_SSO_TOKEN');
```

|| The call to `identify(...)` must be made before any call to `render(...)`.