> 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/sales-and-distribution/access.md).

# Access

Access decides which of your products a partner can see and sell. You open products by activating **destinations** on the partnership, and you refine with an include/exclude list. Access is closed by default: a partner sees nothing until you open it.

***

## Three scope modes

A partnership runs in one of three modes. Market-curated is the default and covers most cases.

<table><thead><tr><th width="190">Mode</th><th>What the partner sees</th></tr></thead><tbody><tr><td><strong>All catalog</strong></td><td>Your entire catalog, minus anything you explicitly exclude. Use for a fully trusted partner.</td></tr><tr><td><strong>Market-curated</strong> <em>(default)</em></td><td>Everything in the destinations you activate, minus excludes, plus any out-of-market products you include.</td></tr><tr><td><strong>Explicit list</strong></td><td>Only the products you add by hand. Nothing is visible until you include it.</td></tr></tbody></table>

***

## Market-curated, default-open

In the default mode, you open products by geography and then trim.

{% stepper %}
{% step %}

### Activate destinations

Activate the destinations the partner may sell — *Georgia*, *Türkiye*. The partner immediately sees every product whose location falls under an activated destination.
{% endstep %}

{% step %}

### Exclude what should stay out

Remove individual properties or rate plans from the opened set — a property you keep direct-only, for example.
{% endstep %}

{% step %}

### Include anything out of market

Add a specific product that sits outside the activated destinations but should still be sellable to this partner.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Default-open within an activated destination.** Once you activate *Georgia*, the partner sees all your Georgia products — you do not list them one by one. You only name the exceptions.
{% endhint %}

***

## Country restriction is automatic

You never set a "country block". A product is simply invisible until its destination is activated for the partner. So a partner that sells from Kosovo but has no *Georgia* destination activated cannot see — and cannot sell — your Georgia products. Restriction is the natural result of what you have not opened.

***

## Tenant access profiles

The scope modes above control what a *partner* sees of your catalog. A separate, tenant-level control — the **access profile** — decides which sections of the console a tenant sees at all.

A tenant on the **LITE access profile** gets only the essentials:

* the dashboard,
* their bookings,
* the partner sales side — what they can sell as a partner,
* onboarding,
* and user management within their own tenant.

Everything else — catalog, pricing, contracts, insights, financials, mapping, connectors and Adrasis AI Operator — stays closed. A LITE tenant suits an early-stage relationship: enough to transact and onboard, nothing more. When the full commercial relationship is in place, switching the tenant to the full profile is a single deliberate change — never triggered automatically by a payment or a signup.

{% hint style="info" %}
**Closed means closed.** A LITE tenant cannot reach a closed section by typing its address. Access is enforced on every request, not just hidden from the menu.
{% endhint %}

## Where to next

* **Build the destinations you activate** → [Markets](/console/sales-and-distribution/markets.md)
* **Price the products you open** → [Pricing rules](/console/sales-and-distribution/pricing-rules.md)
* **How a partner sells what you opened** → [Selling as a partner](/console/sales-and-distribution/selling-as-partner.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/sales-and-distribution/access.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.