> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/my-devices/consent-history.md). # Consent history Review the policies you have accepted and when you accepted them. **Consent History** is the record of the policies you have agreed to — acceptable-use policies, security undertakings, privacy notices — and the date you accepted each one. Open it from your account menu → **Devices & Privacy → Consent History**. ## What it's for The page is read-only. You cannot withdraw consent here, and you cannot edit the record — that is the point of it. It exists so that: * **you can check what you agreed to**, and when * **your organization can demonstrate** that its people accepted the policies it is required to circulate If your organization has to prove to an auditor that everyone accepted a security policy, this is where that evidence comes from. ## Reading it Each entry shows the policy and your acceptance date. Where several versions have been issued over time, you will see an entry for each — so you can tell which version you saw and when a newer one replaced it. ## Being asked to accept again Seeing a fresh policy prompt after you have already accepted one is normal. It happens when the document is updated, or when your organization deliberately resets acceptance and asks everyone to confirm again. See [Accepting the IT policy](/end-user-guide-for-selfservice/signing-in/it-policy.md). {% hint style="info" %} If you want to withdraw consent, or you disagree with a policy you have already accepted, that is a conversation with HR, your manager, or your privacy team. The portal records decisions; it doesn't negotiate them. {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.openiam.com/end-user-guide-for-selfservice/my-devices/consent-history.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.