> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/changelog/earlier-releases/2024-02-26.md).
# 26 February 2024
Organization-Wide Single Sign On
## 26 February 2024
{% hint style="info" %}
Published on dispel.com.
{% endhint %}
## Organization-Wide Single Sign On
Administrators can now enforce that all their users must sign in using single-sign on when logging into Dispel. Previously, users could sign in via SSO or a hybrid model where Dispel Privileged Access Management worked alongside an SSO platform such as Okta or Microsoft Active Directory. With this new update, admins can require that all users must use the organization's SSO provider to authenticate. This disables Dispel Privileged Access Management within the dashboard.
This allows your organization admins more control over user passwords, and can control who has access to the application from the dashboard of the SSO identity provider. With this, admins have centralized management of all their users and all types of users within their organization.
### Bug Fixes and Updates
* Fixed translations in Password Vaulting.
* Fixed an issue with showing a success toast when an admin re-sends an invite to a member that hasn't accepted their invitation.
---
# 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.dispel.com/changelog/earlier-releases/2024-02-26.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.
