It appears that the put policy logic now use the old endpoint with the new format.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dani-garcia/vaultwarden/pull/7296
**Author:** [@Timshel](https://github.com/Timshel)
**Created:** 6/3/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `fix/putpolicy`
---
### 📝 Commits (1)
- [`7728388`](https://github.com/dani-garcia/vaultwarden/commit/77283882e10ab4870245b4861682f74aa3798250) PutPolicy now using vnext format
### 📊 Changes
**1 file changed** (+14 additions, -15 deletions)
<details>
<summary>View changed files</summary>
📝 `src/api/core/organizations.rs` (+14 -15)
</details>
### 📄 Description
It appears that the put policy logic now use the old endpoint with the new format.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/7296
Author: @Timshel
Created: 6/3/2026
Status: 🔄 Open
Base:
main← Head:fix/putpolicy📝 Commits (1)
7728388PutPolicy now using vnext format📊 Changes
1 file changed (+14 additions, -15 deletions)
View changed files
📝
src/api/core/organizations.rs(+14 -15)📄 Description
It appears that the put policy logic now use the old endpoint with the new format.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.