Settings, Support & Activity
This guide covers the three account-area screens in QELM: Settings (your company profile, branding, crew onboarding, and preferences), Support (submitting and tracking requests to our team), and Activity (a read-only record of what happened in your workspace). Settings is the substantial one and is covered first; Support and Activity follow.
Settings
Section titled “Settings”The Settings screen is where you manage your company profile and the defaults that apply across your workspace. It is organized into grouped section cards, and a sticky Save bar stays at the bottom of the screen so you can save from anywhere in the form. Choose Save Settings to apply your changes; the screen confirms when they are saved, and tells you if a field needs fixing.
Only your own workspace’s settings are shown. Viewing them is open to Managers and Admins; saving them is Admin-only by default — a Manager who needs to change settings has to be granted that permission individually on the permissions matrix (see People & Access). The change is checked on the server, which is the final authority, so a Manager without the permission cannot save even if the form is on screen.
Company
Section titled “Company”The Company card holds your business name and contact details — name, email, phone, address, and website. These appear on customer-facing documents such as invoices and estimates, so keep them current. The company name is required.
Branding & Proposals
Section titled “Branding & Proposals”The Branding & Proposals card sets the defaults applied to estimates and proposals: the invoice prefix (the short code prepended to invoice numbers), a license / certification footer, and your default proposal terms. Setting these once means every new estimate starts from your standard language.
Crew Onboarding
Section titled “Crew Onboarding”The Crew Onboarding card lets you generate a self-onboarding link to share with a new crew member. Choose Generate Onboarding Link, then Copy to put it on your clipboard and send it however you like. The person opens the link and fills in their own details to get started — no account is needed to begin. The onboarding page itself is a public, link-based page (it is not part of the signed-in app); this screen simply produces and copies the link.
Preferences
Section titled “Preferences”The Preferences card holds workspace defaults applied across jobs and invoices — the default tax rate, the default labor rate, and the notification CC emails that receive copies of system notifications. These are starting points; individual jobs and invoices can still override them.
Notifications
Section titled “Notifications”Your own notification preferences live at Settings → Notifications — that is where each person chooses what they get told about and whether it reaches their phone. They are per-user, not per-workspace: changing yours does not change anyone else’s.
What stays on the classic screen
Section titled “What stays on the classic screen”A couple of Settings capabilities remain on the classic screen for now: uploading your company logo and connecting a Stripe payout account. The redesigned Settings screen covers everything else; those two will move over in a later update.
Support
Section titled “Support”The Support screen has two halves: a submit form and your ticket history. To open a request, enter a subject, choose a priority (Low, Normal, High, or Critical), describe the issue in the message, and choose Submit Request. A confirmation appears when it is received, and we follow up by email. Your previous requests are listed under Ticket History with their status, so you always know where each one stands. The list shows only your own workspace’s tickets.
Activity
Section titled “Activity”The Activity screen is a read-only record of what happened in your workspace — who did what, and when. It does not change anything; opening it never alters your data. Each row is icon-coded by the kind of action and shows the person, a short description, and a timestamp.
Three controls help you find an event:
- Type pills — choose a type to focus the feed on one kind of action; All clears the type filter.
- Date range — set a From and To date to bound the feed.
- Search — type a few words to match the event descriptions.
Because the feed is read-only, the filters only change what you see — they never record anything.
What gets recorded
Section titled “What gets recorded”Every recorded event carries a type code in the form area.action. The Type pills
filter on these, and the codes are what you will see if you export or search the feed.
Grouped by area, this is what QELM records:
Signing in and accounts
Section titled “Signing in and accounts”| Event type | What it means |
|---|---|
auth.login, auth.spa_login | Someone signed in from a browser |
auth.logout | Someone signed out |
auth.mobile_login, auth.mobile_logout | A sign-in or sign-out from the mobile app |
auth.mobile_magic_request, auth.mobile_magic_login | A sign-in-link was requested, and used |
auth.mobile_login_rotate | The mobile app renewed its session |
auth.reset | A password was reset through the reset link |
auth.verify | An email address was verified |
auth.create-workspace | The workspace itself was created |
user.created, user.updated | A user account was added or edited |
user.role_changed | Someone’s role changed |
user.permissions_updated | An individual permission was granted or revoked |
user.password_reset | An Admin reset a user’s password |
Jobs, dispatch, and change orders
Section titled “Jobs, dispatch, and change orders”| Event type | What it means |
|---|---|
job.created, job.updated | A job was added or edited |
job.archived, job.restored | A job was archived, or brought back |
job.merged | Jobs were merged together |
job.blueprint_uploaded, job.blueprint_archived, job.blueprint_viewed | A blueprint was added, archived, or opened |
dispatch.assignment_created, dispatch.assignment_removed | Crew was scheduled onto a day, or taken off it |
change_order.created, change_order.approved | A change order was raised, and approved |
Estimates, invoices, and payments
Section titled “Estimates, invoices, and payments”| Event type | What it means |
|---|---|
estimate.created, estimate.updated | An estimate was written or edited |
estimate.sent | An estimate was sent to the customer |
estimate.converted | An estimate became a job or an invoice |
estimate.pdf_downloaded | The estimate PDF was downloaded |
estimate.archived, estimate.restored | An estimate was archived, or brought back |
invoice.created, invoice.updated | An invoice was raised or edited |
invoice.job_created | A job was created from an invoice |
invoice.sent_for_signature | An invoice went out for signature |
invoice.archived, invoice.restored | An invoice was archived, or brought back |
invoice.attachment_uploaded, invoice.attachment_replaced, invoice.attachment_deleted, invoice.attachment_viewed | The invoice’s backup file was added, swapped, removed, or opened |
payment.created, payment.deleted | A payment was recorded, or removed |
payment.attachment_viewed | A payment’s attachment was opened |
Job costs and income
Section titled “Job costs and income”| Event type | What it means |
|---|---|
expense.created, expense.updated | An expense was recorded or edited |
expense.archived, expense.restored | An expense was archived, or brought back |
expense.receipt_uploaded, expense.receipt_replaced, expense.receipt_removed, expense.receipt_viewed | A receipt was attached, swapped, removed, or opened |
income.created, income.archived, income.restored | Income against a job was recorded, archived, or brought back |
| Event type | What it means |
|---|---|
time.admin_clocked_in | A supervisor started a shift on someone’s behalf |
time.admin_edited, time.admin_edited_open, time.admin_deleted | An entry was edited or deleted by an approver |
time.edit_requested | An employee asked for a correction |
time.edit_approved, time.edit_rejected | That request was approved, or turned down |
time.week_approved, time.week_reopened | A week was locked for payroll, or reopened |
time.open_entry_resolved | A shift left running was closed out |
Employees and crew onboarding
Section titled “Employees and crew onboarding”| Event type | What it means |
|---|---|
employee.created, employee.updated | An employee record was added or edited |
employee.archived, employee.restored | An employee record was archived, or brought back |
crew_join.enabled, crew_join.disabled | Self-onboarding was switched on or off |
crew_join.rotated | The onboarding link was regenerated |
crew_join.require_approval_changed | The approval requirement for joiners changed |
crew_join.approved, crew_join.declined | Someone who used the link was let in, or turned away |
Inventory and fleet
Section titled “Inventory and fleet”| Event type | What it means |
|---|---|
inventory.item_created, inventory.item_updated | A stock item was added or edited |
inventory.items_archived, inventory.items_restored | Items were archived, or brought back |
inventory.quantity_adjusted | A stock quantity was changed |
inventory.category_created | A category was added |
fleet.vehicle_created, fleet.vehicle_updated | A vehicle was added or edited |
fleet.vehicle_archived, fleet.vehicle_restored | A vehicle was archived, or brought back |
fleet.vehicle_assignment_updated | A vehicle was assigned to someone else |
fleet.entry_created, fleet.entry_updated, fleet.entry_archived, fleet.entry_restored | A fuel or maintenance entry was recorded, edited, archived, or brought back |
fleet.document_created, fleet.document_archived, fleet.document_restored | A vehicle document was added, archived, or brought back |
fleet.reminder_completed | A maintenance reminder was marked done |
Settings, Stripe, and support
Section titled “Settings, Stripe, and support”| Event type | What it means |
|---|---|
settings.updated | Workspace settings were saved |
settings.logo_updated | The company logo was changed |
settings.stripe_connect_started, settings.stripe_connect_completed, settings.stripe_connect_disconnected | Stripe onboarding was begun, finished, or the account was disconnected |
support.ticket.created, support.ticket.updated | A support request was opened, or moved on |
QELM support access
Section titled “QELM support access”| Event type | What it means |
|---|---|
auth.impersonation.start, auth.impersonation.stop | QELM support opened, and closed, a session in your workspace to help with something |
Finding who changed an invoice
Section titled “Finding who changed an invoice”The filters combine, so a specific question is three steps:
- Narrow the type. Choose the invoice type pill so the feed shows only invoice events and drops everything else.
- Bound the dates. Set From and To around when you think the change happened — the day you noticed it, and a few days before.
- Search for the invoice. Type the invoice number in the Search box. What is left is every recorded change to that invoice in that window, each row naming the person and the time.
If nothing comes back, widen the date range first — the change is more often older than expected than missing.
For how the rest of QELM fits together, see the Guides overview.