# Creating a ServiceNow User for Getint Integration
In general scenarios, Admin access is not provided to a ServiceNow instance. The best practice/recommendation is to create a dedicated user (with several different access controls) to connect a ServiceNow instance to Getint and sync the data.
### How to Create a ServiceNow User
#### **1. User Creation:**
* Log in to ServiceNow, click **All** at the top left corner, and navigate to the **Users** (under User Administration) section.
* Click on **New** to create a new user, and enter all relevant user details.
* Enter the User details, and click **Submit** to create the user.
{% hint style="warning" %}
Ensure that you untick **Password needs reset** when creating a new user. If you skip this step, the system will block the connection and display an error stating that you lack sufficient permissions. This message is misleading, as the issue isn’t related to permissions, but simply that the password is set to reset.
{% endhint %}
* After creating the user, you can now generate a password. Do so by clicking **Set Password** in the right corner of the screen. Save the password, and now you can use the full credentials to create a connection with Getint.
#### **2. Create a Role:**
* Navigate to **System Security** > **Users and Groups** > **Roles.**
* Click on **New** and enter relevant details for the new role.
* Click **Submit** to create the role.
#### **3. Elevate System Admin to Security Admin:**
* Click on your profile image and select **Elevate Role.** In the pop-up, choose **security\_admin** and click **Update.** This step elevates the **System Admin** to **Security Admin** and will allow you to modify the **ACL** settings.
#### 4. Required ACLs for Getint Integration:
As we are tailoring access for our users, some base ACLs are required so that the connection with the ServiceNow instance works properly, allowing users to create, edit, and read their fields.
Here is a list of the needed ACLs, as well as their respective purpose in this process:
* **Dictionary Entry \[sys\_dictionary]**\
This is the ServiceNow Data Dictionary, which defines the structure and attributes of every field on every table.\
The Getint user needs read access to this table to introspect the schema of the records being synchronized. By reading this table, Getint identifies a field's type (e.g., reference, string) and its properties (e.g., maximum length, required status). This information is crucial for accurately translating and mapping data types between ServiceNow and other software.
* **Field Class \[sys\_glide*****\_*****object]**\
This table stores definitions for the fundamental data types (e.g., string, integer, reference) used by fields across the instance.
The dedicated user requires read access to this table because it is closely related to sys\_dictionary. It provides the low-level, technical classification of the field types. This access helps Getint's logic correctly interpret and handle the data being pulled or pushed, ensuring that all synchronized fields adhere to their native ServiceNow data constraints.
* **Choice \[sys\_choice]**\
This table contains all the predefined drop-down options (choices) for choice fields in the system, such as Incident State or Priority values.
The Getint user must have read access to retrieve both the internal value (the numerical/system value) and the display label (the user-friendly name) for these choices. This is essential for the core integration function of status and value mapping, ensuring that a status correctly corresponds to the appropriate, valid choice value in ServiceNow.
* **Journal Entry \[sys\_journal\_field]**\
This table is where Journal-type field entries are stored, specifically, records like Additional comments and Work notes from synchronized tickets.
The dedicated user requires read and create/write access to this table to manage bi-directional communication. This access allows Getint to extract comments from a ServiceNow record to sync to the integrated software, and conversely, to write comments back into the correct ServiceNow journal field, maintaining a full communication history.
#### 5. Granting User Access: Create Permission Records in ServiceNow
* Go to **System Security** > **Access Control (ACL).** Now, in the **ACL**, create **six new records** as follows:
**Record 1:**
* Click **New** to create a new record.
* Select **Read** from the **Operation** dropdown.
* In the **Name** field, select **Dictionary Entry \[sys\_dictionary]** in the first dropdown and **\*** in the second dropdown.
* Provide a **Description.**
* In the **Requires Role** section, add the role created in **Step 2** above.
* Click **Submit** at the top right corner, and **Continue** to create the new ACL record.
**Record 2:**
* Repeat the steps as **Record 1,** but this time select **None** in the second dropdown instead of the **\* (asterisk).**
**Record 3:**
* Repeat the previous steps, but in the **Name** field, choose **Field class \[sys\_glide*****\_*****object]** in the first dropdown and **\*** in the second dropdown.
**Record 4:**
* Repeat the previous steps, but in the **Name** field, choose **Choice \[sys\_choice]** in the first dropdown and **\*** in the second dropdown.
**Record 5:**
* Repeat the previous steps, but in the **Name** field, choose **Field class \[sys\_glide*****\_*****object]** in the first dropdown and **None** in the second dropdown.
**Record 6:**
* Repeat the previous steps, but in the **Name** field, choose **Journal Entry \[sys\_journal\_field]** and **None** in the second dropdown.
{% hint style="warning" %}
Do not forget to add the **getint role** in the **Requires role** section for all six records.
{% endhint %}
#### **6. Configure User Permissions:**
* Go to **Users Administration** > **Users.**
* Search for the user created in **Step 1.**
* Click on the user ID and navigate to the **Entitled Custom Tables** section.
* In the **Roles** tab, click **Edit.**
* In the **Collections** section:
* Search for **itil** and move it to the **Roles list.**
* Also, search for the role created in **Step 2** and add it to the **Roles list.**
* Click **Save** and then **Update** to finalize the changes for the user.
With these steps, all permissions are now configured for this ServiceNow user, allowing to establish a connection between Getint and ServiceNow.
---
# 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.getint.io/guides/integration-synchronization/jira-servicenow-integration/creating-a-servicenow-user-for-getint-integration.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.
.png?alt=media&token=5ffbf046-56df-43f8-9721-95d55ab83110)
.png?alt=media&token=799238dd-d212-45a1-b109-e2ac0a3b0f93)
.png?alt=media&token=5dbb5eb5-cfad-4c5a-a550-cd0d4088bc5a)
.png?alt=media&token=e4ab8ba7-20ec-49be-8f10-10968d7ab2d6)
.png?alt=media&token=1a0e6b27-f0ba-47bd-a4e6-f4fb7fffafeb)
.png?alt=media&token=30ac4e3b-d617-4a78-bfc6-da1f23199474)
.png?alt=media&token=20787949-f5e3-4486-bbc6-386480155dec)
.png?alt=media&token=6fecc870-c555-49fd-9fa2-4012f370e604)
.png?alt=media&token=d4511f78-c821-445e-ac12-a101576bf72c)
.png?alt=media&token=d92b7e43-7e17-4d08-b0e6-788145becd08)
.png?alt=media&token=7a055e10-f9a2-46fa-8972-9fcd5fe955d4)
