Skip to main content
Multi-Configuration allows you to use one connected account authorization (1 credential) to set up multiple configurations of User Settings or Workflow enablements for your users. For example, if your Google Drive integration might require you to set up different workflows for different folders that your user wants to watch, Multi-Configuration can provide a separate “instance” of the Connect Portal to show for each of those folder configurations.
Configurations currently do not appear in the Connected Users Dashboard.Any workflow enablements that are displayed in the Connected Users page represent the default configuration, and values for other configurations can only be viewed and modified with the API at this time.

​
Configurations

A Configuration is a set of User Settings and Workflow Enablements associated with one connected account (credential), as shown here:
In the above example, User A with Google Drive Credential A can have NN configurations associated with that credential.
  • Different sets of Workflows can be enabled / disabled for each configuration.
  • Different User Settings can be used for each configuration.
  • Configurations can be associated with an External ID (an ID that you provide).
    • An External ID which can be used to reference a Configuration(s) in place of a UUID, in the following format: ext:[External ID]
    • For example, if the configuration is created with externalId: "Team A", it can be addressed in the Paragon User Token as configuration:ext:Team A.

​
Usage

​
Creating and managing configurations

To create a new configuration, call createConfiguration with a credentialId to attach the configuration to and an optional externalId to reference this configuration in the API. 
const config = await paragon.createConfiguration({
    // The credential to create this configuration from
    credentialId: "...",
    // An external ID that can be used to reference this configuration from the API
    externalId: "Team A"
});
// -> { id: "", credentialId: "", settings: {}, configuredWorkflows: {} }
The createConfiguration call will return a Promise that resolves with the saved configuration object. After creating a configuration, it will be included in the getUser() response under each integration, in both the allConfigurations array and within the configurations property of each credential object. 
paragon.getUser();
// -> { jira: { allCredentials: [{ configurations }], allConfigurations: [] } }
Finally, you can destroy a configuration (removing any User Settings and disabling any workflow enablements for the associated configuration) with destroyConfiguration: 
// Destroy a configuration of this credential
await paragon.destroyConfiguration({ id: "ext:Team A", credentialId: "..." });

​
Presenting the Connect Portal

After creating a configuration, you can present a Connect Portal by passing selectedConfigurationId. You can pass a configuration UUID or the external ID prefixed with ext:to reference the configuration. 
// Open Connect Portal of this configuration
paragon.connect("jira", {
  selectedConfigurationId: "ext:Team A"
});
You can also use Headless Connect Portal functions for managing workflow enablements with the configuration ID: 
// Manage Headless workflow enablements for this configuration
await paragon.enableWorkflow("workflow-id", {
  selectedConfigurationId: config.id
});
await paragon.disableWorkflow("workflow-id", {
  selectedConfigurationId: config.id
});
Note: All credentials have a default Configuration included, which will be used if the configuration does not exist or if selectedConfigurationId is undefined.

​
Calling the API

You can use selectedConfigurationId as an option for SDK calls and X-Paragon-Configuration-Idfor API calls. 
// Send an App Event for this configuration only
await paragon.event("workflow-id", {
  selectedConfigurationId: config.id
});

POST /sdk/events

X-Paragon-Credential: a1304037-d994-40ef-894a-8d6c55f65f7c
X-Paragon-Configuration-Id: ext:Team A

​
Access Control

If you are using Multi-Configuration to enable different groups of users (such as teams) within one organization to set up distinct configurations of an integration, you may want to control which authenticated users in your application have visibility to each configuration. You can use JWT Permissions to encode these visibility controls into your Paragon User Token:

JWT Permissions

Learn more abut implementing JWT Permissions to control access to configurations.