Here is the complete list of events that trigger a transactional email.
- You finish setting up a workspace.
- Someone invites you to join a team.
- You invite someone to a team. After they accept, assign the user groups their work needs. Joining the team does not grant that access.
- Someone invites you to administer an organization.
- You invite someone to administer an organization. The people who already administer it are emailed.
- Someone accepts an invitation you sent, to a team or to administer an organization.
- Your team buys a plan, renews one, or changes one.
- Your team buys Ask AI credits.
- A subscription is canceled, set to end on a named day, paused, or resumed. A cancellation set for later also goes to the other people who manage billing.
- A payment for the team's subscription fails.
- The card on file is replaced. Adding the first card at checkout does not send this one.
- You delete your account. Profile and team memberships are cleared within 3 to 5 days.
- You change your password.
- Someone submits a widget, collection, or ruleset for you to approve. The person who submitted it is left out.
- A reviewer approves or rejects a publish request you submitted. Withdrawing the request sends nothing.
- An administrator removes you from a permission group.
- You are given permission to manage billing, or to publish to Production.
- You leave feedback while signed in.
- You create your first widget, your first collection, or your first widget-selection ruleset. The Default Widget from setup does not count, and a second create does not send another.
- You publish your first widget, collection, or ruleset to Production. A later version, and a Staging publish, do not send another.
- You unpublish a ruleset on Production. Staging and Development stay quiet.
Creating an account sends a separate message that asks you to verify that address. That message is not in this list.