Partner User Guide
As a partner to an organization using Pandium, you have the ability to create, submit, and maintain integrations and marketing content directly within the Pandium Integration Hub.
Last updated
.svg?alt=media&token=47f65a9a-1173-415f-99c4-53091d7c9a52)
As a partner to an organization using Pandium, you have the ability to create, submit, and maintain integrations and marketing content directly within the Pandium Integration Hub.
Last updated
With the creation of a partner organization, the Pandium Administrator creates the initial primary contact user for a partner organization. This contact will receive a welcome email from Pandium with instructions on how to login and set a password.
If a partner form has been set up by the Administrator, it will show on initial login, and must be completed before the partner can login and invite other partners users, or submit integrations. This form will usually include questions that the Pandium Administrator requests are answered before submitting integrations.
If no such form is set up, then a partner can login and immediately begin adding other partner users or begin creating an integration within the Integration Hub.
Partners in the Integration Hub can see their Integrations, Tenants, and Settings.
After an integration has been approved by your Pandium Administrator, new tenants (sometimes called instances) can be created on behalf of your customers. Additionally, any tenants associated with your organization's integrations can be managed in one central location moving forward, making it easy to support your shared customers.
Creating an integration is a straightforward process as a partner. Once logged into Pandium, follow the below steps to start:
Navigate to the Integrations sidebar resource, then click Create in the top right.
Select the Integration Type to create. Below is an explanation of integration types.
Internal integrations are powered by Pandium, and require more thorough configuration. With internal integrations, Pandium creates releases based on changes to your repository.
External Integrations can be used to create "empty" tiles for integrations, purely as placeholders or marketing collateral. They are also used for creating integration tiles for pre-existing and third-party integrations that you wish to leverage in the Integration Hub.
This is most relevant when wanting to show integrations hosted in your partner's marketplace, or showing integrations that Pandium doesn't manage. See Embedding the Marketplace or ask your Pandium Administrator for more information.
External integrations are simple to setup, only requiring a link to the landing page where your integration is hosted, and an ID for how Pandium should refer to this integration programmatically.
Internal Integration will bring you to an integration configuration process, where information is required to submit your integration for review. Those options are explained below.
The initial step in the process is telling Pandium the connectors, or systems, that your integration will be utilizing. Selecting the Global option on a connector will ensure that no individual tenant authenticates to this connector, and that all of your tenants will share the same global secrets. This global authentication is set by the creator of the integration. An example of this might be a single SFTP location where all end user data is sent to.
Applying to both types of integrations, here is where you fill in the information you want displayed for end user discovery as well as a unique identifier for your integration.
Next is the repository settings, which is where you tell us where your integration code lives - this is the information that Source Control uses to keep your integration updated.
Repository URL: A link to a repository - Github, GitLab, Bitbucket, or Azure.
Repository Path: Path to the PANDIUM.yaml file relative to the root of the repository. If left blank, we will look for the file directly in the root.
Here, you set a default sync schedule or sync schedule options that the end user will be able to select when setting up their integration. In either case, you can use simple intervals, or use cron string format to define the frequency of syncs. The tenant sync schedule can be set as active or not on an initial install by toggling 'Paused sync schedule by default'.
Once created, the configuration settings will be saved for the integration. If your Pandium Administrator utilizes the feature to set custom integration-level questions, those questions will show on a following tab:
Selecting 'Save' will save your integration to the Drafts tab so that it can be finalized later, while selecting 'Submit for Review' will move the integration to the In Review tab, and alert your Pandium partner manager that your integration has been submitted and is ready for review.
Once an integration is in review, your partner manager can send feedback if there is a need to edit or add information. You will see any feedback in a yellow box at the top of your integration detail pages in the Integration Hub, as well as seeing a 'Requires Review' badge on your integration in the 'Pending' tab.
Regardless of if there is feedback or not, once approved, the primary contact on the partner organization will be notified via email, and the integration will move to the Published tab of the Integration page.
At any time after an integration is submitted, Marketplace settings can be set if desired. On the Integration detail page, locate the integration and click the 'Marketplace Setup' button near the top right.
This contains options to edit the theming and content of the marketplace display tile that corresponds to the integration. Your partner manager will also be able to edit this information on their end to better fit their theme if needed.
More information on the specific options within these settings can be found in Marketplace Settings.
Once set, these options will reflect on any relevant marketplaces, as well as in the Integration homepage.
Note: The Partner Portal and related features are not included in the Pandium Lite offering.
