Business settings

Admin is where a business is configured. Open it from the sidebar. The rail on the left groups the sections:

Group	Sections
Business	Company, Depots, Pricing, Time and costs
People	Staff, Roles
Fleet	Vehicles, Work phones
Work setup	Service forms, Councils, Recurring work
Customers	Messages, Email and SMS, Documents, Payments, Online booking, Reviews
Assistant	AI, Phone agent, Calls
System	Integrations, Alerts, Audit log, Deleted items
Extensions	Plugins, Branding, Hooks, plus any pages a plugin adds

What you see depends on your permissions. Sections that need one you don't have say "You don't have access to these settings."

This page covers the sections without a page of their own. Staff and Roles are in users and roles. Payments, Email and SMS, Integrations, Online booking, AI, Phone agent and Plugins have their own pages from the setup checklist.

Company

Needs organizations.manage.

Field	Notes
Trading name	Shown in the console frame, on documents and in messages
ABN	Shown on invoices
Status	Active or not
Timezone	Used for "today", reminders and schedules. Set it right first
Billing email	Where billing and Stripe mail goes
Default country, Default currency	AU and AUD for most
GST registration	Whether GST is charged

The slug (the short name in your booking form address) is read-only. A "Tenant settings" box takes extra key=value lines for developers.

Below that, "Billing and subscription" shows the product's own subscription (plan, seats, period, payment) with checkout and portal buttons. It matters only to installations hosted by Rangefront Labs on a subscription plan. A self-hosted installation with a one-off licence can ignore it, and it says "Stripe keys are not configured in this environment" when billing isn't set up.

Depots

Needs branches.manage. A depot has a name, short code, address, coordinates, phone, email and opening hours. Mark one as the default. Technicians start their run from a depot, so add the coordinates (the Runs page can't measure a run without them). Depots can be deleted.

Pricing

Needs the invoices permissions. Pricing has two parts.

Price books. A price book has a key, name, currency, effective dates and rate items. Mark one as the default book. Each rate item has a code, a description, a unit, a unit price ex GST, a GST percent and optional filters for job types and system types. Price books feed invoices, quotes and job charges (pump-out volume, labour, disposal and travel).

Customer price overrides. A special price for one customer for one item, optionally for one price book and between two dates. It beats the book.

Time and costs

Needs time.manage or the costing permissions. Sets the overtime thresholds, the week's start day, default cost per hour, default disposal cost per kL and the cost of each disposal site. Details are in time and costing.

Vehicles

Needs branches.manage. Add each tanker and service vehicle with a name, registration, type, depot, tank capacity in litres, running cost per hour and per km, and whether it's in service. Vehicles can then be put on jobs and runs. Removing a vehicle keeps it on past jobs.

Work phones

Needs mobile.manage_devices. Each phone appears here with its user, platform, last sync and status. Choose "Manage" to rename it, change its status or revoke it. Revoke a phone (or mark it lost) as soon as it's lost: the next time it connects it's refused everywhere, not just at sync, and clears the records saved on it. Work it hadn't sent yet stays, encrypted, until it's linked again.

Link a phone

Every business uses the same Rangefront Waste app from the App Store or Google Play. Link a phone to your business like this:

1. Choose Link a phone, pick the person, and choose Make code. Only people whose role has "Enrol a phone" (mobile.enroll_devices) are listed.
2. On their phone, open the field app, go to Settings, choose Link with a code, and scan the QR code on your screen. If the camera can't be used, type the server and code shown beside it.
3. The phone shows your business name, the person's name and the server. They check it and choose Link this phone.

Nobody types a password on the phone. The code works once and lasts 15 minutes. Making a new code for the same person cancels the old one, and closing the sheet cancels a code that wasn't used. Only a fingerprint (hash) of the code is stored, and wrong codes are limited to 10 per 10 minutes from one address.

People on a Rangefront-hosted business can also sign in on the phone with their email and password instead.

Service forms

Needs templates.manage. A service form is the checklist a technician fills in on site. It has a key, name, jurisdiction, report type (Service report, Pump-out record, Inspection report or Certificate), a version, the keys of required photos, sections and fields.

Each field has a key, label, type (Boolean, Number, Text, Textarea or Select), whether it's required, and options for a Select. Use Add field, Up and Down to build it. "Field app preview" shows how it'll look on a phone.

The standard commissioning certificate form is installed for every business. Install it for a new business with php artisan rangefront:install-defaults {organization}, which also installs the standard messages. See install.

Councils

Needs reports.submit_to_council. Each council profile says how that council wants reports (Email, Portal, SFTP, API, Manual upload or None), the business-day deadline, a default report template, whether the owner needs a copy, an external portal URL and account reference, and the delivery settings for the method. It can apply to all depots or one.

Compliance packs for each state and territory ship with the software and carry the state rules and their official sources. They're starting points. Check them against the council you deal with. How reports then flow is in compliance reports.

Recurring work

Needs recurring.manage. "Raise visits ahead by" sets how far ahead the morning job makes draft visits for recurring plan dates and system services coming due. It starts at two weeks. Pick at least as far ahead as you plan your runs, or due work will not be in Build runs when you group. How the cycle works is in recurring work.

Messages

Needs notifications.manage. Two lists:

• Templates. A key, event, channel (email, SMS, push, in-app or websocket), subject and body. You must render a preview before you can switch a template on.
• Rules. An event, channel, recipient type, the template, whether it's on, timing (an offset in minutes) and quiet hours.

The standard templates and rules are installed switched off. Turn on the ones you want. Events include booking confirmation, service reminder, on the way, completed service report, invoice sent, payment receipt, urgent breakdown assigned, quote sent and reminder, invoice reminders, statements, defect notices, review requests and more. Recipients can be the customer, customer contacts, site contacts, the assigned technician, dispatchers, owners or a custom list.

Below the lists is the Delivery log of every message sent. A service reminder rule's offset sets how many days ahead it looks (one day if blank).

Reviews

Needs notifications.manage. Campaigns ask for reviews, follow up quotes, reactivate old customers or ask for referrals. A campaign has a type, trigger, channel (Email or SMS), delay in minutes, cooldown in days, a template and a review URL. A run ledger tracks each message as queued, sent, failed, skipped or converted. "Queue review request" lets you queue one by hand for a completed job. Customers who've opted out are skipped.

Alerts

Needs analytics.read to see results and notifications.manage to change rules. Rules watch for trouble and feed System checks on Today. Each rule has a threshold, severity, repeat interval, channels, recipient roles and users, quiet hours and an escalation policy. The built-in rules are: council reports overdue, council reports rejected, services overdue, high-severity defects open, invoices overdue, mobile devices stale, systems missing a tank location, uploads pending or failed, and outgoing webhooks failed.

Alerts are checked and delivered every 15 minutes by the scheduler. See install. The delivery log shows each notification with its provider status and has Resend for transient failures.

Audit log and Deleted items

Audit log lists every change with who and when, and can be filtered by record type and date. Deleted items restores customers, sites, systems, bookings and vehicles. See reports.

Branding

Needs organizations.manage. Branding picks a theme (Default or Slate), lets you override colours and the font, and warns when a colour pair fails the WCAG AA contrast ratio of 4.5 to 1. You can still save with a warning. Only fonts bundled with the console are offered. The theme's colours apply to the console and to PDFs, and its email layout and PDF header are part of it. The public pages (quote, pay, tracking and booking) don't pick it up yet. Developers can read how themes work in developer/themes.

Documents

Logo, accent colour, business details, email layout and wording, report and invoice numbering and the report builder have their own page: document templates.