1
New Policy: Require Name Field Population
Source: dani-garcia/vaultwarden#7838 · opened by @marshallwp
Recently we've been adding some users to organizations and some of them are doing the bare minimum. This includes never setting their name. It is irritating to manage and can even be confusing if their email doesn't nicely match up to a name.
I get that this wouldn't keep names up to date or anything, but it would be nice to require the field not be Empty (or only Whitespace) as a condition of joining an organization.
Alternatively, a way to require the Name field as part of user registration would also work.
I get that this wouldn't keep names up to date or anything, but it would be nice to require the field not be Empty (or only Whitespace) as a condition of joining an organization.
Alternatively, a way to require the Name field as part of user registration would also work.
No pledges yet. Be the first to back this.
Comments
Similar requests
Configuration option to allow custom image sources
1 vote · 0 comments
Add an "Exclude specific characters" field to the password generator policy
1 vote · 0 comments
Feature request: option to set 2mfa policy on collections
1 vote · 0 comments
Require MFA by default
2 votes · 0 comments
New Organization policy to enforce encryption key algorithm/iterations
1 vote · 0 comments
No comments yet.