> ## Documentation Index
> Fetch the complete documentation index at: https://docs.minimo.it/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> The few words these pages use, each with one meaning

These pages use one name for each idea. The example app is a restaurant-manager app: replace "restaurant" with your
own kind of customer.

| Word | What it means |
| - | - |
| **Workspace** | Your account in Minimo. You have one for your whole app. Your restaurants never get a Minimo account. |
| **Restaurant** | One of your customers. In the API it is the `tenant` field: a string you choose, such as your restaurant id (`restaurant_4812`). Up to 64 characters: letters, digits, `.` `_` `:` `-`. |
| **Guest** | A person a restaurant sends email to. The API calls it a contact. The same address at two restaurants is two separate guests. |
| **API key** | The `mn-…` key your backend sends as `Authorization: Bearer`. It has permissions: **Widgets**, **Events**, **Transactional**, **Domains**. Keep it on your server only. |
| **Widget settings** | The one-time call `PUT /public/v1/widgets/settings`. It turns on restaurants for your workspace: before it, `tenant` is only a label. |
| **Master template** | An email template you create once in Minimo and list in `masterTemplateIds` of the widget settings. Every restaurant uses it and can personalize its own copy. You name it by its **uid**, a 7-character code like `TRF4MS9` (the UID column in **Templates**). A master is either an automatic message (sent by your API or a rule) or a campaign starter (used in the Campaigns widget). |
| **Service email** | An email the guest needs: booking confirmation, reminder, cancellation. Always sent. In the template editor this category is called **utility**. An automatic message can still be marketing: a review request is. |
| **Marketing email** | Offers, newsletters, review requests. Sent only to guests who agreed to receive them, and subject to [protections](https://docs.minimo.it/guides/embedded-protections.md). |
| **Event** | What your backend tells Minimo happened, for example `booking.created`. |
| **Rule** | Which master template to send for which event, and when: immediately, or before or after a date of the event. |
| **Widget** | A Minimo screen inside your page (send history, statistics, automatic messages, campaigns, contacts, brand). |
| **Session** | A short-lived set of widget links for one restaurant, created by your backend. |
| **Sender** | The From address of an email, for example `bookings@trattoriadamario.yoursaas.example`. |
| **Top-up** | Adding credit in **Settings → Plan & billing**. Until the first one, a workspace sends at most 100 emails a day. |

## Next step

[Start here: the 5 steps](https://docs.minimo.it/guides/embedded-start-here.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.