# Access Tracking

CRM Access Tracking is a feature to track access of the Dynamics CRM users. It enables the managers to monitor the CRM access of their team members by tracking various web activities performed by them in the CRM manually.

{% hint style="info" %}
**Note: This feature doesn’t give the actual daily login count of a CRM user. It instead provides brief detail on the number of times a user accesses a CRM.**
{% endhint %}

#### STEPS TO TRACK USER’S CRM ACCESS

* The first step to track user’s CRM Access is to **Enable Auditing**. For this, navigate to **Settings --> Auditing (under ‘System’ group).**

![](https://272130504-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M0QoyqUVI8_HaZ9FOSL%2F-MQog0Rhwn2kwp1HxPju%2F-MQoiBz607nu-G1o3zDx%2FAccess%20Trac_1.png?alt=media\&token=4a1e0270-002b-42c4-9eb2-b76499f9878d)

* It opens Audit window as shown below. Click on **‘Global Audit Settings’**.

![](https://272130504-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M0QoyqUVI8_HaZ9FOSL%2F-MQog0Rhwn2kwp1HxPju%2F-MQoiX6HyNG3lxfduaHV%2FAccess%20Trac_2.png?alt=media\&token=3791e60f-a839-486a-99e0-8809b57d6f7f)

* Click on **‘Auditing’** tab. Check **‘Start Auditing’** and **‘Audit user Access’** settings as shown below:

![](https://272130504-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M0QoyqUVI8_HaZ9FOSL%2F-MQog0Rhwn2kwp1HxPju%2F-MQoigGCZeHAQxU85BCu%2FAccess%20Trac_3.png?alt=media\&token=cff16148-024d-4b69-97ce-2caeeb608f20)

* After enabling **Auditing,** create a **‘User Adoption Entity Configuration’** record for user login. For this, navigate to **User Adoption Monitor App** **--> Entity Configurations** (under **‘User Adoption Monitor’** group).

![](https://272130504-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M0QoyqUVI8_HaZ9FOSL%2F-MQog0Rhwn2kwp1HxPju%2F-MQoimfVH778OlPMgFCV%2FAccess%20Trac_4.png?alt=media\&token=2df6124b-c3cf-4656-9525-442c9e0c8dab)

* Click on **(+ New)** to create a new User Adoption Entity Configuration record for login (If no record is already created).

{% hint style="info" %}
**Note: Whether the entity configuration record has already been created or not can be verified from the Entity Configurations home view.**
{% endhint %}

* The User Adoption Entity Configuration record should always be created with the following attributes as shown in the screenshot below:
  * **Entity Label:** “systemuser” 
  * **Entity Schema:** “systemuser” 
  * **Message:** “login” 
  * **Period:** “Daily” 
  * **Polling:** Select the interval period after which tracking will be conducted. 
  * **Preferred Start Time:** Select the time to start the tracking.

![](https://272130504-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M0QoyqUVI8_HaZ9FOSL%2F-MQog0Rhwn2kwp1HxPju%2F-MQoj8BK7Xu2b-alMN2J%2FAccess%20Trac_4.5.png?alt=media\&token=ddc8c9d0-1983-4a01-9223-158a1526fb5d)

{% hint style="info" %}
**Note: The period should always be selected as ‘Daily’ as this feature only works for daily tracking.**
{% endhint %}

* Once the Entity Configuration record is created, the User Adoption Monitor will track the CRM Access of each logged in user. The tracking details can be reviewed either from the **‘systemuser-login’** entity configuration record as below or by navigating to the **Settings --> User Adoption Monitor --> Trackings.**

![](https://272130504-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M0QoyqUVI8_HaZ9FOSL%2F-MQog0Rhwn2kwp1HxPju%2F-MQojEEG7XKSY3tmb4zn%2FAccess%20Trac_5.png?alt=media\&token=6b953e19-5e88-4dd1-b1e0-658f5439cd47)

{% hint style="success" %}
For further queries, reach out to us at <crm@inogic.com>
{% endhint %}


---

# 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.inogic.com/user-adoption-monitor/configuration/setting-up-other-messages/access-tracking.md?ask=<question>
```

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.