> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/core-concepts/users-onboarding.md).

# Users Onboarding

Explanations about the users onboarding feature

## Why ? <a href="#id-1.14.x-usersonboarding-businessrules-why" id="id-1.14.x-usersonboarding-businessrules-why"></a>

The goal of onboarding is to encourage users to fill out their profile to communicate the most information about themselves.

The User onboarding page will be used to let’s offerer or asker complete their entire profile (Presentation, User categories, User attributes, User address).

## Which context <a href="#id-1.14.x-usersonboarding-businessrules-whichcontext" id="id-1.14.x-usersonboarding-businessrules-whichcontext"></a>

Lot of users do not fill their user profile, so we do not have a lot of information of the concerned users when a booking request is done. It can be a missed sale for lack of trust in the customer or the seller. To avoid this, we try to encourage users to fill in their information, and thus improve mutual trust when making a booking.

## Interfaces <a href="#id-1.14.x-usersonboarding-businessrules-interfaces" id="id-1.14.x-usersonboarding-businessrules-interfaces"></a>

* [User onboarding page](https://features.scnd.com/v2.0/front-office/users-onboarding-page.md)

## Workflow <a href="#id-1.14.x-usersonboarding-businessrules-workflow" id="id-1.14.x-usersonboarding-businessrules-workflow"></a>

Once the configuration of the user onboarding feature is done, the user will see only one time the user onboarding. He can choose to skip it or fill all his user information.

## Configurations <a href="#id-1.14.x-usersonboarding-businessrules-specialrules" id="id-1.14.x-usersonboarding-businessrules-specialrules"></a>

SBO > Other > Feature > User Onboarding

## Special rules <a href="#id-1.14.x-usersonboarding-businessrules-specialrules" id="id-1.14.x-usersonboarding-businessrules-specialrules"></a>

### When the user onboarding appear ? <a href="#id-1.14.x-usersonboarding-businessrules-whentheuseronboardingappear" id="id-1.14.x-usersonboarding-businessrules-whentheuseronboardingappear"></a>

When a user has not filled in their profile information or when one of these fields are missing:

* Presentation,
* User categories,
* User attributes,
* User address


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://features.scnd.com/v2.0/core-concepts/users-onboarding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
