> 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/signing-in/it-policy.md).

# Accepting the IT policy

Accept your organization's IT policy, and review what you have agreed to.

Many organizations ask you to read and accept an IT policy — an acceptable-use policy, a security undertaking, a confidentiality statement — before you use their systems. OpenIAM can present that document when you sign in, and records the date you accepted it.

## Accepting it

When a policy is waiting for you, it appears after you sign in and before you reach the rest of the portal. You cannot skip past it.

{% stepper %}
{% step %}
**Read the document shown.**

It is your organization's own text. If you disagree with something in it, that is a conversation with your manager or HR — not something the portal can change.
{% endstep %}

{% step %}
**Confirm your acceptance.**

Choose the confirmation button — commonly **Approve** or **Accept**. Your acceptance is recorded with the date and time.
{% endstep %}

{% step %}
**Continue into SelfService.**

You will not be asked again unless the policy is updated or reset.
{% endstep %}
{% endstepper %}

## Reviewing what you have accepted

Go to your account menu → **Devices & Privacy → Consent History**.

This lists the policies you have accepted and when. It is a read-only record — useful if you need to confirm you agreed to something, or check which version you saw.

## Being asked again

You may meet the policy a second time. The usual reasons are:

* **The policy was updated.** A new version needs fresh acceptance.
* **The policy was reset.** Your organization deliberately asked everyone to re-accept.

Neither means anything is wrong with your account.

{% hint style="info" %}
Your acceptance is a record your organization may rely on for audit or compliance. Read the document rather than clicking straight through — you are agreeing to it.
{% 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/signing-in/it-policy.md?ask=<question>&goal=<user_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.