Users
| User | Access Group | Last login | 2FA | Status | |
|---|---|---|---|---|---|
| Loading... | |||||
Access Groups set ordinary visibility and work access. Choose a group on the left, then rename it, manage its users and set its modules on the right. Refunds, approvals, case closure and other controlled actions stay under Special Permissions. Quasar AI module access controls the management workspace; the top-bar AI chat keeps its own access and checks each requested business action. An Access Group is not a People Department: the names may be similar, but changing one never creates, assigns or changes the other.
Loading...
Team Chat Channels
| Channel | Who can open it |
|---|---|
| Loading... | |
All Chat remains available to everyone. Create only the private or open channels you need, then choose their members. Access Groups and departments never create channels automatically.
People Departments
Directory organisation only| Department | Members | People | |
|---|---|---|---|
| Loading... | |||
Directory only. Departments organise where people sit in the company. They never grant modules, functions, approvals or Team Chat channels, even when a department and an Access Group have the same name.
Work-from-home eligibility
Choose who may clock a work-from-home day. The clock-in location gate enforces this setting server-side.
Loading...
Assigned WFH days
Assign weekly recurring days or specific dates for the people selected above. Applies to phone and desktop clocking.
Money approval layers (who approves refunds, credits and replacements by amount - RMA money path)
Money approval layers
app_settings 'approvals.money_rules' - admin-only, auditedLoading...
These layers are server-enforced only on the RMA money-intent path (G-R3). RMA decision approvers control who may choose the case outcome; Refund authorisers separately control the primary Finance > Refunds & credits flow. On the RMA money-intent path, the named unlimited-RMA approver authority bypasses the amount limit but not a required named-person gate. A saved change applies from the next authorisation attempt, with no deploy needed. When an amount exceeds every layer the requester holds, HQ notifies the roles named in the covering layer.
Manufacturing settings (line names, proposal snooze and build-time thresholds)
Manufacturing settings
app_settings 'manufacturing.lines' / 'manufacturing.proposal_snooze_days' / 'manufacturing.sla' - admin-only, auditedRetired (HQ-1434): production lines now live in Manufacturing > Scheduling > Production > Lines, with their hours per day and crew. This list only seeded them once; the Line View wall, each line's tablet and the scheduling pickers read Manufacturing's lines. Edit lines there, not here.
How long a dismissed stock-shortfall suggestion stays snoozed before the 30-minute proposal rule may raise it again. Default 7 days.
A build using more than this percentage of its target time shows red on the order page, the orders board, the line screens and the leadership report. Between 100% and this line shows amber; at or under target shows green. Default 120%.
How long after release a unit should start before its Started badge turns red (amber past half this time). Default 24 hours.
How long after completion a finished order should reach the warehouse before its Received badge turns red (amber past half this time). Default 24 hours.
Support targets (SLA hours and team targets)
Support targets
app_settings 'support.sla_hours' / 'support.sla_nearing_hours' / 'support.weekly_case_target' / 'support.avg_resolve_target_hours' - support manager or admin, auditedHow long a case may stay open before the Dashboard's Breaching SLA tile counts it. Time a case spends On Hold or Waiting Customer Reply is not counted. Also the target a resolved case's own SLA record is stamped against. Leave blank to leave Breaching/Nearing SLA unconfigured (they show 0, honestly, rather than a made-up cap).
How close to the cap above counts as "Nearing SLA" (and the per-case amber warning on any open case). Default 4 hours.
Shown as a Target/wk column on the Dashboard's Team Performance card, next to each person's actual Closed count. Leave blank to hide the column entirely.
Compared against the Dashboard's Avg Time to Resolve tile (on target / over target). Leave blank to show the figure with no benchmark.
Other approval rules (preview - wired to no server table or gate; collapsed by default)
Other approval rules
Preview - not yet wired to a server table or gate| Rule | Approvers | Threshold / Conditions | Enforced in | Action |
|---|
Rule details
Select a rule to view its approvers and notes.
Administrator access (restricted - Administrator gives access to everything)
Loading...
These settings apply company-wide. They control defaults and service behaviour. Use Access Groups for module access and Special Permissions for approval authority.
Settings marked Save changes stay pending until you save at the top. Other controls save immediately or use their own labelled Save button.
Company and sign-in
Company details and staff authentication.
General settings
Use Save changes to apply company details.
Security defaults
Use Save changes to apply the 2FA requirement.
AI replies
Drafting and automatic replies for the shared inboxes.
AI replies
Switches save immediately.
Missed customer email review
Switch saves immediately.
Loading archive review status...
Review spending limits will appear after status loads.
Sales controls
Credit checks and shipping without payment.
Credit and payment controls
Switches save immediately.
Support and warranty
Close-off routing and expected claim times.
Support workflow default
Use Save changes to apply the close-off assignee.
After an approved RMA refund is executed, HQ assigns the case to this person for final review and closure. This controls workflow routing only; it grants no Support access or approval authority.
Warranty claim step estimates
Use Save estimates below to apply these times.
How many business days each step usually takes to happen after the one before it, shown to customers on safiery.com and in their update emails. Leave both boxes blank to show no estimate for that step. Keep these generous - they read as a promise.
Warranty claim emails to customers
Switches save immediately.
When this is on, a customer gets one short email from support@safiery.com each time their warranty claim reaches a new step, with their case number and a button to see its progress on safiery.com. Only claims created after you switch it on are emailed, so old claims are never sent a pile of emails.
Status: Off
Email the customer when their claim reaches:
RMA issued to you emails when staff generate the RMA Identity Label (not if the return-pack email already went). Product returned is skipped when the replacement ships with its own shipping email. At most one email per claim per day.
Refund authorisers
Who may approve or decline an order refund. Tick people here and only they can authorise a refund - this applies even to admins. With nobody ticked, refunds fall back to today's rule: Finance, and any admin.
Loading...
Changes to this list are recorded in the audit log. This only controls who may authorise a refund - it does not grant admin access or change anyone's role.
RMA decision approvers
After testing is complete, the RMA waits at Pending Decision. Only the people ticked here can approve the assessment and choose refund, credit, replacement, chargeable, not-covered or customer-pickup. This applies even to admins. With nobody ticked, the existing Support Manager/admin fallback stays active. Any later movement of money remains a separate approval, including the Refund authorisers list above.
Loading...
Changes to this list are recorded in the audit log. This only controls who may sign off an assessment and raise a refund or credit - it does not grant admin access or change anyone's role.
Booking return shipping label authorisers
Safiery pays to get a unit returned only by exception. Only the people ticked here can attach or replace a Booking Return Shipping Label on an RMA - this applies even to admins. With nobody ticked, this falls back to today's rule: Support Managers, and any admin.
Loading...
Changes to this list are recorded in the audit log. This only controls who may attach or replace a Booking Return Shipping Label - it does not grant admin access or change anyone's role.
Remote assessment authorisers
Who may record a remote assessment on an RMA - the warranty decision made when no unit came back. Tick people here and only they can record one - this applies even to admins. With nobody ticked, this falls back to today's rule, which for this action is wide: any Support, Warehouse, Sales or Finance role, plus any admin.
Loading...
Changes to this list are recorded in the audit log. This is the list for recording an assessment only. Signing one off is a separate door with its own list - RMA decision approvers, above - because the person who reviews an assessment must not be the person who wrote it. Neither list grants admin access or changes anyone's role.
Tick at least two people, or make sure the people here are not the same single person on the RMA decision approvers list. A remote assessment cannot be signed off by whoever recorded it, so one shared name means nothing can be reviewed and the refund behind it stays blocked.
Internal assessment authorisers
Who may record an internal assessment on an RMA - a unit received at the warehouse and assessed in hand without going onto the bench. Tick people here and only they can record one - this applies even to administrators. It does not let them record a remote assessment. Empty means the Remote assessment authorisers list decides, as before.
Loading...
Changes to this list are recorded in the audit log. This is the list for recording an internal assessment only. A different person still reviews it (RMA decision approvers), unless they are on Review own RMA assessment.
Review own RMA assessment
People ticked here can review an RMA assessment they recorded themselves (remote, internal, or the Section 10 sign-off of their own testing diagnosis) and finish the Decision Outcome themselves, including confirming their own Repaired. Anyone else who tries gets a warning and the Support Managers are asked to review it. Money outcomes still go to Finance. Empty means nobody.
Loading...
Changes to this list are recorded in the audit log. This list does not grant admin access or change anyone's role, and it never bypasses Finance executing a money outcome.
RMA override and close
Who may press Override and close on an RMA - closing it while its Ready to Close steps are not all complete. Tick people here and only they can do it - this applies even to admins. With nobody ticked, only Support Managers and admins can.
Loading...
Changes to this list are recorded in the audit log. An override still needs a written reason, and it can never close an RMA while a refund, credit or other money outcome is still waiting on Finance. This list does not grant admin access or change anyone's role.
Customer emails
Order confirmation, payment, shipping and warranty progress emails, including staff copies.
Order emails to customers
Switches save immediately. Each copy list has its own Save copies button.
Three automatic emails, all in the Safiery design. Each switch saves as soon as you click it.
What it sends: "Thanks for your order" with each product and its picture, the totals and the tax invoice. When: as soon as someone orders on safiery.com. If they paid by card, this one email also says the payment was received. Only orders placed after you switch it on.
Status: Off
Copies go to: jean.cobine@safiery.com
What it sends: "Payment received - thank you" with the current invoice. Full payment gets one receipt per order and turns Email receipt to customer green. Verified part payments get a receipt showing that payment, total paid and balance remaining; they do not mark the invoice fully paid or promise dispatch. Each payment receipt is deduplicated, including an unchanged payment removed and added again in Xero. Part-payment coverage starts on the first enabled run; earlier payment days are not replayed. Every automatic send is listed in Activity as Quasar AI. Jean is always copied.
Status: Off
Copies go to: service@safiery.com, jean.cobine@safiery.com
What it sends: "Your order is on its way" with the products, the carrier, the tracking number and a Track your parcel button, from the person who booked it. When: a parcel is booked with Shippit or Easyship. This email already went out before this switch existed, so it starts on. Off stops it completely, including the warehouse inbox copy when a customer has no email.
Status: On
Copies go to: jean.cobine@safiery.com
Emails 1 and 2 come from sales@safiery.com, which must stay connected in HQ. HQ checks for new orders and payments every 5 minutes.
Copy to: Safiery addresses only (name@safiery.com), up to 5, separated by commas. Jean (jean.cobine@safiery.com) is always copied on customer order emails. Clear the box to remove optional copies only. Payment received also copies Donovan (service@safiery.com) by default.
Warehouse packaging
Measured boxes and satchels used for shipping.
Packaging boxes
Each box is saved from its Add or Edit form.
The cartons and satchels the warehouse actually stocks, with measured internal size, outer size, empty weight and cost. Combined shipping needs a complete measured carton and a stated maximum gross weight.
| Code | Name | Internal size (mm) | Outer size (mm) | Empty weight | Max gross weight | Cost | Status | |
|---|---|---|---|---|---|---|---|---|
| Loading... | ||||||||
Whether a box's cost is ever charged to the customer is a separate pricing decision, not made here - this catalogue only records what a box costs us.
Staff communications
Bell and email notifications, plus weekly and monthly updates.
Notifications
Email notifications save immediately. In-app preferences and the alert recipient need Save changes. Email design has its own Save button.
This person gets the red-bell alert for every new trade account request. With Email notifications on, the same alert is emailed by the existing scheduled mirror. If the selected account becomes unavailable, Sales and then management remain the fallback.
Design company-wide notification email (subject, wording and colour)
This subject, wording and colour are shared by every notification email across the company.
Keep {{headline}} in the subject so every inbox shows which alert arrived.
Enter a six-digit hex colour, for example #2f7fc4.
Merge fields can be used in the subject, brand, header, intro, button or footer. The live alert headline, record title, details and link always remain in the email.
Available merge fields: {{headline}}, {{title}}, {{body}}, {{actor_name}}, {{company_name}}, {{link}}, {{notification_kind}}.
This company-wide design saves separately from both the on/off switch and the page's Save changes button. Send test to me always uses the last saved design.
[Quasar HQ] Sameera Jeffrey mentioned you
Sameera Jeffrey mentioned you
Open in Quasar HQ
In-app notifications are always on - the bell cannot currently be switched off, so this toggle records a preference only.
Weekly updates
Switches, people and the budget save immediately.
Monday-morning email summaries about Quasar itself - security, ISO 9001 readiness and AI usage, with links back into the record - separate from the customer and team notification mirror above.
What needs your attention this week - security, ISO 9001 records progress and AI usage - sent every Monday at about 6am. Nobody gets one until this is switched on and at least one person is picked below.
Orders, quotes, money to chase, website and distribution from last week - sent every Monday at about 6am.
Support cases, RMAs, field service, production, stock and shipping from last week - sent every Monday at about 6am.
A personal list for each person picked below: what is waiting on them, their jobs, cases, quotes and accounts - sent every Monday at about 6am, only to people with something to act on. Nobody gets one until this is switched on and at least one person is picked below.
Sent at 6pm on the last day of each month, with a PDF. Only people who can open Reports > Hours & Targets receive it (administrators, Finance, Operations Manager).
Shown as a guideline figure in the Admin update - Quasar does not record the cost of an individual AI call yet, so this is not a hard cap. Leave blank for no budget.
Project timer reminder
The switch, time and people save immediately.
Each listed person gets one bell and one email on each of their work days if, by the time below, they have not started a project timer or logged project time that day. Nobody on approved leave or on a public holiday is reminded, and nobody is reminded twice in a day.
Status: Off
People to remind (up to 30)
People who get a copy (up to 5)
Anyone picked for a copy receives one bell and email a day listing who was reminded. Nobody is reminded until the switch is on and at least one person is picked.
Records and backups
Reference numbering, settings history and database information.
Monitoring & records
Reference numbers are assigned automatically and cannot be changed here. RMA numbers are continuous and never reused.
Data & backups
Database backups are managed by Netlify and Neon. This page does not create a backup.
Manage automatic replies and outgoing emails. Staff use the Quasar AI icon in the top bar for everyday chat. Company-wide setting changes retain their existing administrator permissions.
Quasar AI jobs
Use the switch on the right of each job to turn it Off or On in Suggest mode. Confirm each change below. Jobs keep their permissions, source checks and review requirements. Open Agents to edit guidance, choose models or review history.
Open the Quasar AI tab to load current job status.
RMA close summaries currently add an internal note to the linked Support case after return dispatch, when their job and the site's agent switch allow it. The AI summary does not currently add a note to RMA activity.
Outgoing emails and replies
Manage each email workflow here. Each control states when it saves and who receives the message.
The switches below control their named automatic emails. Staff-triggered emails, account security messages and deployment-controlled services keep their existing sending rules.
Connections and model choices
Use the existing integration controls to review provider and mailbox configuration. Keys stay on the server. A configured key does not prove a working connection.
Usage and limits
Each agent's Testing tab shows its supported test limits and recorded usage. Existing runtime limits still apply. The monthly budget in Weekly updates is a reporting guideline, not a company-wide spending cap.
Who can manage Quasar AI
Use Access Groups to hide the Chat, Agents, AI Conversation Chat, Brain or AI Settings menu entries. Staff can keep using the top-bar Chat under its existing permissions.
Menu visibility does not grant access to records, Finance, Sales, private projects or source documents. Every read and action still checks the person's current permissions. Automation switches require an authorised person using their own account.
Connected below means a key is present in the site env - a presence check, not a live health check. For the carriers, a second pill says whether bookings are actually live: a carrier can be Connected and still return a dry-run preview, or book against the vendor's staging account, in which case a click on Book shipment produces a tracking number but no parcel is ever collected. RingCentral gets the same second pill for its call sync (Syncing calls or Sync off), and its card also shows the last call saved and any recent sync problem. Use Test connection on a card to confirm it can actually reach that provider right now; Inbound health further down checks something no single integration's key can - whether a customer message is actually arriving at all.
Inbound health
admin-onlyA Connected pill above only proves a key is set - not that any customer message is actually arriving. That gap is exactly what stayed invisible for 13 days while the Intercom webhook silently 401'd on every delivery. This reads the one watermark every inbound path bumps and warns when it has gone quiet.
Shared mailboxes
Gmail sends as the mailbox that authorised it, so a company address such as sales@safiery.com can only be chosen as the From address on a document once that mailbox itself is connected here. An alias is not enough. Connecting one never affects your own personal Gmail connection.
| Mailbox | Status | Connected by | Last updated | |
|---|---|---|---|---|
| Loading... | ||||
Google Chat sync
Checking...Each person links their own Google account from Team Chat - private messages only sync for people who have linked their own account, and nobody's messages are read without their consent. Restricted rooms never sync to Google Chat.
Loading...
Customer comms rail
app_settings 'comms.*' - admin-only, auditedWhere a customer conversation travels while Safiery moves off Intercom. Turning a half off here never deletes anything: the imported Intercom history lives in HQ's own tables and stays exactly where it is.
Off means a reply leaves through Gmail instead, from the mailbox chosen on the case. This half is safe to switch off today.
CONVERSATION_INBOXES - by default sales@ and support@ only. A mailbox can be Connected above and still not be polled: connecting it stores a token, the env var decides what the ingest reads. Any address a customer writes to that is not on that list now goes uncollected. The last run's Mailboxes polled count in Shared mailbox ingest below tells you how many are actually being read.Shared mailbox ingest
admin-only, auditedPolls the connected company mailboxes (sales@ and support@) for new customer email, and turns a genuinely new enquiry into an unassigned request in the Inbox. Runs automatically every 5 minutes; this button runs it once, now. Safe to re-run - a message already pulled in is matched and skipped, never duplicated.
Email signatures
app_settings 'signature.company_html' - admin-only, auditedOne signature for every outgoing email, personal or from a shared mailbox like sales@ - built once here and reused everywhere. Each person's own name and role fill in automatically from their People record, so nobody edits their own signature and a job title is corrected in exactly one place.
Press Use the standard block for the house signature, or paste your own straight out of Gmail's signature editor - there is no HTML to type by hand either way. Use the Bold and Link buttons above the editor for that formatting; only http, https and email addresses are allowed in a link, the same rule the Email Templates editor uses.
Each person's own details fill in automatically from the staff directory on the People page: {{USER_NAME}}, {{USER_ROLE}}, {{USER_PHONE}} and {{USER_EMAIL}}. So nobody builds a signature of their own, and a job title is only ever corrected in one place. Anything with nothing to fill in disappears cleanly. A reply sent from a shared mailbox like sales@ shows the name and role of whoever is actually signed in and sending it - the same as any other email.
Add {{USER_NOTE}} anywhere you want a person's own note to appear underneath their name and role - e.g. Jean's rostered work days. It fills from the "Signature note" field on that person's Directory profile (People page), and always renders smaller and in light grey since it is a note, not a signature line - you do not need to style it yourself. Leave it blank for someone and their line disappears cleanly; today that is everyone except Jean.
Use {{signature}} instead if you would rather each person paste their own block and this template only wrap it.
Text beats a logo here. Outlook and most company mail systems block images by default, so a logo shows for some recipients and leaves a hole for the rest - the standard block uses the word SAFIERY set bold instead, which nothing can block. If you do add a logo it must be PNG; SVG is refused.
SKU convention
app_settings 'sku.*' - admin-only, auditedOwn (Safiery-made) products get a dotted code, checked as it is entered on Inventory's + New item; resale products keep the supplier SKU untouched. A format issue prompts the person entering it and they can still consciously save (flag, don't block); a duplicate SKU is always refused outright. Existing codes are never re-checked or regenerated.
Shipping email templates
app_settings 'shipping.*' - admin-only, audited{{first_name}}, {{order_number}}, {{items}}, {{ship_to}} and {{tracking}} are filled in from the real order - never an invented promise or a guessed ETA. Each box shows the built-in template until you save your own; clear a box and Save to go back to the built-in text.
AI providers
Assistants work only when the system-level keys are configured. Provider keys are held server-side, never in the browser.
Data access
Admin sets the policy here; each staff member connects their own AI account under their own profile. WooCommerce is retired per CLAUDE.md v2.0 (Xero is the order-of-record); the Woo card is reference-only.
Historical import and contact maintenance
Intercom import
admin-only, auditedPulls every Intercom conversation - including internal notes - into HQ's own tables, so the history is here before Intercom is switched off. Preview first: nothing is written until you apply. Safe to re-run - an already-imported conversation is matched and skipped, never duplicated.
version on every request it touches. Run it when nobody else is editing the inbox.Contact name backfill
admin-only, auditedSome contacts have their name stuck as their own email address, even though a real name later arrived via billing or shipping details. Preview first: nothing is written until you apply. Safe to re-run - a contact renamed by a person since the preview is left alone.
Audit log
| When | User | Action | Module / Record | Detail |
|---|---|---|---|---|
| Loading... | ||||
Deleted records
Loading...
Warranty fault categories
app_settings 'support.fault_categories' - admin-only, auditedLoading...
The controlled dropdown a no-return RMA's remote assessment picks a fault category from (Support > RMA > Remote assessment), and the list a monthly warranty report will group by. Retiring a category removes it from the pick-list for NEW assessments only - an assessment that already recorded it keeps working unchanged. The key is generated from the label and cannot be changed once saved.
Commissioning guides (edit voltages, cable tables and steps used in Field Service commissioning; device Wi-Fi/Bluetooth passwords)
Commissioning guides
app_settings 'fs.commission_guides' - admin-only, auditedEvery reference guide a technician sees inside a Field Service commissioning part. Edit a guide to change its voltages, cable tables or steps for every job that uses it from now on. "Back to built-in" on the edit sheet undoes just that one guide.
| Guide | |
|---|---|
| Loading... | |
Device passwords
app_settings 'fs.device_passwords' - Field Service staff view, admin save, auditedOnly Field Service staff and admins can see these in Field Service. Every view is recorded.
| Device | Password | Note | |
|---|---|---|---|
| Loading... | |||
Website chatbot status
Review queue
Show all recentKnowledge
Add or replace document knowledge
Each document is converted to plain text on the server and split into knowledge entries by heading, added to the curated list above. The original file is never stored, and re-ingesting a document with the same title disables its previous entries first.
Chatbot settings and knowledge sources
Chatbot settings
The bot answers ONLY from the knowledge sources below. The env switch and API key are server-side facts (read-only here); flipping the toggle alone cannot enable the bot.
Knowledge sources
Source toggles are saved with Save settings. The curated knowledge list above is always on.
Link reference documents into chatbot knowledge
Reference library
RefreshThe library of manuals, datasheets, wiring guides and certificates is created and tagged on the Reference Docs page. Link one below to let the bot read its full text - split into entries above, exactly like an upload - instead of only citing its title and link.
Unlink disables that document's entries; re-link to pull in a newer version.
Test a website answer
Test console
Test questions run the REAL engine (logged as mode "test", capped 30/hr per user) but skip the public visitor cap. Works before the public kill switch is on.
Website embed instructions
Embed on the website
Optional attributes: data-accent takes your brand colour; data-title renames the launcher. The widget fails to a friendly offline note whenever the bot is disabled.
One server prerequisite: the website's origin (e.g. https://safiery.com) must be listed in the CORS_ALLOW_ORIGIN environment variable on this site, or the browser will block the widget's calls. Ask whoever manages the Netlify environment before embedding.
Email templates
email_templates - support_manager/admin, auditedReusable subject/body pairs used when Support and RMA screens send mail (e.g. the "matching order not found" reply on an RMA request). Placeholders like {{first_name}} are substituted at send-time - keep the key stable once a screen refers to it.
These are your own templates - this table is owner-scoped server-side, so a template a colleague created does not appear here (and vice versa). Before adding a key a screen already refers to, check with whoever set it up: a screen that sends by key finds a template owned by anyone, so a duplicate key means two rival rows, of which only the most recently edited one is used.
| Loading... |
Office kiosk location
Lock mobile and desktop clock-in and clock-out near the office to the site kiosk for WHS. TAFE and WFH attendance require this location to be saved and enabled. Location is captured when staff start and finish; there is no background tracking.
Safiery: 45/8 Distribution Court, Arundel QLD 4214. Check the site address on Google Maps. Use this device location only while at this site. Review the accuracy and coordinates before saving.
Load the current setting before editing.
On site now
Staff on site, plus visitors and contractors signed in and not yet signed out| Name | Kind | Company / role | Host | Signed in | Status |
|---|---|---|---|---|---|
| Loading... | |||||
Visitor and contractor record
| Name | Kind | Company | Host | Signed in | Signed out | Induction acknowledged | Signature |
|---|---|---|---|---|---|---|---|
| Loading... | |||||||
Paired tablets
| Tablet | Paired by | Paired | Last activity | State | Action |
|---|---|---|---|---|---|
| Loading... | |||||
Automatic sign-in phones
Signs a person in when their phone arrives at the office and out when it leaves| Person | Phone | Set up | Last activity | Expires | State | Action |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Contact site admin
Where a tablet's "Contact site admin" report is emailedSite reports go to adamd@safiery.com unless an administrator saves a different recipient here. Reports use the Quasar HQ notification email service.
Manager sign-out
Whether a manager can sign staff out of the site clockON when never set - matches the Operations board's existing Sign out. Untick to block manager sign-outs everywhere (People and Operations). Stored in app_settings under kiosk.manager_signout_enabled, admin-only server-side.
WHS and Emergency induction
Shown on the tablet to every visitor and contractor before they can sign inThe wording and the version are one record: this editor only ever writes them together, so the text can never change under acknowledgements already recorded against a version. Stored in app_settings under kiosk.whs_induction, which is admin-only server-side (the kiosk. prefix lock in the db function) - a hidden button is not the control.
Work type vocabulary
Read-only hereLoading...