> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.getzendo.io/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Every notification your clients can get This is the full list of events your clients can be notified about: 31 events in seven groups. It is not the same list as your team's. On the **Clients** tab of **Settings › Workspace › Notifications**, you choose which events a new client starts with, and after that each client can change their own settings. For your team's list, see [Every notification your team can get](https://help.getzendo.io/en/article/every-notification-your-team-can-get-19s0zs4/). ## Channels Clients have the same three channels as your team: **In-app**, **Browser** and **Email**, and you switch each event on or off separately for each channel. **All channels** switches an event in all three at once. **Browser** notifications only work once the client has allowed notifications in their browser. ## Events The descriptions are the ones Zendo shows next to each event. Below each table, you can read how the group differs from your team's list. ### Requests | Event | Zendo's description | |---|---| | New request created | When a new request is submitted. | | Status changed | When a request moves to a different status. | | New request message | When a new message is sent in a request. | | Mentioned in a request | When someone mentions you in a request. | | Intake Form sent in a request | When an Intake Form is sent into a request to be completed. | | Request archived | When a request is archived. | | Request restored | When an archived request is restored. | Two of your team's events are missing here. **Assigned to a request** does not apply, because clients cannot be assigned to requests, and **New request note** does not apply, because notes are internal and clients never see them. ### Chats | Event | Zendo's description | |---|---| | New chat message | When you receive a new direct chat message. Messages in requests are covered under Requests. | Your team has three chat events, but clients have only this one, because notes and mentions in chats are internal. See [Message clients outside a request](https://help.getzendo.io/en/article/message-clients-outside-a-request-1ixx0ns/). ### Quotes | Event | Zendo's description | |---|---| | New quote issued | When a new quote is issued. | | Quote updated | When an issued quote is updated. | | Quote pending approval | When a quote is ready for your approval. | | Quote awaiting payment | When an approved quote is ready for payment. | The last two events exist only for clients. Your team gets the **Quote approved or rejected** and **Quote paid** events instead. Both pairs cover the same two moments in a quote's life: the client is told when they need to act, and your team is told once the client has acted. ### Invoices | Event | Zendo's description | |---|---| | New invoice issued | When an invoice is issued, paid or voided, including invoices for quotes and subscription renewals. | As on your team's list, one event covers issued, paid and voided invoices. ### Subscriptions | Event | Zendo's description | |---|---| | New subscription created | When a subscription starts for the first time. | | Subscription payment failed | When a recurring subscription payment fails. | | Subscription payment pending | When a subscription payment is due. | | Subscription paused | When a subscription is paused. | | Subscription resumed | When a paused subscription resumes. | | Subscription canceled | When a subscription is canceled and will not renew. | | Subscription ended | When a subscription reaches the end of its final paid period. | Two of these events exist only for clients: **Subscription payment pending** reminds the client that a payment is due, and **Subscription ended** tells them that the last paid period is over. ### Forms | Event | Zendo's description | |---|---| | Form shared with you | When an Intake Form is shared with you to complete. | The client is notified when you share an Intake Form with them. Your team, in turn, is notified through **New form submission** when someone submits a form. See [Send an Intake Form to a client](https://help.getzendo.io/en/article/send-an-intake-form-to-a-client-1pgejux/). ### Teams This group exists only for clients. Clients can create and manage their own teams, and these events cover what happens in them. | Event | Zendo's description | |---|---| | Invited to a team | When someone invites you to join a team. | | Added to a team | When someone adds you directly to a team. | | Member accepted an invitation | When someone accepts an invitation to a team you own. | | Member declined an invitation | When someone declines an invitation to a team you own. | | Removed from a team | When you're removed from a team. | | Member left a team | When a member leaves a team you own. | | New member joined a team | When a new member is added to a team you own or administer. | | New member invited to a team | When a new member is invited to a team you own or administer. | | Team ownership transferred by you | When you transfer ownership of a team to someone else. | | Team ownership transferred to you | When ownership of a team is transferred to you. | These events only matter if your clients use teams. Every team has an owner, other people can help administer it, and the owner can hand ownership over to someone else. See [Put clients into a team](https://help.getzendo.io/en/article/put-clients-into-a-team-74h5nv/). ## Clients have no Orders events Your team has an **Orders** group with **New order placed**, but clients do not. They hear about their orders through the quote, invoice and subscription events instead. ## Defaults are only a starting point Each client can change their own notifications. A client who never opens their settings keeps your defaults, and if you change the defaults later, Zendo does not overwrite what a client has already chosen. A notification is not the right tool for a written confirmation when a client submits a request. For that, use an automation with a **Send message** action. See [Automate a request type](https://help.getzendo.io/en/article/automate-a-request-type-1m2cf6k/). ## Related - [Set notification defaults for your team and clients](https://help.getzendo.io/en/article/set-notification-defaults-for-your-team-and-clients-7uej9f/) - [Every notification your team can get](https://help.getzendo.io/en/article/every-notification-your-team-can-get-19s0zs4/) - [Put clients into a team](https://help.getzendo.io/en/article/put-clients-into-a-team-74h5nv/) - [Automate a request type](https://help.getzendo.io/en/article/automate-a-request-type-1m2cf6k/) - [Send an Intake Form to a client](https://help.getzendo.io/en/article/send-an-intake-form-to-a-client-1pgejux/)