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
When someone adds you to an instance, you aren't really "invited"—there's nothing to accept or reject. This leads to confusion.
We should send one kind of email when inviting people who aren't existing users, and another kind of email when granting access to someone is a user.
Also, while fixing this, it would be good to ensure that the invite email says "organization" when it should say "instance".
Probably don't fix this until the PRs starting #678 are merged, as they refactor some of the invite stuff.
Part of #618.
The text was updated successfully, but these errors were encountered:
Since we have to make these changes on sendgrid, I thought it would be best if someone could review my prose here:
You've been invited to join the organization ":org_id" on Weave Cloud. Click this link to login to Weave Cloud: Log in to Weave Cloud This single-use login link is valid for 3 days. You can generate a new one at any time by visiting Weave Cloud You need to run probes on your Docker hosts to send information to Weave Cloud. Instructions for that are available once you log in. Thanks, the Weaveworks team <%body%>
You've been invited to join the organization ":org_id" on Weave Cloud.
Click this link to login to Weave Cloud:
Log in to Weave Cloud
This single-use login link is valid for 3 days. You can generate a new one at any time by visiting Weave Cloud
You need to run probes on your Docker hosts to send information to Weave Cloud. Instructions for that are available once you log in.
Thanks, the Weaveworks team
<%body%>
:user_name has invited you to access the ":org_name" monitoring instance on Weave Cloud. Click this link to login to Weave Cloud: Log in to Weave Cloud This single-use login link is valid for 3 days. You can generate a new one at any time by visiting Weave Cloud You need to run probes on your Docker hosts to send information to Weave Cloud. Instructions for that are available once you log in. Thanks, the Weaveworks team <%body%>
:user_name has invited you to access the ":org_name" monitoring instance on Weave Cloud.
Differences
:user_name has granted you access to the ":org_name" monitoring instance on Weave Cloud. View :org_name Thanks, the Weaveworks team <%body%>
:user_name has granted you access to the ":org_name" monitoring instance on Weave Cloud.
View :org_name
Differences:
Sorry, something went wrong.
We don't always have a user_name. There is always a user email, but only a username if they've logged in via github (or google).
user_name
Thanks. I'll amend that.
jml
Successfully merging a pull request may close this issue.
When someone adds you to an instance, you aren't really "invited"—there's nothing to accept or reject. This leads to confusion.
We should send one kind of email when inviting people who aren't existing users, and another kind of email when granting access to someone is a user.
Also, while fixing this, it would be good to ensure that the invite email says "organization" when it should say "instance".
Probably don't fix this until the PRs starting #678 are merged, as they refactor some of the invite stuff.
Part of #618.
The text was updated successfully, but these errors were encountered: