Docs/Workspace Setup

Organisation and Gas Safe Identity

Organisation and Gas Safe identity settings hold the details and certificate identity that print on every record.

For: Owners and office admins3 min read4 sections
Settings exampleCustomer-safe walkthrough

Get the certificate identity right before real records

The certificate identity block prints on every record. Settings is where you lock organisation details, Gas Safe identity, notifications, and sole-trader mode.

What you see

  • Organisation name, timezone, and branding.
  • Certificate identity: business name, address, phone, email, Gas Safe and VAT numbers.
  • Notification preferences and the sole-trader toggle.

How to use it

  • Confirm certificate identity before generating real records.
  • Set the timezone so scheduled dates read correctly.
  • Enable renewal reminders and confirm recipients.
  • Turn on sole-trader mode if you work alone.

Organisation settings

Plan

Team

Seats used

4/10

Certificate identity

Mercer Gas Ltd - Gas Safe 512347

Renewal remindersOn
Tenant deliveryOn
Sole-trader modeOff
Client portalEnabled

Decision guide

SituationRecommended actionProof it worked
First real recordVerify every certificate identity field.A generated record shows the correct details.
Working soloEnable sole-trader mode.Checks auto-assign to you.
Reminders not firingConfirm reminders are on and recipients exist.A due-soon property triggers a reminder.

Troubleshooting path

  1. 1If a record shows wrong business details, fix the identity and regenerate future records.
  2. 2If the logo will not update, check file type and size and refresh.
  3. 3If dates look wrong, confirm the organisation timezone.

Settings Functions

  • Set organisation name, timezone (Europe/London by default), and branding.
  • Set the certificate identity: business name, address, phone, email, Gas Safe number, and VAT number.
  • Configure notification preferences and renewal reminder behaviour.
  • Toggle sole-trader mode and manage onboarding walkthrough state.
  • Brand outgoing email: sender identity, an email logo, and your own template copy where you want it.
  • Maintain the van stock list that engineers pick parts from during checks.
  • Connect integrations: Google Calendar for conflict protection, Stripe for card payments, and an accounting platform where configured.
  • Personal preferences live here too: each user picks their own console theme (light or dark) and density, and it follows them across devices.

Why Identity Matters

The certificate identity block is printed onto every gas safety record using a fixed document palette. If it is wrong, records are wrong. Confirm it before generating real records.

Troubleshooting

  • Record shows the wrong business details: update the certificate identity in Settings and regenerate future records.
  • Logo does not update: check file type and size and refresh cached browser assets.
  • Timezone-dependent dates look wrong: confirm the organisation timezone and the check dates.

Data Quality Standard

Setup records are not just admin. They become the labels, filters, and certificate fields customers rely on later. A small naming or address mistake in setup becomes a compliance or delivery problem weeks later.

  • Use one canonical spelling for every client, property, and appliance.
  • Keep property addresses precise, because they drive the route planner, scheduling, and the printed record.
  • Keep appliance make, model, serial, and GC number accurate so PlateScan deduplicates cleanly.
  • Deactivate former engineers and historical records instead of deleting history that explains past work.
  • Run bulk imports in dependency order: clients, then properties, then appliances.

Customer-Facing Consequences

If a value can appear on a record, in the portal, or in an export, write it as if a landlord or letting agent will read it. Manifold reuses operational labels across customer outputs, so there is no separate translation step at delivery time.

Troubleshooting

  • If a client sees a confusing name, fix the source record and regenerate future records.
  • If analytics split across duplicate names, choose one canonical record going forward and keep the old ones for history.
  • If an export does not join downstream, check names, identifiers, and relationships in setup before changing the export.

Was this page useful?