> For the complete documentation index, see [llms.txt](https://docs.emory.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emory.pro/getting-started.md).

# Getting Started

This section guides you through the recommended setup process, from creating your organisation profile to running your first test inspection. Most teams can complete the initial setup in under two hours and perform their first real inspection on the same day.

### What you’ll need

Before you begin, make sure you have:

* Administrator access to your Emory Pro account
* Your company name and contact details
* A rough idea of the asset types and inspection types you want to configure
* A list of team members who need access
* Any existing asset data you want to upload, such as an Excel or CSV file

You do not need to have everything finalized before starting. Emory Pro is flexible, so you can add more users, assets, workflows, fields, and settings later.

### What to do next

Work through the following pages in order:

#### 1. Setup Overview

Understand the full setup process, the recommended order, the setup checklist, and the difference between admin and field user responsibilities.

#### 2. Create Your Organisation&#x20;

Add your company details, logo, primary contact, and organisation-level settings.

#### 3. Set Up Asset Types&#x20;

Define the structure, fields, and Asset Blueprints for each type of asset your team manages.

#### 4. Set Up Inspection Types&#x20;

Create inspection workflows for scenarios such as Check-In, Check-Out, Handover, Daily Check, Damage Inspection, and Quality Check.

#### 5. Set Up Lifecycle Stages

Define how assets move through your operation, for example from Inbound to Inspection, Storage, Outbound, Delivered, or Archived.

#### 6. Add or Import Assets&#x20;

Create assets manually, upload them in bulk using a spreadsheet, or import them through the Emory Pro API.

#### 7. Set Up Roles & Permissions&#x20;

Control what each user can see and do across assets, inspections, reports, tasks, and organisation settings.

#### 8. Invite Team Members&#x20;

Add internal users, external inspectors, subcontractors, partners, or customers who need access to Emory Pro.

#### 9. Install and Log In to the Mobile App

Prepare field users to complete inspections on [IOS](https://apps.apple.com/de/app/emory-pro/id6443503759) or [Android](https://play.google.com/store/apps/details?id=pro.emory.inspections\&gl=DE\&pli=1) devices, including offline inspection workflows.

#### 10. Run Your First Test Inspection

Validate your setup by completing a test inspection, capturing evidence, generating a report, and reviewing the final output.

### Need help?

If you need support during setup, contact us at <support@emory.pro>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.emory.pro/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
