> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/partner-portal/creating-partner-specific-pages.md).

# Creating Partner-Specific Pages

You can restrict access to specific pages in Limio Commerce so only authenticated partner users can view them. This guide explains how to set up the authentication in the Limio settings and how to apply the partner authentication to certain pages.

## Set up new partner authentication

*This guide applies only to **OpenID Connect** authentication. The **Is Partner** setting is not available for other authentication types.*

1. In Limio Commerce, go to **Settings → Authentication Providers**.
2. Create a new authentication provider by clicking **OpenID Connect.**
3. Fill out the fields normally.
4. Find the **Is Partner Auth?** field. Tick the checkbox to mark this provider as a partner authentication provider.
   * **Default**: Unticked (false)
   * Leave it unticked for regular customer login flows.
5. Click **Save**.

Please note that you will typically only need to configure one partner authentication provider. Partner eligibility to purchase certain offers is configured on the offer itself. Read this article to find out more:

When this authentication provider is used on a Limio Shop page, if the user’s email matches a partner user in the :

* the user will be provided with a OTP via email
* upon successful login, the JWT token will include the following claim:

```auto
"lmo:partner_org": "12345"
```

If the user’s email **does not** match any partner user:

* the user will not be sent a OTP via email, so they will not be granted access to partner-only pages.

## Apply partner authentication to pages

On each page you want to restrict to partners, follow these steps:

1. Open the Page.
2. Open the Settings.
3. Set **Require Authentication?** to true.
4. Set **Auth Provider** to the partner authentication method you set in in the stage above.
5. Click confirm.
6. Click Save.
7. Rebuild and republish your page.

## Typical partner pages required

This is a list of typical partner pages you will need for your partners to create and manage customer subscriptions.

Read our [Partner Portal Guide](https://docs.limio.com/guides/feature-implementation-guides/guide-partner-portal) for step-by-step instructions.

**Purchasing a new subscription:**

* Offers page
* Checkout page - see our [Modular Checkout guide](https://docs.limio.com/product/~/revisions/odxPCKTJ4escQ74ZDQLs/checkout/overview-how-to-customise-the-limio-modular-checkout) to get started
* Order complete page

**Managing existing customers and subscriptions:**

* List of all of partner's customers - use the [Partner Customers Table](https://docs.limio.com/components/component-library/partner-portal-components/component-partner-customers-table)
* List of all subscriptions for one specific customer - use the Subscription Details component
* Update subscription pages - see our [Update Subscription guide](https://docs.limio.com/product/~/revisions/gC564qJSw4wiACLAgMiY/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-configure-an-update-subscription-flow) to get started


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/product/partner-portal/creating-partner-specific-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
