This page is a reference for every screen under Settings in the admin. Each section says what the screen controls, who can open it, and where to read more. Settings are grouped the way the settings menu groups them: Business, Process and Portal, plus your personal Security page.

How settings are organised#

Open Settings from the avatar menu in the admin. The left-hand menu lists only the screens your role can open. Each screen has its own permission, so you can, for example, let an ops manager edit order statuses without touching payments.

Group	Screens
Business	Company, Payments, Team, Modules, Integrations, Storage, Import
Process	Orders, Tickets, Clients, Messaging, Saved replies, Tags, Templates
Portal	Portal menu, Dashboard, Emails, Email templates, Language, Logs
Personal	Security (avatar menu → Security)

Every settings change is recorded in Settings → Logs.

Business#

Company#

Route: /settings · Permission: Company

Your name, five logo slots and alt text, primary and accent colours, timezone, currency, business address, contact link, How clients reach you (contact person, photo and channels), Sales page (guarantee, testimonials, policies), Trustpilot Reviews, and Export / Import of the whole page as a JSON file.

The currency can change only until the first invoice, payment or checkout.

Read more: Branding and white-label.

Payments#

Route: /settings/payments · Permission: Payments

• What can take money: a read-only list of connected gateways and their state.
• Ways to pay that aren't a gateway: account credit and invoices.
• Manual payment: offer payment to your own crypto wallets, with instructions and up to 10 wallets; your team confirms each one.
• Currency: shows the workspace currency (set on Company).
• Tax: name, rate, tax-inclusive or exclusive prices, registration number.
• Processing fee: a name, plus a percentage and fixed fee per gateway, charged to the buyer.
• Dunning: retry days for declined subscription cards and what to do after the last retry, days until a hand-paid subscription invoice is due, renewal reminders, and whether Clients may change their plan and Clients may cancel.

Read more: Checkout and payments, Invoices and credit, Subscriptions.

Team#

Route: /settings/team · Permission: Team policy

Default role for invitations, Tell the team when someone joins, Require two-factor authentication for every admin account, and Sign out inactive sessions after 15 minutes, 30 minutes, 2 hours or 8 hours.

Members and roles themselves are managed on the Team page (avatar menu → Team).

Read more: Team and permissions.

Modules#

Route: /settings/modules · Permission: Modules

Turn parts of the product on and off. A module that's off disappears from your team's menus and your clients' portal, its pages and API routes answer as though they were never there, and its permissions stop working for every role. Nothing is deleted. Turn it back on and everything returns as it was.

Module	Always on	Covers
Orders and delivery	Yes	Orders, deliveries and hand-overs.
Clients	Yes	People and companies.
Store	Yes	Services and their pages.
Invoices and payments	Yes	Invoices, payments, refunds and credit notes.
Settings	Yes	These screens.
Helpdesk	No	Tickets in the admin, Support in the portal, Ask for a quote on service pages, and Settings → Tickets.
Messages	No	Client, order and team chat, and Settings → Messaging.
Coupons	No	Discount codes and the code field on service pages.
Subscriptions	No	Recurring plans billed on a schedule.
Referral program	No	Partners, commissions and payouts.
Forms	No	Lead and onboarding forms with their own public page.
Traffic tracking	No	Short links and visit tracking for services, forms and signup.

Each module's card shows what turning it off hides, and asks you to confirm.

Integrations#

Route: /settings/integrations · Permission: Integrations

Connect the services ClientOS sends data to. Every key you paste is checked against the provider before it's saved, and sealed (encrypted) at rest.

Integration	What it's for
Stripe	Card payments, saved cards and automatic subscription charges.
PayPal	PayPal checkout.
NOWPayments	Crypto payments.
CoinGate	Crypto payments.
BTCPay Server	Bitcoin payments through your own BTCPay Server.
Resend	All outgoing email, delivery reports and inbound email into tickets.
Cloudflare Turnstile	Bot protection on signup, quote requests and public forms.

For each payment gateway you can connect (test or live keys are detected automatically), see the Checks, see whether its webhook is registered under Callbacks, switch Offer the gateway at checkout on or off, Verify the connection, replace keys, and disconnect. Webhooks are registered automatically where the provider allows.

Meta Conversions API isn't here; it's set up under Sales → Ad platforms (/sales/ads). See Leads and tracking.

Read more: Checkout and payments, Notifications and email.

Storage#

Route: /settings/storage · Permission: Storage

One bucket holds every file in the product: logos, deliverables, attachments, receipts and invoice PDFs. Out of the box it's the storage the installer set up on your server, and the screen says so. To keep files in Cloudflare R2 instead, save a bucket here; it takes over from the next upload, so copy existing files across first.

Setting	What it is
Account ID	From the R2 overview in Cloudflare.
Bucket name	The bucket ClientOS writes to.
Jurisdiction	Must match the bucket; fixed when the bucket is created.
Access key ID / Secret access key	An R2 API token with Object Read & Write, scoped to that one bucket.
Public URL	A custom domain on the bucket, or its r2.dev subdomain, used to serve logos. Leave empty to serve logos through the API instead, which works everywhere but is slower.
Signed URL lifetime	How long a link to a private file keeps working.
Maximum file size	The largest upload allowed.

The screen also shows the derived S3 endpoint, runs Connection checks with a remedy for anything that fails, and gives you a CORS policy to paste into the bucket's settings. Files are private by default and served through short-lived signed links; the bucket itself is never public.

Read more: Moving files to Cloudflare R2.

Import#

Route: /settings/import · Permission: Import

Bring your history from Wayfront into ClientOS: clients, orders, messages, invoices and files. Migrations are done with our help as part of assisted setup.

How it works:

