> For the complete documentation index, see [llms.txt](https://adrasis.gitbook.io/console/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adrasis.gitbook.io/console/contracts-and-onboarding/onboarding-flow.md).

# Onboarding flow

**Onboarding** is how a new commercial relationship — a property, a supplier, a partner agency, or a workspace — becomes ready to sell and operate in Adrasis. The platform provides a guided flow so the work stays consistent: relationship, setup, signing, and go-live.

## Three onboarding paths

The console offers three primary onboarding flows; each starts from a different commercial situation but ends in the same place — operational data live in your organization.

| Path                        | Starting point                                                             | What you end with                                                                                                       |
| --------------------------- | -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Property onboarding**     | A new property you operate or contract directly                            | A canonical property in your catalog, channels bound, mappings complete, ready to publish.                              |
| **Supplier onboarding**     | A new source of inventory you will resell                                  | An ingestion pipeline from the source, mapping complete, contract terms recorded, ready to expose to your distribution. |
| **Organization onboarding** | A new organization in your group (subsidiary, white-label, partner agency) | A organization configured with branding, locale, currency, default policies, ready for users.                           |

Most operators run all three at different times. The flows share their underlying steps — set up the relationship, configure the data, sign what needs signing, go live.

## Property onboarding

<figure><img src="https://2136275255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KCdaQhBoltBaPQD0D0Y%2Fuploads%2Fgit-blob-88f181bd05ebc7f103aae671b335d323559ae0e4%2Fonboarding-property.svg?alt=media" alt="Property onboarding — relationship → setup → signing → live"><figcaption><p>The steps a single property goes through to become a live, sellable record.</p></figcaption></figure>

Each step has a console surface; Adrasis AI Operator can drive most of them on confirmation. A 30-room boutique with a single rate plan and one channel is a focused 1–2 hours of operator time; a 400-room resort with 6 room types, multiple meal plans, child-age tiers, and 8 channel bindings can run half a day to a full day, mostly waiting on partner-side certification — but the steps stay the same.

The full property surface is in [Property](/console/catalog/property.md).

## Supplier onboarding

<figure><img src="https://2136275255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KCdaQhBoltBaPQD0D0Y%2Fuploads%2Fgit-blob-bb597e48a9b35f0af3e7529cd57a84df38e0ff87%2Fonboarding-supplier.svg?alt=media" alt="Supplier onboarding — connector → contract → mapping → live"><figcaption><p>Bringing a supplier into your catalog. Mapping review is where most operator time goes.</p></figcaption></figure>

Supplier onboarding is heavier on mapping than property onboarding because every supplier has its own vocabulary. In a typical bedbank ingest of 5,000 properties, many matches can be handled in batches while unfamiliar amenity codes, ambiguous room types and fuzzy property names need a human decision. The AI Operator fills in the obvious matches; you decide the rest.

The supply ingestion details are in [Inbound overview](/console/distribution/inbound.md) and [Mapping & review](/console/mapping-and-review/canonical-mapping.md).

## Organization onboarding

<figure><img src="https://2136275255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5KCdaQhBoltBaPQD0D0Y%2Fuploads%2Fgit-blob-a523b502db5a5e2ebc61371180e31ba68f2cd082%2Fonboarding-organization.svg?alt=media" alt="Organization onboarding — application → activation → defaults → live"><figcaption><p>Bringing a new organization onto the platform. Defaults inherit; every step can be overridden.</p></figcaption></figure>

A new organization typically inherits configuration defaults from the platform but can override every step. White-label brands often deviate on branding and currency; partner agencies often deviate on policies and signature counterparties.

Each organization is its own workspace with its own users, catalog, contracts, distribution and payment configuration.

After an organization application is approved, its authorized signer can receive one private link for the three onboarding agreements. Signing is account-free and tracked separately from tenant creation; the tenant administrator retrieves completed documents from the Console. See [Sign onboarding agreements](/console/contracts-and-onboarding/e-signature.md) for statuses, expiry, and recovery.

## What stays the same across paths

Three properties hold across every onboarding path:

* **Step-by-step with previews.** Nothing commits without explicit confirmation; you can pause and resume.
* **AI Operator assists.** Bulk content, bulk mapping, bulk channel binding — all addressable in natural language.
* **Clear status.** Each flow shows what is complete, what is blocked, and what needs the next action.

You do not need a different muscle memory per path; the flow shape is consistent.

## What slows onboarding down

A few things commonly extend the work:

* **Mapping the unfamiliar.** A new supplier with an unusual amenity vocabulary or category set requires more review. The AI Operator reduces but does not eliminate this.
* **Content gaps.** A new property without good photos or multilingual descriptions blocks publishing — you fill the gap before going live.
* **Contract complexity.** A heavily-customized contract with many overrides per property takes longer to capture cleanly.
* **Partner certification.** Some channels require certification rounds before traffic flows; that timeline is the partner's, not yours.

Each of these has a clear surface in the console; you see what is blocking and what to do next.

## AI Operator and onboarding

Common phrases that map to the AI Operator onboarding operations:

* *"Onboard the property described in this forwarded email — extract name, address, room count, and start the flow."*
* *"For the new supplier, find every room in their catalog and propose mappings to our canonical room types."*
* *"Run a checklist on the new white-label organization — branding, locale, currency, default policies — and tell me what's missing."*
* *"Activate every property bound to the new bedbank supplier once their first ingest succeeds cleanly."*

Read operations return immediately; writes preview before applying.

## Where to next

* **The contract layer that backs every onboarding** → [Contracts](/console/contracts-and-onboarding/contracts.md)
* **The organization onboarding signature step** → [Sign onboarding agreements](/console/contracts-and-onboarding/e-signature.md)
* **The catalog the property landing-pad sits in** → [Catalog](/console/catalog/catalog.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://adrasis.gitbook.io/console/contracts-and-onboarding/onboarding-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.