> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/gls-connector/gls-connector_en_us/licensing-and-plans.md).

# Licensing and Plans

How licensing, offers and permissions relate to each other and where to find the terms that apply to you.

This page explains how licensing for the app works and how it differs from permissions in Business Central. Prices and individual terms are not part of this documentation; they are in your current offer or the Marketplace listing.

## Licenses and permissions are two different things

|               | License                                            | Permission                                              |
| ------------- | -------------------------------------------------- | ------------------------------------------------------- |
| Question      | Is this person allowed to use the app at all?      | What is this person allowed to do in the app?           |
| Where defined | Through the purchased offer and license assignment | In Business Central through permission sets             |
| Example       | A person is licensed for the app                   | The person is assigned **GLS Integration User** to ship |

You need both. An assigned license alone does not grant access to the setup, and a permission set alone does not replace a license.

## Current licensing model

The regular AppSource plan assigns usage rights to **individual users**. Which people you need to license, how many usage rights are included and how billing works depend on your purchased offer and your license agreement.

Which plan applies to you, how many users are included and whether a trial is offered are defined in the current offer. Do not rely on periods stated in older documents; a fixed trial duration or a fixed expiry date does not apply to this app across the board.

## One-time purchase and updates

With a **one-time license** agreed with solutioo, the license is billed once through solutioo. The app is acquired through the designated Microsoft AppSource plan. **Future updates through Microsoft AppSource are included with the one-time license as well.**

For a subscription, the agreed terms and payment conditions apply. Prices and the purchased scope of services are stated in your offer. If you have questions, the solutioo sales team can help.

## What you also need from GLS

The app license does not include a GLS contract. You agree on credentials, products, services, countries and hazardous goods approvals directly with GLS.

## Tariff administration

Local tariff administration requires dedicated permission sets. Importing and managing tariffs is not automatically included in the standard shipping permissions. See [Installation and Permissions](/gls-connector/gls-connector_en_us/installation-and-permissions.md) and [Tariffs and Shipping Costs](/gls-connector/gls-connector_en_us/setup/tariffs-and-shipping-costs.md).

## Licensing questions

Write to <support@solutioo.de>. Include your Business Central environment and the installed app version. You can find the app in the [GLS Connector listing on Microsoft AppSource](https://marketplace.microsoft.com/de-de/product/dynamics-365-business-central/PUBID.tobiasghl1698658579854%7CAID.solutioo_14%7CPAPPID.3e6e4d00-ce16-4a21-9b22-bed6e333afaa?tab=Overview). Select the plan agreed with solutioo.


---

# 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.solutioo.de/gls-connector/gls-connector_en_us/licensing-and-plans.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.
