Settings is where your organization's profile, its team, its notifications and its automations live. You need the Settings · View permission to open the page at all. Most of what you can change there needs a further permission, named on each section below.
The tabs, and what each one controls
Settings is split into two groups in the left-hand menu.
Organization
- General — your organization's profile and branding: name, workspace URL, primary organization type, website, phone, timezone, business hours, logo, brand colours and description.
- Notifications — the organization-wide email toggles described below.
- Team — your active member and pending invitation counts, with a link through to Manage members & invitations. Members are managed on their own page, not here.
- Calendar & Integrations — how many calendar connections you have, and a link to Manage calendar sync.
- Marketplace — how your organization appears to performers on the ARRIVE Marketplace.
- Billing — opens the Billing page: your plan, Free and Pro side by side, and Manage billing. Your organization runs on a single subscription covering all of its locations and spaces; booking charges are handled per booking.
Advanced
- Security — your ARRIVE account, not this organization: password, two-factor authentication and session controls. ARRIVE is one account across the marketplace and Organization OS, so anything you set here applies in both.
- Permissions — the role and permission matrix. Visible only to holders of Settings · Administer; everyone else sees an explanation instead.
- AI — which ARRIVE AI surfaces are switched on for the organization and for you personally. See ARRIVE AI: what it does, and what it keeps.
- Automation — the four automations, covered in detail below.
- Activity Log — the organization-wide audit feed. Also Settings · Administer only; per-item Timeline tabs stay visible to every member.
- Advanced — data export, activity-log retention, and the danger zone. See Exporting your data and Leaving or deleting an organization.
Your organization profile
General holds: Organization name (required), Workspace URL (slug), Primary organization type, Website, Phone, Timezone, Business hours, Logo URL, Primary color (hex), Secondary color (hex) and Description. Changing the slug changes your workspace URL, and if the one you pick is already taken you'll be told so rather than silently given another.
Three things to know before you edit:
- The logo is a URL, not an upload. There is no file picker on this form — paste a link to an image you already host. Uploading a file to your organization is done in Assets, which is a different thing.
- Saving posts the whole form. A field you clear is cleared — the form doesn't merge your change into what was there before, it saves exactly what's on screen.
- Timezone is the fallback. A booking or opportunity uses its location's time zone; your organization's is used when there is no location. Changing it later doesn't move anything already posted or booked — each keeps the time zone it was made in.
General, Notifications and Marketplace all save with the Organization · Edit permission. Without it those panels are read-only and say so.
Organization-wide notifications
These three toggles are organization-wide — they apply to everyone, not just you.
- Booking updates — "Team-wide email when a booking is confirmed or cancelled. Turning this off mutes it for every member; event reminders always send." On unless you change it.
- Weekly digest — "A weekly summary of activity across your organization." On unless you change it.
- Member activity — "When members join, leave or change roles." Off unless you change it.
Worth being straight about: of these, only Booking updates currently changes what ARRIVE sends. Switching it off stops confirmation and cancellation emails for everyone in your organization — the in-app bell still appears, and event-day reminders send regardless, by design. Weekly digest and Member activity save your preference, but nothing reads them yet; the emails they describe aren't being sent either way.
Your own booking emails
Each member can also turn off booking emails just for themselves. Open your account menu → My notifications (it's also in the Settings sidebar) and switch off Booking emails. That stops emails about your organization's bookings — answers to requests, payments due, confirmations, cancellations and messages from performers — for you only, in every organization you belong to. You still see every update in the app.
Some emails always send: event reminders, a payment due soon, a payment window that has closed, a no-show refund, ARRIVE's decision on a dispute, and messages in your team's own threads.
Booking updates above still comes first: when it's off, nobody gets confirmation or cancellation emails, whatever their own switch says.
Marketplace visibility
- Show organization name to performers — "Performers see your organization's name on bookings and opportunities." On unless you change it.
- Auto-share opportunities — "Automatically share new opportunities with matched performers." Off unless you change it.
Both are saved preferences today. Neither yet changes what performers see — treat them as a stated intention rather than an active control until this article says otherwise.
Automations
There are exactly four automations, and no automation builder. You cannot describe a new trigger, a new condition or a new action from inside the product. The set is fixed in code, each one was reviewed individually, and anything not on the list is refused before it can run.
Every member can see this panel — being able to see what runs unattended in your organization is not an admin privilege. Changing any of it needs Settings · Administer, the same permission that governs the activity log and retention. Every change, and every action an automation takes, is written to your activity log.
Booking reminders — a setting, not an action
Chooses which of three reminders your team receives before a confirmed booking: One week before, 24 hours before, Morning of the event. Keep at least one switched on — the form refuses an empty selection. Reminders go to members with booking access, as an in-app notification and an email.
These are your team's reminders. The performer you've booked gets their own before the event — 14, 7, 5 and 3 days before, and on the day — and this setting doesn't change those.
While this is off, all three send. To undo: re-enable the offset, and the next reminder in that window sends normally.
Program scheduling window — a setting, not an action
How far ahead recurring programs create their events, between 30 and 365 days. While this is off, programs use the standard 90-day window. Shortening it never removes events that already exist — it only stops creating new ones further out; delete any you don't want.
Auto-publish events — this one acts
Moves draft events to planned as their date approaches, between 1 and 90 days ahead. Only future, non-archived drafts are touched. While it's off, drafts stay drafts until someone moves them. To undo: set the event back to Draft from the event page.
Close expired opportunities — this one acts
Stops your organization's own opportunities accepting applications once the deadline has passed, after a grace period of 0 to 168 hours. An opportunity with a booking in progress is left alone, and one with no deadline is never closed. While it's off, opportunities stay open after their deadline until someone closes them by hand. To undo: reopen the opportunity, or duplicate it with a new deadline.
The safety guarantee
None of these four books, charges, refunds, cancels or deletes anything. That is a property of the system, not a promise we're asking you to take on trust: each automation is declared non-destructive where it is defined, an automation that moved money or deleted a row could not be expressed there at all, and the engine re-checks that declaration before it acts on anything.
The two that act are also safe to run twice — each one re-checks the state it's changing as it changes it, so a repeat run does nothing rather than doing it again.
What this does not do yet
Until an automation has actually done something, its card reads "Hasn't run yet" rather than showing you a fabricated count. The two acting automations run once a day; the two settings tune jobs that were already running.
There is no automation builder, no per-automation schedule, and no way to add a fifth. Single sign-on, IP restrictions and backup & recovery are not present on the Advanced tab — they're absent rather than shown as disabled, because a control nobody can switch on is an advertisement, not a setting.