Skip to main content

Require users to accept a policy

Policy attestation requires every user to accept a policy you write, such as an acceptable use policy, before they can use Glean. Glean enforces the requirement at sign-in and records who accepted each policy version and when, so you can export an audit record for compliance reviews.

info

Policy attestation is in private beta. To turn it on for your deployment, contact your Glean account team.

Understand how policy attestation works​

When enforcement is on, Glean checks each user's acceptance during sign-in, after your identity provider authenticates them. If the user hasn't accepted the current policy version, Glean shows a full-page prompt with your policy instead of the app. The user can't reach Glean until they accept.

  • One policy at a time — your deployment has one current policy. Editing it creates a new version and keeps the history of earlier versions.
  • Everyone in your deployment — the policy applies to all users. You can't target specific users or groups.
  • Acceptance per version — a user accepts a version once. Glean doesn't prompt them again until you publish a new version.
  • Fail closed — if Glean can't confirm whether a user accepted, it doesn't sign them in.
  • Single sign-on (SSO) required — Glean shows the prompt during SSO sign-in. Glean support sessions that act on behalf of a user skip the prompt.

Prerequisites​

Complete the following prerequisites:

  • Have the Admin or Super Admin role to create, edit, and enforce a policy. See User roles.
  • Configure SSO for your deployment. See About Glean SSO.
  • Ask your Glean account team to turn on policy attestation for your deployment.

Create a policy​

Creating a policy doesn't require anyone to accept it yet. You turn on enforcement as a separate step, so you can review the policy first.

1

Open the Attestation tab

In the Admin console, go to Notifications → Alerts and select the Attestation tab.

2

Start a new policy

Click Create attestation.

3

Write the policy

Enter the following details. The Preview panel shows the prompt as users will see it.

  • Title — the heading of the prompt, such as "Acceptable Use Policy". Up to 256 characters.
  • Policy text — what users agree to. Up to 20,480 characters. Supports Markdown.
4

Publish the policy

Click Create, and then click Create again to confirm.

The Policy text field supports Markdown headings, lists, emphasis, block quotes, and code. Links open in a new tab and must use https://, http://, or mailto:. Glean doesn't load images in the prompt. It shows their alternative text instead. Glean also doesn't render raw HTML.

Turn on enforcement​

After you create a policy, turn on enforcement to require it at sign-in.

  1. On the Attestation tab, turn on the switch next to the policy.
  2. Click Enable to confirm.

Glean signs everyone out of the web app. When users sign back in, Glean prompts them to accept the policy if they haven't accepted this version already. Some users can keep access for up to 5 minutes before Glean signs them out.

warning

Turning on enforcement signs out web app sessions only. Users stay signed in to the Glean desktop and mobile apps, the Microsoft Office add-in, MCP clients, and other apps connected through OAuth. The Glean app in Slack and API tokens also keep working. Glean prompts users the next time they sign in through SSO.

To stop requiring the policy, turn off the switch and click Disable. Glean keeps your policy and all existing acceptances. If you turn enforcement back on later, users who already accepted the current version aren't prompted again.

Update a policy​

Every saved edit creates a new policy version. Users must accept the new version, even if they accepted an earlier one.

  1. On the Attestation tab, click Edit.
  2. Change the Title or Policy text.
  3. Save your changes:
    • If enforcement is on, click Save and re-prompt. Glean signs everyone out of the web app and prompts them to accept the new version when they sign back in.
    • If enforcement is off, click Save. Users see the new version when you turn on enforcement.

If another admin publishes a change while you're editing, Glean blocks your save so you don't overwrite their version. Copy your edits, close the editor, and reopen it to edit the latest version.

Understand the user experience​

When a user signs in and needs to accept the policy, Glean shows the policy title and text with two options:

  • Accept and continue — records the acceptance and finishes signing the user in.
  • Log out — signs the user out without recording an acceptance. The user can sign in again right away to review and accept the policy.

Closing the page doesn't count as acceptance. The user sees the prompt again the next time they sign in. If the user leaves the prompt open for more than 10 minutes, Glean asks them to sign in again.

Export acceptance records​

Export a CSV file to see who has and hasn't accepted the current policy version. On the Attestation tab, click Export CSV.

The export includes everyone in your people data, plus any other users who reached the prompt. Each row has the following columns:

ColumnDescription
first_nameUser's first name
last_nameUser's last name
user_idUser's Glean ID
user_emailUser's email address
policy_idIdentifier of your deployment's policy. It's the same for every version.
policy_versionIdentifier of the policy version the row reports on
attestation_statusacknowledged if the user accepted this version, or outstanding if they haven't
attested_atTime the user accepted, in Coordinated Universal Time (UTC). Empty for outstanding users.
attestation_surfaceWhere the user accepted: web_login for the web app, or oauth_login for an app that signs in through OAuth. Empty for outstanding users.
exported_atTime you generated the export, in UTC

The export covers the current policy version only. Users who accepted an earlier version appear as outstanding until they accept the current one.

Frequently asked questions​

See also​

  • About admin alerts — manage the other settings on the Alerts page
  • Restricted topics — block or flag prompts on sensitive topics to enforce acceptable use in Glean Assistant