> For the complete documentation index, see [llms.txt](https://docs.ai.insly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.insly.com/nora/onboarding.md).

# Onboarding

Setup and the input we need from you.

## How to use this guide

* **This page:** what Nora is and the ways you can use it.
* **The topic pages below:** each topic in detail.
* [**What we need from you, and when**](/nora/onboarding/what-we-need-from-you-and-when.md)**:** every input we need, with its deadline. This will be your checklist. Start here if you already know Nora.

Every input carries one of three deadlines:

| Deadline       | Meaning                                                                             |
| -------------- | ----------------------------------------------------------------------------------- |
| 🔴 **ASAP**    | At kick-off. Blocks work: nothing can be built until it arrives or takes more time. |
| 🟡 **TESTING** | Needed to test in Demo. The earlier it arrives, the earlier you can start testing.  |
| 🟢 **GO-LIVE** | Before rollout. Production (live) setup only.                                       |

## Nora at a glance

Nora reads insurance submissions (emails, PDFs, spreadsheets, Word files), extracts the data into your product’s fields, checks that it is complete and, optionally, creates the quote in Insly Ledger.

| Step          | What happens                                                                                                                   |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| 1. Intake     | A submission arrives by email or is uploaded in the Nora web app.                                                              |
| 2. Extraction | AI reads every attached file and the email body and fills in your product’s fields.                                            |
| 3. Validation | Nora checks required fields, allowed values (e.g. dropdown options) and formats.                                               |
| 4. Follow-up  | Email intake only. If required details are missing, Nora emails the sender for them and adds the reply to the same submission. |
| 5. Review     | Your team checks and corrects the data in the Nora web app: every submission, or a sample.                                     |
| 6. Completion | The quote is ready. Optionally it can be exported to Insly Ledger.                                                             |

**Two environments**

* **Demo:** for testing (optionally connected to your Ledger test environment).
* **Production (live):** for live use (optionally connected to Ledger production environment).
* Each has its own configurations such as users, whitelisted addresses and broker mappings, so most inputs are asked for each environment.

## Choose how you’ll use Nora

|                               | Web app only                             | Email only                        | Email + web app                      |
| ----------------------------- | ---------------------------------------- | --------------------------------- | ------------------------------------ |
| How submissions arrive        | Your team uploads files in the web app   | Senders email a dedicated address | Both                                 |
| Follow-up for missing details | No: your team fills gaps in review       | Yes, by email to the sender       | Yes, for emailed submissions         |
| Export to Ledger              | An approver exports each submission      | Automatic once complete           | Uploads: approver; emails: automatic |
| Who needs a web app login     | Everyone who uploads, reviews or exports | Reviewers only; senders never do  | Both groups                          |

**Decide:** which mode to use, and for which product(s). 🔴 **ASAP**