# FAQ

> Quick answers to the questions new AssetLab teams ask most.

Source: https://app.assetlab.ca/docs/start/faq

## Accounts & sign-in

### How do users sign in?

With their email address and a one-time passcode - no passwords to manage, reset, or leak. On the Enterprise plan, single sign-on is set up self-serve under **Settings → SSO** - see [Security & data residency](/docs/manage/security).

### Can one person belong to several organizations?

Yes. A consultant or shared-services manager can be invited to multiple organizations with a different role in each, and switch between them from the profile menu.

### Someone left the team - what happens to their records?

Remove the user under **Settings → Users**. Their history stays intact (work orders they completed, comments they wrote), but they can no longer sign in. Reassign their open work orders from the work order list.

## Data

### Where is my data stored?

Your records and uploaded files are stored in Canada (`ca-central-1`). A few supporting services - sign-in, outbound email, error monitoring - run in the United States; they're listed individually on [Security & data residency](/docs/manage/security), along with what each one handles.

### Can I get my data out?

Always. Every list view exports to CSV/Excel, the [REST API](/docs/reference/rest-api) exposes every resource, and Administrators can export each record type to CSV from the **Settings → Import** tab (Settings → Data also offers quick exports of assets, work orders, and PM schedules). Your data is yours.

### Is there a sandbox to experiment in?

Use a pilot import - bring in a small trial file with the [import wizard](/docs/start/importing-data), inspect the result, and iterate: re-importing a corrected file updates matching rows in place. For a fully separate environment, ask support about a second organization.

## Modules

### Do I need the Infrastructure module if I only manage buildings?

No. Facilities teams live entirely in [Asset Management](/docs/asset-management) and [CMMS](/docs/cmms). The [Infrastructure module](/docs/infrastructure) exists for linear networks - roads, water, sewer - and stays out of the way otherwise.

### What's the difference between a work request and a work order?

A **work request** is what a [requester](/docs/cmms/requester-portal) submits - unvetted, no asset required. A **work order** is scheduled, assigned work that staff execute. Requests are triaged and converted into work orders. See [Work requests](/docs/cmms/work-requests).

### Can AssetLab handle both my arena and my roads?

Yes - that's the point. Vertical assets live in the registry, linear assets live in Infrastructure, and dashboards, projects, and reporting see both.

## Integrations & AI

### Which AI assistants work with AssetLab?

Claude (claude.ai, Claude Desktop, Claude Code) and ChatGPT, through the [MCP server](/docs/ai). Any MCP-compatible client can connect.

### Is there an API?

Yes - a REST API covering every major resource, authenticated with scoped, tenant-bound [API keys](/docs/manage/api-keys). API access is part of the Enterprise plan (or available as an add-on on other plans). Start at [REST API basics](/docs/reference/rest-api), then explore every endpoint in the [interactive API reference](/docs/reference/api).

### Can AssetLab notify other systems when something changes?

Yes - [webhooks](/docs/manage/webhooks) push events (work order created, asset updated, …) to any HTTPS endpoint you register.

### Is AssetLab down, or is it just me?

Check [status.assetlab.ca](https://status.assetlab.ca) - live service status and incident history. If status is green and you're still stuck, it's worth an email.

## Something else?

Email [support@assetlab.ca](mailto:support@assetlab.ca) - a human reads it.