Inviting users via email results in a reference to a "bitwarden_rs" organization. This is turning out to be confusing to my users - it would be great if I could configure that string to be something else.
It looks like the string is hardcoded at src/api/admin.rs:164:
I think just being able to set this string via environment variables would solve my problem.
Your environment
Bitwarden_rs version: 1.13.1
Install method: docker
Originally created by @aroberts on GitHub (Jan 26, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/825
<!--
Please fill out the following template to make solving your problem easier and faster for us.
This is only a guideline. If you think that parts are unneccessary for your issue, feel free to remove them.
Remember to hide/obfuscate personal and confidential information,
such as names, global IP/DNS adresses and especially passwords, if neccessary.
-->
### Subject of the issue
<!-- Describe your issue here.-->
Inviting users via email results in a reference to a "bitwarden_rs" organization. This is turning out to be confusing to my users - it would be great if I could configure that string to be something else.
It looks like the string is hardcoded at `src/api/admin.rs:164`:
```rust
let org_name = "bitwarden_rs";
mail::send_invite(&user.email, &user.uuid, None, None, &org_name, None)
```
I think just being able to set this string via environment variables would solve my problem.
### Your environment
<!-- The version number, obtained from the logs or the admin page -->
* Bitwarden_rs version: 1.13.1
<!-- How the server was installed: Docker image / package / built from source -->
* Install method: docker
Sounds reasonable to me. Should we use the already existing SMTP_FROM_NAME as it serves a similar purpose? Or create a separate option?
<!-- gh-comment-id:580444555 -->
@dani-garcia commented on GitHub (Jan 30, 2020):
Sounds reasonable to me. Should we use the already existing SMTP_FROM_NAME as it serves a similar purpose? Or create a separate option?
I'd vote for a separate var, but it would be great to default the new var's value to SMTP_FROM_NAME if left blank/unset
<!-- gh-comment-id:580740053 -->
@aroberts commented on GitHub (Jan 31, 2020):
I'd vote for a separate var, but it would be great to default the new var's value to SMTP_FROM_NAME if left blank/unset
Fixed, decided on creating a separate independent option to avoid making the configuration logic more complex than needed.
<!-- gh-comment-id:582119099 -->
@dani-garcia commented on GitHub (Feb 4, 2020):
Fixed, decided on creating a separate independent option to avoid making the configuration logic more complex than needed.
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.
Originally created by @aroberts on GitHub (Jan 26, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/825
Subject of the issue
Inviting users via email results in a reference to a "bitwarden_rs" organization. This is turning out to be confusing to my users - it would be great if I could configure that string to be something else.
It looks like the string is hardcoded at
src/api/admin.rs:164:I think just being able to set this string via environment variables would solve my problem.
Your environment
@dani-garcia commented on GitHub (Jan 30, 2020):
Sounds reasonable to me. Should we use the already existing SMTP_FROM_NAME as it serves a similar purpose? Or create a separate option?
@aroberts commented on GitHub (Jan 31, 2020):
I'd vote for a separate var, but it would be great to default the new var's value to SMTP_FROM_NAME if left blank/unset
@dani-garcia commented on GitHub (Feb 4, 2020):
Fixed, decided on creating a separate independent option to avoid making the configuration logic more complex than needed.