Docs/Workspace Setup

Engineers and Team

Engineers and team setup covers inviting the office and engineer users who schedule, capture, review and deliver work.

For: Owners and office admins3 min read5 sections

Team Functions

  • Invite office users and engineers and assign the right role.
  • Track engineer active status, which controls whether they can be assigned checks.
  • Switch on sole-trader mode to hide team prompts and auto-assign checks to the owner.
  • Manage member roles and remove access when someone leaves.

Engineer Readiness

  • Engineers need their own account to keep signatures and record generation attributable.
  • An engineer must be active to appear as assignable in scheduling.
  • Engineers should confirm mobile sign-in and camera permission before their first field day.

Troubleshooting

  • Engineer not assignable: confirm the profile is active and has the engineer role.
  • Invite not received: check the email address and spam folder, then resend.
  • Cannot change a member: confirm the acting user has team management permission.

The Team Page

Team, in the sidebar, is the working list of your people. Settings holds the invitation and role controls; the Team page is where you browse, search, and maintain the members themselves. The two work together rather than competing.

  • See every member with their role, email, phone, and active status, with search, filters, and sorting.
  • Open a member to view or edit their details, or add a new engineer directly from the Team page.
  • Import engineers in bulk with the CSV importer when onboarding a bigger team.
  • Use bulk actions to deactivate several members at once, for example after a seasonal crew finishes.

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?