Basics | Notion

Every message Airstudio sends on your behalf, from a booking confirmation to a payroll approval, is a notification. This page explains the pieces, where they live, and how a message travels from an event in the system to a recipient's inbox or phone.

The pieces

Term	What it is
Notification	A named event Airstudio watches for, such as Session Booked or Employee Job Reminder. Each one can be switched on or off per channel and carries its own templates, recipients, and timing.
Channel	Email, SMS, or Push. A notification can use any combination. Email needs an Email Sender, SMS needs Twilio, Push reaches employees signed in to the mobile app.
Template	The content for one channel: subject and body for email, message text for SMS, title and body for push. Templates use variables such as `{{ subject_first_name }}` that are filled in at send time.
Recipients	Who receives it. Fixed for most defaults (the subject, the organization's invoice contacts, the assigned employee) and chosen by you for custom notifications and task rules.
Sends / Starts / Until	The timing rule: what date the notification measures from, how far before or after it fires, whether it repeats, and what stops it.
Sent Notifications	The log of every attempt: who, when, which channel, whether it was delivered, opened, or clicked.

Three levels of templates

Your studio starts with a complete set of default notifications under Settings › Notifications. When you create an organization or a subject group, Airstudio copies the relevant defaults onto it, so each client and each program can carry its own wording, logo, and timing without touching the studio defaults.

Level	Where to edit	Use it for
Studio default	Settings › Notifications	Your house style. Edit these before you add clients.
Organization	Organization › Notifications tab	Client-specific wording, the client's logo, invoice reminders on their terms.
Subject Group	Subject Group › Notifications tab	Booking campaigns, session reminders, and payment receipts for one program.

Changes at one level do not flow to the others automatically. Sync copies a template from any level onto one or many organizations or subject groups when you want them aligned again.

<aside> 💡

Review every default before you import your first organization. A default you fix later is only fixed for organizations created after that point, unless you sync it out.

</aside>

Where notifications are sent from

Automatically, when the event happens or the scheduled time arrives. Most of the defaults work this way.
On demand, from a subject group, organization, job, session list, or employee, using the Send Notification button. You choose the audience and can edit the message before it goes.
From a task, when a task rule fires on a status change, due date, or event date.
Quick email, by clicking any email address in Airstudio to compose a one-off message.

From event to inbox

An event occurs or a scheduled tick arrives.
Airstudio finds the notification at the most specific level available (subject group, then organization, then studio default) and checks that the channel is enabled and the job's notifications are not disabled.
Recipients are resolved. Anyone who has turned off email or SMS in their preferences is skipped, except for account and security messages.
The template is rendered with live data.
The message is handed to your Email Sender, Twilio, or the push service, in batches that respect the sender's rate limit.
A row is written to Sent Notifications with the outcome, and opens and link clicks are tracked from there.