mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #2015] Send policy across multiple Orgs #1126
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1126
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bloodypiker on GitHub (Oct 1, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2015
I am trying to selectively allow users to create sends. I have sends enabled from the admin console, but blocked in the primary org. The org owners are able to create sends, and all other users cannot. (expected) I would like to allow select users to create sends, so I created a new org and joined a test user to this org. However, they are still blocked from creating sends, by org policy. (unexpected) I have also given this test user owner privileges to the new "send" org.
`### Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN, SMTP_HOST, SMTP_SSL, SMTP_PORT, SMTP_FROM, SMTP_USERNAME, SMTP_PASSWORD
@cksapp commented on GitHub (Oct 6, 2021):
If the test user is still a part of the org which has the Disable Send policy in place then that policy will still apply to that test user unless they are Owner/Admin of the Org that has the policy enforced. Joining a second Org as Owner/Admin without the Disable Send policy will still leave the policy from Org 1 in place unless the test user was made an Owner/Admin of that first organization.
https://bitwarden.com/help/article/policies/#disable-send
@bloodypiker commented on GitHub (Oct 6, 2021):
I incorporated a workaround by creating separate policy organizations with individual policies. I had my users join these new policy org's to enforce the policy type.
The only downside I see in this approach is the user can un-enroll from the policy org's, to remove the restrictions.