# Notices

URL: /products/app/notifications · Id: `page:products/app/notifications`

> How an App tells each person what needs them, in the App, by push, SMS or email, on the schedule that person chose.

An [App](/business/nouns/app) notifies people through [Notices](/systems/notices): in the App, by push, by SMS and by email. The App decides what to say; each recipient decides how and when to hear it.

## What notifies
A notice starts from an [Event](/business/nouns/event) the reader cares about, never from a screen.

| Event at Leaseline | Who hears | Default |
| --- | --- | --- |
| `Lease.notified`, a renewal notice sent | The unit's manager | In the App |
| `Message.created`, a resident's answer | The manager who sent the notice | In the App and by email |
| An [Approval](/business/nouns/approval) waiting on them | Its approver | In the App and by push |
| `Invoice.overdue` | The [Tenant](/business/nouns/tenant)'s `owner` | By email |

Each notice links to the record it is about, opened at the step that needs the reader.

## Each person's choice
Every person sets, per kind of notice, which media reach them, a digest in place of each alert, and quiet hours. A manager at Riverside Property turns renewal alerts into one morning digest, and nothing reaches her at night.

A Tenant's admin sets the Tenant's defaults. A person's own choice overrides them.

## Agents hear too
An [Agent](/business/nouns/agent) member receives the same notices as [Messages](/business/nouns/message) in its context. The [Success Manager](/agents/customer/success-manager) agent hears every resident's answer at once, and answers questions within the hour.

## Next
[Collaboration](/products/app/collaboration) covers people working on one record together.