---
title: Agreements
description: You can require end users to consent to an agreement that is part of a sign-on policy in PingOne.
component: pingone
page_id: pingone:user_experience:p1_agreements
canonical_url: https://docs.pingidentity.com/pingone/user_experience/p1_agreements.html
revdate: May 17, 2024
---

# Agreements

You can require end users to consent to an agreement that is part of a sign-on policy.

Whether to require consent is based on configuration settings and the user's consent history. If the user doesn't have any consents for any of the configured agreements, then PingOne will require the user to consent. End users can see their most recent consent in the self-service application. Administrators can use auditing to see a history of the consents that the end user has accepted. Learn more in [Auditing for agreement consents](p1_audit_agreements.html).

You can configure an agreement for each language and locale. If there's no exact match, then PingOne defaults to the general language (without locale). If there is no language match, then PingOne uses the default language for the environment. You can find more information on adding languages in [Languages](p1_languages.html).

For the localized agreement text, you can use any UTF-8 characters up to a maximum of 32,000 characters.