1. Click Start an import. You receive a one-time code and a command.
2. The import package, prepared from your Wayfront account, is uploaded to your workspace's storage with that code.
3. Click Check the import. This is a dry run: nothing is written. It shows how many New clients, Existing clients (same email already here, so history is added to them), Orders, Invoices, files, team members and services it will bring in, and any problems that would stop it.
4. Take a database backup, then click Apply and say when the backup was taken.

Nothing is written until you apply, and nobody is emailed or notified during an import. Imported services arrive archived, former staff arrive as inactive, and imported invoices are never chased by overdue reminders. Earlier imports lists every import with what it brought in.

Process#

Orders#

Route: /settings/orders · Permission: Order settings

• Statuses: rename and recolour the six built-in steps (Awaiting brief, In progress, Delivered, In revision, Completed, Cancelled), and add your own to set by hand.
• After delivery: Lock completed orders, Re-open on revision (with an optional limit in days after delivery), Ask for a rating.
• Waiting on the client: Auto-approve after a wait, with the number of days.
• Team checklists: Add checklists to new orders, and when steps are still open at final delivery, Warn, then deliver or Don't allow delivery.

Read more: Orders and delivery.

Tickets#

Route: /settings/tickets · Permission: Ticket settings · Needs Helpdesk

Two tabs:

• Statuses and rules: ticket statuses; what a team reply does (Move it to Pending or Leave the status as it is); A client's reply reopens the ticket; Close pending tickets automatically after a number of days; First response targets in hours per priority, optionally counting only business hours; Ask for a rating when a ticket closes.
• Replies and email: Reply automatically to a new ticket (always, or only outside business hours), Business hours per day with a timezone, a Signature, and Email into tickets (receiving address, inbound webhook URL for Resend and its signing secret).

Read more: Support tickets.

Clients#

Route: /settings/clients · Permission: Client settings

• Statuses: rename, recolour, reorder, add and delete client statuses.
• Signing up: Enable the signup page, Block free email providers, Require a company name. These are enforced by the server, so switching the page off closes signup entirely.
• Custom fields: up to 50 fields of type Text, Number, Date, Dropdown or Checkbox, optionally required and optionally shown in the portal.

Read more: Clients and companies.

Messaging#

Route: /settings/messaging · Permission: Messaging · Needs Messages

Email reminders when a chat message goes unanswered:

• Remind the team when a client is waiting and Remind the client when the team is waiting on them, each with up to three reminders (First reminder, Second reminder, Third reminder) set in hours after the message.
• Which conversations: Each client's general conversation and Order conversations.

Read more: Messages and files.

Saved replies#

Route: /settings/saved-replies · Permission: Saved replies

Answers your team sends often, written once and inserted in a ticket, a chat or a delivery.

• Each reply has a Name (team only) and a Body, which can use variables filled in when the reply is inserted.
• Share with the team makes it available to everyone; off keeps it in your own list.
• Send automatically lets a shared reply go out by itself. Under Auto replies, pick which reply is sent when a client writes in their general chat for the first time.

Tags#

Route: /settings/tags · Permission: Tags

Your own labels for orders, tickets and clients. Each tag has a name, a colour and where it's offered: Any record, or only Orders, Tickets or Clients. Reorder them with the arrows. Tags are internal; clients never see them. Deleting a tag removes it from the records that carry it and deletes nothing else.

Templates#

Route: /settings/templates · Permission: Task templates

Checklists of the steps your team takes on an order, added as tasks automatically when a new order comes in.

• Name and Applies to: Every order or one service.
• On — add these steps to new orders.
• Show progress to the client: the client sees each step's name and a tick when it's done on their order page, never who's doing it or any notes.

Deleting a template stops new orders getting its steps; existing orders keep theirs.

Read more: Todo and checklists.

Portal#

Portal menu#

Route: /settings/portal-menu · Permission: Client portal

The sidebar every client sees: the focus button, renaming, reordering, hiding and grouping links, and up to eight custom links.

Read more: Branding and white-label.

Dashboard#

Route: /settings/portal-dashboard · Permission: Client portal

The client's Overview page: which cards show and in what order, a welcome message, a welcome video (YouTube or Vimeo), and the star-rating feedback card with the answers clients gave.

Read more: Branding and white-label.

Emails#

Route: /settings/emails · Permission: Emails

Sender name, sender address and reply-to, Send me a test, the Bounces and complaints suppression list with Resend's webhook status, and an Email and In app switch for every notification.

Read more: Notifications and email.

Email templates#

Route: /settings/email-templates · Permission: Emails

Edit the subject, preview line, heading, opening, button and closing of every email, with variables and a live preview by format, width, colour scheme and recipient.

Read more: Notifications and email.

Language#

Route: /settings/language · Permission: Language

Rename the words clients read in the portal: menu labels, overview text and page headings. This renames words; it doesn't translate the interface, which is in English.

Read more: Branding and white-label.

Logs#

Route: /settings/logs · Permission: Audit log

The audit log: every change made through the product, who made it, the area, the record and when. It's append-only and read-only. Filter by Area, Who (a person or Automatic) and Record.

Read more: Team and permissions.

Security#

Route: /settings/security · Everyone

Your own account, reached from the avatar menu → Security:

• Two-factor authentication: set up or turn off an authenticator app, with backup codes.
• Password: set or change an optional password (at least 12 characters). You can always sign in with an emailed code instead.
• Where you're signed in: every open session, with sign-out.
• Your notifications: your own in-app and email switches.

Tips#

• After installing, work through Integrations (Resend), Emails, Storage and Payments before inviting anyone. See First run.
• Turn off modules you don't use. Your team's menus and your clients' portal get simpler, and you can turn them back on any time.
• Give each settings permission only to the people who own that process.