> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/security-governance/universal-logout/trigger-cerby-universal-logout.md).

# Trigger Cerby Universal Logout

This article describes how to trigger Cerby’s native Universal Logout.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, and **Admins**
* Only supported using the Cerby web app
  {% endhint %}

As a workspace **Admin**, **Super** **Admin**, or **Owner**, you can use Cerby Universal Logout to terminate user access across all devices for the accounts assigned to a user in Cerby.

{% hint style="info" %}
**NOTE:** This version of Universal Logout is triggered solely from Cerby's dashboard.
{% endhint %}

To trigger Universal Logout in Cerby, you must complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Select the **All members** option from the left navigation drawer. The **All Members** page is displayed with the **Members** tab activated.
3. Search for the member whose sessions you want to terminate.
4. Click the **More options** (...) icon of the corresponding user. A drop-down list is displayed.
5. Select the **Trigger Universal Logout** option. All user sessions are terminated immediately on the Cerby client apps. An email notification is sent to all workspace **Admins** informing them about the termination.

Now you are done.


---

# 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://help.cerby.com/setup-and-admin/security-governance/universal-logout/trigger-cerby-universal-logout.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.