2. Prepare your organisation

Organisation settings

Organisation settings are the foundation of your account — your details, how dates and numbers are displayed, your branding, and your integration and security options. It's the first place to visit after signing up, and it's worth keeping complete and current. Configure it whether or not you integrate with an external CMMS.

Last updated: September 2026

Who can do this: owners and admins. Where: Home → Administration → Organisation Settings.

Open organisation settings

From the sidebar, go to Administration → Organisation Settings. Settings are grouped into General, Integrations, and Security.

The Organisation Settings page, open on the General tab, showing the Details and Content languages sections

General tab

The General tab holds your organisation's core information and display preferences.

Details

Core contact information for your organisation. Select Edit to change:

Organisation name — required.
Phone number — optional.
Website — optional. It must start with http:// or https://.

Keep these accurate — the organisation name appears on inspection PDFs alongside your logo.

The remaining fields on this panel are shown for reference and cannot be edited here:

Organisation email is the address of the person who created the organisation.
Legal & security notifications email currently shows that same address.
Last updated by records who last saved the panel.

Note: To change the address shown in Organisation email, contact support. There is no field for it in the app.

Content languages

English is always the source language for your content. Enable additional languages to reveal translation fields when you edit asset types, templates, response types, and other organisation data. Select the languages your operation needs and Save. Throughout the app, Translate buttons then let you provide translations for those languages.

The Content languages section, with English as the required source language and checkboxes to enable Spanish, German, French, Dutch, and Portuguese

Sites and locations

An organisation-wide switch for location hierarchy. When it's on, each site can define its own location tree (which sites use hierarchy, the node names, and the depth) in Sites admin. A defined hierarchy makes it simpler to build inspection routes and rounds. Structure and time zone are configured per site — see Set up sites.

The Sites & locations section, with a toggle to enable location hierarchy for the organisation

Inspection rounds

Route-based inspection rounds give field teams an ordered set of asset stops to inspect several assets in sequence. Routes can be assigned to groups and put on schedules, with a claim-to-conduct workflow. Rounds require a Professional license — check your plan under Billing. On a lower plan this section is not shown at all, rather than shown as locked.

The Inspection rounds section, with a toggle to enable the inspection rounds module

Formats

Your organisation's display settings for language, date format, time format, and time zone. Once saved, they apply across the organisation and follow the account on every device.

Work management mode

Choose how work created from inspections is handled:

Full work management — a task is created per issue; assignees provide root cause and resolution on completion; full analytics including root-cause and resolution trends.
CMMS integration — work orders and requests are pushed to your external CMMS; no tasks are held in LambdaAssetCheck; analytics show issue detection only.

Work management mode is usually confirmed during onboarding. If it hasn't been confirmed yet, the organisation owner can still choose Full work management or CMMS integration here and select Confirm work management mode. After confirmation, the setting is permanent and can't be changed from this screen. Other admins can see the current mode but can't confirm it.

The Work Management Mode section, showing the Full Work Management and CMMS Integration options

Priority-based due dates

Set the default number of days from creation to due date for each priority, between 1 and 365 days. Select Edit Due Date next to a priority to change it. This applies to tasks and incidents; if you integrate with a CMMS, the CMMS determines these instead.

The Priority-based due dates table, mapping Low, Medium, High, and Critical priorities to default due dates

Custom branding

Upload your company logo to personalize your reports and the in-product experience. Select Upload logo and choose a PNG, JPG, or SVG up to 4 MB — a square or landscape image works well. Once a logo is set, use Replace logo to swap it or Remove to clear it. Your logo appears on reports and dashboards.

Uploading a company logo in the Custom branding section — the empty Brand logo panel, then the uploaded logo with Replace logo and Remove options

Organisation ID

A system-generated reference used for integrations and support requests. It's set during onboarding and can't be changed.

Notification defaults

Set organisation-wide defaults for push and email notifications. Events are grouped by area — Tasks, Work requests, and more — and each event has its own Push and Email toggle. Select Edit to change them. These defaults apply to everyone in the organisation, and individual users can override them in their own Preferences (from the account menu).

The Notification defaults screen, with events grouped by area and a Push and Email toggle for each event such as Task assigned, Task completed, and Tasks overdue

Integrations tab

Manage API credentials for connecting LambdaAssetCheck to your other systems. Select Create credential, give it a name that identifies where it will be used, and confirm — the credential is generated and added to the table.

Each credential lists its Name, Client ID, when it was Created, when it was Last used, and its Status, with an action to copy the client ID. Treat client IDs and secrets as sensitive: store them securely and never commit them or share them publicly. See the developer documentation for how to authenticate and call the API.

Creating an API credential on the Integrations tab — the API credentials table with client IDs masked, then the Create API credential dialog where you name the credential

Security tab

The Security tab covers password two-step verification (MFA) for everyone, and — on the Professional plan — single sign-on.

Two-step verification (MFA)

Owners and administrators must always use authenticator MFA on password sign-in. To require the same for every password user:

Open Administration → Organisation Settings → Security.
Under Two-step verification (MFA), turn on Require MFA for all password users.
Select Save.

Users who do not have MFA yet are asked to set it up the next time they sign in with a password (they are not logged out mid-session). Users cannot turn MFA on or off from My account — use Reset MFA only for lockouts. This setting does not prompt for LambdaAssetCheck MFA after SSO — even when both MFA and SSO are on. Use MFA at your identity provider for SSO. Full user steps: Two-step verification (MFA).

Single sign-on (SSO)

Configure single sign-on so your team signs in through your company identity provider instead of a password. SSO settings appear on this tab only when your organisation is on the Professional plan. Once SSO is set up, it applies to sign-in for your organisation — see Log in to LambdaAssetCheck. Full setup steps: Set up single sign-on.

The Security tab with Enable SSO switched on, revealing the redirect URI to add at your identity provider, the provider picker set to Google Workspace with its setup checklist, and the Issuer URL, Client ID, Client secret and Email domains fields

This is what an employee then sees on the sign-in page:

Shown in dark theme until a light-theme capture is available. Sign-in and Organisation settings may look light if that is your setting.

Was this page helpful?