> This page is for Product Documentation.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Customer Portal overview

> Overview of the Customer Portal, NaviPartner's web app for tenant, user and license management, and where it is heading.

The **Customer Portal** is NaviPartner's administration web app. It runs in the browser at [<ins>portal.navipartner.com</ins>](https://portal.navipartner.com), signing in with a Microsoft account (see [Getting access](#getting-access) for details).

## What it covers today

The portal currently handles three areas:

* **Tenant management** — the customer's tenant. Its Business Central (BC) environments show up here too: they register themselves from BC, so nobody creates them by hand, but they are still managed here — that's where their license quotas are set.
* **User management** — who has access to the portal, and what they are allowed to do (see [Getting access](#getting-access)).
* **License management** — how many licenses a customer has bought, and how those are shared across their BC environments (see [License management](#license-management)).

Other systems read this data from the portal instead of keeping their own copy. NP Retail, NaviPartner's POS solution in BC, uses the license data to control POS access.

## Getting access

Everyone signs in with a **Microsoft account** — there's no separate portal password, and Microsoft may ask for consent the first time you sign in, including for customer accounts.

* **NaviPartner staff** are usually added automatically through internal Microsoft groups — an option unique to NaviPartner's own tenant. They can also be invited directly, like anyone else.
* **Customer users** don't have the group option. They either request access themselves from the sign-in page, or are invited directly by an admin — NaviPartner's or their own organization's.

Either way, once you're added or your request is approved, you can sign in right away. There's no email notification for this yet, so check back rather than waiting for one.

## License management

The portal holds the number of licenses a customer has bought — the license pool — and splits it across their BC environments when a tenant has more than one.

Go to **Tenants → Licenses** to see the pool: how many licenses the customer has of each product and term, for example POS for 1 year. Everything below is limited by these numbers, so a customer with no POS licenses recorded here has no POS seats anywhere.

Go to **Tenants → Environments** to split that pool, by setting a license quota per production environment. This is only needed for tenants with two or more production environments — a tenant with a single environment gets the whole pool automatically, which is why most customers never need to touch this. When quotas are needed, every production environment needs a number: one left empty counts as **0**, and the portal won't let you save until all of them are filled in and add up to no more than the pool.

Splitting is switched on and off with **Environment-scoped licensing** on **Tenants → Features**, and it is normally on. With it off, quotas are still saved but not applied, and every environment can draw the whole pool — the Environments page says as much when that's the case. The switch needs **License configuration** on the same page, which is on for customer tenants but off to start with for partners and for NaviPartner's own tenant.

Any admin can turn **Environment-scoped licensing** on, but only **NaviPartner staff** can turn it back off. This is a safeguard: with it off, the same licenses count towards every environment at once.

See [<ins>Set up module licensing</ins>](/product/retail-module-licensing-setup) for the BC side of the setup.

## Where it is heading

More will move into the portal over time. The goal is a single interface where NaviPartner and customers manage the things they have in common, instead of using a separate tool for each task.

#### See also

* [<ins>Set up module licensing</ins>](/product/retail-module-licensing-setup)