# 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 settings for operation within the platform. {% embed url="" %} *** ### User Information This section defines the user's main data within the system. * **Name** – Name of the user who will use the system. * **Phone** – User's contact number. * **Date of Birth** – Birth date registered for the user. * **E-mail** – E-mail address used for login and receiving notifications. * **CPF** – Individual Taxpayer Registry of the user. * **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 to send 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, being able to view and configure all areas of the system. * **Absence indicator time** – Setting used in **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 tickets * Conversation routing * Access permissions * Automation of flows and processes A user can be linked to **one or more departments**, depending on the company's organizational structure. This configuration helps ensure that service requests and activities are routed correctly to each team. *** ### Default Access Permissions In this section, define **which users or departments will have initial access** to the items created by this user in other entities in the system. These permissions determine **who will be able to view or edit the created records**, 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**. --- # Agent Instructions: 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: ``` GET https://docs.sprinthub.com/en/topics/settings/users/users-initial-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.