> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/features/user-interface/sharinpix-add-licenses.md).

# SharinPix Add Licenses

## Overview

SharinPix provides a way to request additional licenses for existing contracts.

In the following sections, you will learn:

* [*How to review existing license assignments*](#review-existing-license-assignments)
* [*How to use the "SharinPix Add Licenses" tab to request additional licenses*](#add-licenses)

{% hint style="warning" %}
**Prerequisite:**

* The SharinPix Package Version 1.309 (or later) is installed; refer to the article below to upgrade your current package: [*How to upgrade SharinPix package*](/faqs/how-to-update-sharinpix-package-from-the-appexchange.md)
  {% endhint %}

## Review existing license assignments

Verify that your account needs additional licenses before requesting more.

1. Navigate to Setup
2. Type "Installed Packages" in the *Quick Find*(left column)
3. Click "Installed Packages"
4. Find the SharinPix package in the list, and click Manage Licenses
5. Review your current *Allowed Licenses* and *Used Licenses*

![](https://2221230591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5EvYRrLbUyvRh8o1jmMG%2Fuploads%2Fgit-blob-d19e633772fdef290c51f02d10b85eee140c8053%2F2025-05-12_Installed%20Packages.png?alt=media)

## Add Licenses

To request that additional licenses are added to your organization's contract:

* Click the Launcher and type "license" in the *Quick Find*.
* Click "SharinPix Add Licenses"
* Enter the number of licenses to add in *New License*.
* Click to acknowledge that you have been authorized
* The "Validate" button will become active. Click "Validate".

SharinPix will review the request and activate approved licenses within 24 hours of receiving payment.

An explanation of the fields on the "Add Licenses" tab is provided below:

![](https://2221230591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5EvYRrLbUyvRh8o1jmMG%2Fuploads%2Fgit-blob-6a85a989d40a8d3505d9a1364f002ad538d138e3%2F2025-05-12_Add%20Licenses.png?alt=media)

1. *Current Contract* - provides information about the existing contract
2. *Type -* this is the type of license included with the contract
3. *Number of Months* - the number of months remaining on the contract
4. *Unit Price* - the cost per license per month for any additional licenses requested
5. *New License* - enter the number of additional licenses to be added
6. *Price -* the months remaining x the unit price x the New License. This is the amount you can expect on your invoice to complete your current contract. It will appear once you have entered a desired number of New Licenses.
7. *New contract after validation* - provides the projected price to be charged at renewal.


---

# 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.sharinpix.com/documentation/features/user-interface/sharinpix-add-licenses.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.