This page covers features gated by Admin-tier permissions — typically Settings access. Admins have these by default; your administrator can adjust who has them in Settings > Team.
The six groups
Settings is organised into six broad groups. You’ll find them all in the left sidebar under Settings.| Group | What it covers | Start with |
|---|---|---|
| Shop setup | Business identity, opening hours, locations, team members, and Terms of Service. | Shop setup |
| Integrations | Connect a website, courier, card terminal, or relay network. | Integrations |
| Communications | Notifications and automations — emails and texts triggered by built-in events or your own rules. | Communications |
| Customer programmes | Loyalty, gift cards, and the two friend-referral schemes. | Customer programmes |
| Advanced | Devices, delivery slots, tax rates, payment methods, email drivers, banners. | Advanced |
| Logs & recovery | Audit history and disaster recovery — the paperwork you reach for when something needs investigating or undoing. | Audit Logs |
A sensible setup order
If you’re setting up a fresh instance, work through Settings in this order. Required steps are flagged; the rest you can come back to once orders are flowing.Shop setup — required
Your shop name, contact details, opening hours, default tax rate, and dashboard preferences. The rest of the docs assume this is filled in. Open Shop setup.
Locations — required if you have more than one shop
Add each physical location you operate from. A single-shop florist can skip ahead. See Locations.
Team — required
Invite your staff, drivers, and managers. Pick role presets first and fine-tune individual permissions later. See Team.
Integrations — optional
Connect anything outside Digital Florists — your website, a card terminal, a courier, or a relay network. See Integrations.
Communications — strongly recommended
Decide which order milestones trigger an email or SMS to the customer, and add your own rules where the built-in events don’t fit. See Communications.
Customer programmes — optional
Turn on loyalty, issue gift cards, or enable referral schemes. See Customer programmes.
Advanced — as needed
Register POS devices and set delivery slots. See Advanced.
General vs Advanced
Settings splits the technical plumbing into a separate area to keep day-to-day controls easy to scan.- General (the Shop setup page) covers your shop’s identity and operating rules: business details, opening hours, dashboard preferences, default tax rate, delivery slots, and event types.
- Advanced covers the technical plumbing: registered POS devices, payment-method definitions, tax rate list, email sending domain, data migration, and banners.
Winding down or exporting paperwork
When you’re closing out a quarter, responding to a query about an old order, or untangling who changed what — head to Logs & recovery.- Audit Logs — a searchable record of who did what and when.
- Disaster Recovery — roll the shop back to an earlier point after a serious incident.
Common questions
Who can access Settings?
Who can access Settings?
By default, only the Admin preset can open Settings. Your administrator can grant the Settings (Admin) capability to other users in Settings > Team.
Do I have to set everything up before going live?
Do I have to set everything up before going live?
No. Shop setup, Team, and Terms of Service are the only required steps. Most shops are up and running within an hour and add the rest as needed.
What's the difference between Notifications and Automations?
What's the difference between Notifications and Automations?
Notifications are template-driven messages tied to built-in product events. Automations are rules you build yourself with custom triggers, conditions, and actions. See Communications for the full breakdown.
What’s next?
Shop setup
Shop identity, hours, and dashboard preferences.
Team
Invite staff and set permissions.
Communications
Notifications and automations in one place.
Integrations
Connect websites, couriers, and card terminals.
Customer programmes
Loyalty, gift cards, and referrals.
Audit Logs
Who changed what, and when.