> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-resellers/introduction-to-resellers.md). # Introduction to Resellers Discover how Zentitle's Reseller Portal lets Enterprise customers build multi-tier reseller hierarchies with delegated, permission-based access and full central visibility. ### Reseller Portal — Modern Channel Management, Built In Many ISVs sell both directly and through partners. As those partner ecosystems grow, they often evolve into multi-tier structures — typically ISV → Distributor → Reseller → Sub-reseller. Managing this complexity with spreadsheets, manual license blocks, or legacy tooling quickly becomes a bottleneck. Zentitle’s Reseller Portal was built specifically to solve this — natively, cleanly, and without bolt-ons. *** #### Designed for Real-World Channel Structures Enterprise customers can create resellers and sub-resellers beneath their own account, mirroring real commercial hierarchies. Each reseller gets secure access to only what they are entitled to see and manage, while you retain full visibility and control across the entire channel. * Create as many reseller tiers as you need * Assign reseller-specific users, entitlements, and permissions * Delegate day-to-day operations without losing governance or control * Pause or terminate a reseller (and their entire sub-channel) with one click * Have a complete picture of your entire channel, with detailed sales and analytics data, all on one platform * Retain full control of your IP. You can control every end-user's entitlement centrally should there be a need to access them {% hint style="info" %} This functionality is available to **Enterprise** customers. If it’s not yet enabled in your package, speak with your Account Representative. {% endhint %} *** #### License Separation Without Complexity Reseller management works seamlessly with offerings and entitlements, ensuring that every license is: * Clearly associated with a specific reseller * Fully auditable end-to-end * Isolated from other channels and partners The result is clean separation, accurate reporting, and zero ambiguity — even at scale. *** #### Simple, Secure, and Permission-Driven You decide exactly what each reseller can do: * Create and manage licenses * View entitlements and trials * Support their own end customers * Integrate with their internal systems via APIs All without exposing other resellers, internal data, or master-level configuration. *** #### How This Compares to Legacy Alternatives Many traditional licensing platforms technically *support* resellers — but often through manual processes, separate systems, or custom professional services: * Platforms such as Flexera/Revenera typically rely on complex entitlement trees, offline reporting, or heavy configuration to approximate multi-tier resale. * Solutions like Thales Sentinel or Reprise Software often treat resellers as an extension of internal operations rather than first-class users, increasing operational overhead and support dependency. Zentitle takes a cloud-native, account-based approach instead: reseller access, hierarchy, and reporting are built into the core platform — no scripts, no custom projects, no fragile workarounds. *** #### Built for Scale, Not Administration With Zentitle, reseller enablement is no longer a trade-off between reach and control. You get: * Faster partner onboarding * Lower internal support burden * Cleaner reporting and audit trails * A modern UI your partners actually want to use *** #### Get Started To begin configuring your reseller structure today, continue with the documentation that follows to see how the Reseller Portal works in practice. ***Modern channel sales shouldn’t require legacy complexity — and now, they don’t.*** --- # 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.nalpeiron.com/zentitle2-docs/ui-resellers/introduction-to-resellers.md?ask=&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.