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 admins4 min read6 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 and VAT number. Each engineer adds their own Gas Safe registration number under Profile; it prints against their name on every record they generate.
  • 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 business identity (or the engineer’s Gas Safe number on their profile); records generated from then on pick it up.
  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 (London leads the list; set it once, the default is UTC), and the workspace logo.
  • Set the business identity that prints in the certificate footer: business name, address, phone, email and VAT details. Each engineer enters their own Gas Safe registration number on their Profile tab; it is stamped on every record they generate.
  • Configure notification preferences and renewal reminder behaviour on the Notifications tab (Growth and above).
  • Toggle sole-trader mode and readiness quick edits under Workspace defaults. Sole-trader mode assigns new checks to you and hides the Team tab.
  • Brand outgoing email: sender identity, an email logo, and your own template copy where you want it.
  • Set invoice payment details (bank account and payment terms), pricing norms for quote warnings, and CIS deductions.
  • Connect integrations: Google Calendar for conflict protection, Stripe for card payments, and an accounting platform where configured.
  • Personal preferences live on the Appearance tab: each user picks their own console theme (Dark or Light), density (Comfortable or Compact) and a Reduce motion switch, and they follow them across devices.

Accounting Sync

  • Connect Xero, QuickBooks Online or Sage under Integrations (Growth and above). Manifold pushes your customers and draft quotes into your accounts package; invoices and payments do not sync yet.
  • Sync runs in the background. Sync now retries anything that did not go through, and the panel shows the synced and failed counts and when it last ran.
  • A provider only appears once the Manifold deployment has its credentials configured; if you cannot see one, ask support.

The Settings Tabs

Settings is split into tabs, and every card saves on its own button, so a change in one card never waits on another.

  • Profile, Appearance, Notifications, Organisation, Branding, Team, Billing & plan, Integrations, AI & automation, API & webhooks, and Audit log.
  • Organisation also holds the no-show threshold, the check-in distance and the default on my way ETA that drive the check-in alerts.
  • Branding sets the from name, reply-to address and per-template subject and body overrides for outgoing email; the email logo is the organisation logo.
  • Integrations holds Google Calendar, Stripe and accounting; API keys, webhooks and the Power BI connector (Growth and above) sit under API & webhooks.
  • Office users can open Settings but cannot edit the Organisation, Team or API sections; those need the owner role.

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 Business identity under Settings, then Organisation. A wrong Gas Safe number is fixed on that engineer’s Profile tab. Future records pick up the change.
  • Logo does not update: use a PNG, JPEG or WebP under 2 MB, then refresh the page.
  • 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 so every record generated from now on prints it correctly.
  • 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?