> 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/general/contacts/leads-common-questions/contacts-edits/contact-history-now-displays-access-permission-changes.md).

# Contact History Now Shows Access Permission Changes

Now, the lead history has a new enhancement: displaying access permission changes. With this feature, it is possible to view which changes were made, ensuring greater transparency and control over the permissions assigned within the platform.

**What changed?**

From now on, when an access permission is changed on a lead, this modification will be recorded in the lead's history. Among the recorded information are:

* Action taken: What was changed in the access permission.
* ID of the previous owner: Identification of the user who previously had access.
* ID of the new user: Indicates the user who received the new permission.

<figure><img src="/files/33c99614b4719ebd8edcc5e2f7c4d5fb62aa8ee0" alt=""><figcaption></figcaption></figure>

#### Benefits of the new feature

This improvement allows:

* Greater traceability: Understand who made changes and when they occurred.
* Transparency: Avoid conflicts by knowing exactly which users had access changes.
* Security: Control the sharing of sensitive information within the platform more precisely.

With this update, users gain more autonomy and clarity about lead permissions, ensuring a safer and more efficient workflow.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/contacts/leads-common-questions/contacts-edits/contact-history-now-displays-access-permission-changes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
