We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is possible for admins to change the email address of SecHub users. They will recieve an email, but all it currently says is:
Subject: SecHub account email address changed A SecHub administrator has changed your email address and it will not be used any longer for SecHub. In case you do not receive a follow up notification to the new email address, please inform your SecHub administrator!
Subject: SecHub account email address changed
A SecHub administrator has changed your email address and it will not be used any longer for SecHub.
In case you do not receive a follow up notification to the new email address, please inform your SecHub administrator!
The email should say for which user the mail address was changed, and what the new email address is.
Example:
Subject: SecHub email address of $SECHUB_USER changed A SecHub administrator has changed the email address of $SECHUB_USER from $OLD_EMAIL_ADDRESS to $NEW_EMAIL_ADDRESS. In case you do not receive a follow up notification to the new email address, please inform your SecHub administrator!
Subject: SecHub email address of $SECHUB_USER changed
A SecHub administrator has changed the email address of $SECHUB_USER from $OLD_EMAIL_ADDRESS to $NEW_EMAIL_ADDRESS.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Situation:
It is possible for admins to change the email address of SecHub users. They will recieve an email, but all it currently says is:
Wanted:
The email should say for which user the mail address was changed, and what the new email address is.
Example:
The text was updated successfully, but these errors were encountered: