> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-docs/user-guide/smart-auth/getting-started.md).

# Getting Started

## **Account creation**

First of all, you will need to be registered with Smart Auth. If you do not have an account yet, please [register here](https://identity.combateafraude.com/signup).

## **Identities**

Identities are used to authenticate your users.

Go to the "Identities" tab and then go to "Create identity".

### **Data required to create an identity**

| Field          | Required |
| -------------- | -------- |
| **`PersonId`** | Yes      |
| **`Name`**     | Yes      |
| **`Selfie`**   | Yes      |
| **`Phone`**    | No       |
| **`E-mail`**   | No       |

{% hint style="info" %}
You must inform Phone with country and region code, DDI+DDD+NUMBER (5511999999999).
{% endhint %}

### **Create an identity manually**

In the manual creation tab, fill in the data for the desired identity and upload a selfie. To conclude, click "Register identity".

### **Create identities via API**

You can also create identities via API, allowing for a more seamless and integrated experience within your own user flow. This approach enables you to automate identity creation and fully integrate it with your systems.\
For more details, see the [Identity API documentation](https://docs.caf.io/caf-api/smart-auth-api/available-resources/identity).

## **Access policies**

Access policies define how users will be authenticated. Contexts are the information that will be collected to determine if the user is accessing the system from a known context. Reauthentication methods, on the other hand, are the steps the user will have to go through to prove their identity if their context is not known.

To create a policy, go to the "Tools" tab select "Authentication policies" and click "Create policy".

### **Data required for creating an access policy**

| Field                         | Required |
| ----------------------------- | -------- |
| **`Identifier`**              | Yes      |
| **`Name`**                    | Yes      |
| **`Contexts`**                | Yes      |
| **`Reauthentication method`** | Yes      |

### **Identifier**

It is the unique ID of the policy. It is used when invoking the Smart Auth SDK.

### **Contexts**

| Context        | Description                                          |
| -------------- | ---------------------------------------------------- |
| **`Device`**   | Checks if the device being used by the user is known |
| **`Location`** | Checks if the user's access location is known        |
| **`Network`**  | Checks that the user's network information is known  |

### **Reauthentication methods**

| Method                      | Description                                                                                                  |
| --------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **`Facial authentication`** | Takes a picture of the user accessing the system and compares it with the selfie registered for the identity |
| **`E-mail`**                | Sends a code to the e-mail address registered for the identity and uses this code to validate the user       |
| **`SMS`**                   | Sends a code via SMS to the phone registered for the identity and uses this code to validate the user        |


---

# 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://docs.caf.io/caf-docs/user-guide/smart-auth/getting-started.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.
