> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/readme/users-of-pandium.md). # Users of Pandium ## Platform User A Pandium platform user is an employee of a B2B software company that has access to the Integration Hub part of the platform. This user may be a customer success rep, partnership manager, product manager and/or marketer. Platform users troubleshoot, configure, and onboard end-customers to new integrations. A platform user may also run reports, monitor behavior, or set up marketplaces or marketing content. ## Engineering User A Pandium engineering user is the software developer who is building integrations that run on the platform. An engineering user may be an employee of your customer, a partner's engineer, a third-party developer like a development agency, or a member of Pandium's professional service team. Engineering users typically provision new integrations and then perform development locally. From there, an engineering user's interaction with the platform is typically related to version management, testing, and troubleshooting. ## Partner User A partner user is a third-party user that is submitting integrations to our customer. Often a partner user is another SaaS company that wishes to be listed in your Pandium-powered marketplace; however, a partner user could also be a development or marketing agency. Partner users can submit marketing content and/or apps for approval and publication in your first-party marketplace, and can also see tenants and activity associated with integrations they own. Partners are invited by Pandium users and access can be revoked at any time. ## Customer End User An end-customer user is the business user that is the customer of Pandium's customer. End-customers are often referred to as tenants, and they are the ultimate consumers of apps running on Pandium. End-users typically do not know that Pandium exists but interact with the platform through a white-labeled UI that is hosted by Pandium, living inside your application. End-customers authenticate into connected systems and manage their own configuration options as specified by the engineering user of the platform. --- # 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.pandium.com/~/revisions/x7Thkx1S9I9SnLbXNFwg/getting-started/readme/users-of-pandium.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.