Users and Access

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.

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.

One production line per line, in any order. Shown on the Line View wall, each line's own tablet, and the scheduling line picker. Leave blank to keep deriving names from recent orders.

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.

A 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.

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.

Where 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.

Pulls 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.

Some 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.

Polls 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.

One 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.

Own (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.

{{order_number}}, {{items}}, {{ship_to}} and {{tracking}} are substituted from the real order - never an invented promise or a guessed ETA. Leave a template blank to use the built-in default text.

Loading...

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.

The 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 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.

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.

Reusable 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.

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.

Site reports go to adamd@safiery.com unless an administrator saves a different recipient here. Reports use the Quasar HQ notification email service.

ON 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.

The 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.

Loading...