Platform
The dashboard
What your customer works in every day, and which settings decide how your integration behaves.
Half the questions an integrator has are answered by a screen they have never seen. This page walks through the dashboard, with the settings that change what your site sees called out as they come up.
The workspace
A sidebar of the modules this organization runs, an organization switcher at the top for people who belong to several, and a keyboard-driven command palette that jumps to any screen or setting without hunting for it. Modules that are off are not in the list at all.
Live data updates without a refresh. A new order appears on the board, a colleague's status change lands on your screen, and a reservation being read by someone else shows you that they are there. Nobody presses reload, and two people cannot quietly answer the same request.
Notifications
In-app notifications for the things that need answering, with per-user preferences for which ones arrive and per-organization rules for who is told about what. Web push is supported, so a kitchen tablet can be woken by an order while the tab is in the background.
None of this needs anything from your site. It is worth knowing about because it is the reason your storefront does not have to nag anyone: the order has already arrived somewhere it will be seen.
Organization settings
| Section | Holds | Affects your integration |
|---|---|---|
| General | Name, logo, and the venue timezone. | Yes. The timezone is what calendar_timezone resolves to, and every opening hour depends on it. |
| Members | Invitations, roles, removals. | No, but the role model is in Core concepts. |
| Modules | Which modules are on. | Yes. A module that is off makes its endpoints answer 403. |
| Sender, SMTP, templates. | Indirectly. It decides what your buyers receive after you post. | |
| Tax | Rates, country and inclusive pricing. | Yes. See Tax. |
| API Keys | Creating, scoping, expiring and revoking keys. | Yes. Your key lives here, and so does its rate limit. |
| AgnusPAY | Onboarding, methods, fees, payouts, transactions. | Yes. It decides whether a checkout is possible at all. |
Module settings
Each enabled module adds its own panel. These are the settings most likely to explain surprising behaviour in a working integration.
| Panel | Decides |
|---|---|
| Content Management | Content types, fields, and which type is the catalog. Also the generated integration brief. |
| Online Ordering | Which content type holds the menu, and which field is the price, the image, the category and the tax rate. |
| Restaurant Ordering | Fulfillment types, preparation times, kitchen ticket layout, printers and receipts. |
| Promotions | Automatic promotions, discount codes, priorities and limits. |
| Reservations | Opening hours, slot interval, date overrides, party size cap, and whether reservations arrive as requests. |
| Bookings | Availability and the confirmation emails. |
| Contact Form | Notification recipients and templates. |
The integration briefs
Several module panels can generate a written brief for whoever builds the site, filled in with this organization's own base URL, id, content type slugs, mapped fields and enabled options. Your customer copies it and sends it over.
It is worth asking for. These pages describe the platform; that brief describes the one account you are building against, including the slugs you would otherwise have to guess.
Personal settings
Profile, password, interface preferences including the dashboard font, and which notifications reach this person. Per user, not per organization, so someone working across several businesses carries their preferences with them.