> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/users/users-initial-settings.md).

# Users - Initial Settings

When creating or editing a user in the system, it is necessary to fill in some basic information. These settings define the user's data, access credentials, permissions, and other important definitions for how they function within the platform.

{% embed url="<https://youtu.be/yryVf-7Mdp8>" %}

***

### User Information

In this section, the user's main data within the system is defined.

* **First name** – User name that will use the system.
* **Phone** – User contact number.
* **Date of Birth** – Date of birth registered for the user.
* **Email** – E-mail address used for login and receiving notifications.
* **CPF** – User's Individual Taxpayer Registry.
* **Outgoing automation WhatsApp** – Defines which WhatsApp number will be used when automations are sent on behalf of this user.
* **Outgoing automation e-mail** – Defines which e-mail will be used for sending automatic messages.
* **Default branch** – Determines which branch will be considered the default for this user within the system.

***

### Login Information

Configure the data below so that the new user can access the system.

* **User** – Identifier used to log in to the system.

{% hint style="danger" %}
**Important:** this field **cannot be changed after creation**.
{% endhint %}

* **Password** – Password used to access the system.

***

### Other Settings

Additional settings that control the user's permissions and behavior in the system.

* **Block user?** – Allows blocking the user's access to the system without needing to delete the record.
* **Administrator** – Defines whether the user will have administrative access, allowing them to view and configure all areas of the system.
* **Absence indicator time** – Setting used in the **VoIP** to indicate the user's inactivity time before appearing as absent.

***

### Departments

Select below which **departments** this user will be part of within the system.

Departments are used to organize teams and can also be applied in different platform features, such as:

* Distribution of service
* Conversation routing
* Access permissions
* Flow and process automation

A user can be linked to **one or more departments**, depending on the company's organizational structure. This configuration helps ensure that services and activities are directed correctly to each team.

***

### Default Access Permissions

In this section, define **which users or departments will initially have access** to the items created by this user in other entities of the system.

These permissions determine **who will be able to view or edit the records created**, such as:

* Leads
* Contacts
* Companies
* Opportunities
* Other system records

#### Access configuration

* **Users** – Allows selecting specific users who will have access to the items created by this user.
* **Departments** – Allows defining which departments can view or edit the created items.

⚠️ **Important:**\
If a user **does not have access to an item**, they **will not be able to view or edit it**, regardless of the permissions configured in the **Permission Groups** of the system.

💡 **Tip:**\
If the lists of **Users** and **Departments** are left **empty**, the system will understand that **all users will be able to access the created items**.