> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/common-scenarios/glossary/vendor-platform.md). # Vendor Platform ### Customer Basic [**Customer**](/vendor-platform/customers.md) information is stored within the LicenseSpring platform as customer profiles. These profiles contain essential details about customers, such as their name and email address. By having this information stored in the platform, it becomes convenient to search for orders of licenses associated with a specific customer. ### Customer Accounts [**Customer Accounts**](/vendor-platform/customer-accounts.md) are a way to group multiple business units of an organization within the LicenseSpring platform. They allow convenient organization and management of customers based on specific criteria or attributes. ### Customer Import The system allows a requesting manager to import customers from a CSV file if they have the necessary access permissions. For more information, see [**Customers Import**](/vendor-platform/importing-exporting-data/customers-import.md). ### Customer Labels [**Customer Labels**](/management-api/customer/labels/list-customer-labels.md) are tags or labels that can be assigned to customers or organizations to categorize and group them based on specific criteria or attributes. ### Customer/Product/License Metadata Customer metadata provides insights into individual customers, product metadata provides details about specific software products, and license metadata provides information about the characteristics and status of software licenses. ### Customer Reference A customer reference is contact information or testimonials from existing customers who have successfully implemented and used the software. These references serve as a way for potential customers to gain insights into the experiences and satisfaction levels of current customers. ### Disabling a License [**Disabling a License**](/vendor-platform/licenses.md) revokes all entitlements associated with the specific key. For example, if an end user requests a refund or decides to discontinue using an application, the software publisher can issue a refund and disable the license key, preventing further access to the full version of the application. ![Disabling a License](/files/cd27327338ef5eb5e58eceb5e992f008d10d274d) ### License A license is a legal agreement or permission granted by a software vendor or provider that allows individuals or organizations to use a specific software product or service. It establishes the terms and conditions under which the software can be utilized, including usage rights, limitations, and any associated entitlements. Within LicenseSpring, licenses are closely linked to orders. An order refers to a transaction or purchase made within the LicenseSpring system, and each license is associated with a specific order. This means that multiple licenses can be issued under the same order, allowing for efficient management and administration of licenses. ### License Export If a requesting manager has the appropriate access permissions, they can [**Export Licenses**](/vendor-platform/importing-exporting-data/license-export.md) to a CSV file. ### License Import The system allows a requesting manager to [**Import licenses from CSV**](/vendor-platform/importing-exporting-data/license-import.md) if they have the necessary access permissions. ### License Manager Permissions License manager permissions refer to the specific rights and privileges granted to individuals or roles responsible for managing licenses within a software licensing system. These permissions determine the actions that license managers can perform and the level of control they have over license-related activities. To see a list of permissions, see: [**The License Manager**](/license-entitlements/portal/end-user-portal/the-license-manager.md). ![Assigning Permissions](/files/98ad789f830d217367a4c788382ab81fc8c4a10b) ### License Status License status refers to the current state or condition of a license within a software licensing system. It indicates whether a license is active, inactive, expired, revoked, or in any other predefined state that determines its validity and usage rights. To see a list of potential license statuses, see: [**License Types**](/license-entitlements/license-types.md). ### License Usage Report A license usage report provides comprehensive information about the utilization of licenses within a specified timeframe. This report presents data on license activations, deactivations, and other relevant metrics that help assess the usage patterns and trends. ![Usage Report Page](/files/9d5a1b39a9838f99817c75447b93e19923763c37) ### Linked Accounts Linked accounts refer to the capability of associating multiple user accounts or entities together within the software system. This feature allows for centralized management and control of licenses across connected accounts. ### Notification Events [**Email Notifications**](/vendor-platform/settings/email-notifications.md) are triggered when specific conditions are met. Users have the ability to define notification policies, modify or remove them, monitor notification history, and customize email templates for each event. ### Order An [**Order**](/vendor-platform/orders.md) refers to a transaction or purchase made within the LicenseSpring system. It is associated with a specific order number that serves as a unique identifier. In LicenseSpring, every license is linked to an order, and multiple licenses can be issued under the same order. The order serves as a container for organizing and managing licenses, allowing for easy tracking and administration of license-related activities. ### Platform Audit Log The [**Audit Log**](/vendor-platform/settings/audit-log.md) is a useful table to keep track of all essential actions performed within an account and who performed them. ![Audit Log](/files/5755b3b6c43e7065bfe0cace4ba0065f2eba40bf) ### Platform Permissions [**Platform Permissions**](/vendor-platform/settings/roles-permissions-user-labels.md) refer to the customizable rights and privileges that can be assigned to platform users within a software platform or management system. These permissions determine the actions and functionalities that platform users are allowed to access and perform within the platform. ### Platform Users List of users that have access to the platform account. ### Resetting a License [**Resetting a License**](/management-api/license/reset-license.md) revokes all existing entitlements from any previously authorized computers and restores the license key to its pre-activation state. This process erases any linked hardware ID, and the validity and maintenance periods are reassigned upon the next activation of the license key. Resetting a license is useful when a user changes computers. ### SSO Settings The configuration and customization options for implementing [**Single Sign On (SSO)**](/common-scenarios/single-sign-on-sso.md) authentication in an application or system. SSO allows users to authenticate once with their credentials and gain access to multiple systems or applications without the need to log in separately for each one. --- # 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://docs.licensespring.com/common-scenarios/glossary/vendor-platform.md?ask=&goal= ``` `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.