[PR #216] [MERGED] Implement poor man's admin panel #2669

New issue

Closed

opened 2026-03-03 08:36:14 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 08:36:14 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/216
Author: @mprasil
Created: 10/12/2018
Status: ✅ Merged
Merged: 10/13/2018
Merged by: @dani-garcia

Base: master ← Head: superuser

📝 Commits (1)

a28caa3 Implement poor man's admin panel

📊 Changes

12 files changed (+210 additions, -72 deletions)

View changed files

📝 README.md (+16 -0)
📝 src/api/core/accounts.rs (+4 -21)
📝 src/api/core/mod.rs (+4 -3)
📝 src/api/core/organizations.rs (+37 -22)
📝 src/api/identity.rs (+6 -4)
📝 src/auth.rs (+8 -2)
📝 src/db/models/cipher.rs (+7 -0)
📝 src/db/models/device.rs (+10 -6)
📝 src/db/models/folder.rs (+7 -0)
📝 src/db/models/organization.rs (+71 -4)
📝 src/db/models/user.rs (+38 -10)
📝 src/main.rs (+2 -0)

📄 Description

This enables you to configure one email account to be server administrator via the SERVER_ADMIN_EMAIL environment variable. This will give the user extra functionality and privileges to manage users on the server. In the Vault, the user will see a special (virtual) organization called bitwarden_rs. Deleting users from this organization will actually completely delete the user from the server. Inviting users into this organization will just invite the user so they are able to register, but will not grant any organization membership.

This should hopefully cover use cases like the one in #212 and #202 without actually creating the admin panel.

_{🔄 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/216 **Author:** [@mprasil](https://github.com/mprasil) **Created:** 10/12/2018 **Status:** ✅ Merged **Merged:** 10/13/2018 **Merged by:** [@dani-garcia](https://github.com/dani-garcia) **Base:** `master` ← **Head:** `superuser` --- ### 📝 Commits (1) - [`a28caa3`](https://github.com/dani-garcia/vaultwarden/commit/a28caa33ef48ef452aa9fb84f729a3005cc165fc) Implement poor man's admin panel ### 📊 Changes **12 files changed** (+210 additions, -72 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+16 -0) 📝 `src/api/core/accounts.rs` (+4 -21) 📝 `src/api/core/mod.rs` (+4 -3) 📝 `src/api/core/organizations.rs` (+37 -22) 📝 `src/api/identity.rs` (+6 -4) 📝 `src/auth.rs` (+8 -2) 📝 `src/db/models/cipher.rs` (+7 -0) 📝 `src/db/models/device.rs` (+10 -6) 📝 `src/db/models/folder.rs` (+7 -0) 📝 `src/db/models/organization.rs` (+71 -4) 📝 `src/db/models/user.rs` (+38 -10) 📝 `src/main.rs` (+2 -0) </details> ### 📄 Description This enables you to configure one email account to be server administrator via the `SERVER_ADMIN_EMAIL` environment variable. This will give the user extra functionality and privileges to manage users on the server. In the Vault, the user will see a special (virtual) organization called `bitwarden_rs`. Deleting users from this organization will actually completely delete the user from the server. Inviting users into this organization will just invite the user so they are able to register, but will not grant any organization membership. This should hopefully cover use cases like the one in #212 and #202 without actually creating the admin panel. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>