Skip to main content

Solutions

A solution is a workspace and security boundary inside an organization. It groups HubItems, members/teams, connectors, and API keys for one business domain or product.

Example organization structure:

Example Financial Services (Organization)
  Lending (Solution)
  Customer Onboarding (Solution)
  Collections (Solution)

Use separate solutions when assets have distinct ownership, access, or integration credentials. Do not create a separate solution merely for every folder or version.

Create and manage solutions​

Organization administrators work from Organization → Solutions. Enter a clear name and the settings offered by the form. After creation, assign members or teams and select it from the application header.

An active organization member does not automatically have access to every solution. Solution access must be assigned through roles and policies.

Solution Info​

Solution Info displays identity, status, and usage summaries. Use it to confirm that you are working in the intended workspace before creating keys, connectors, or HubItems. Similar names across test/business domains can otherwise cause configuration in the wrong solution.

Solution Dashboard​

The Dashboard summarizes assets and activity within the selected solution. Use it for navigation and trend awareness, then open the specific HubItem, deployment, execution, or API-key view for evidence.

Solution Access​

Assign users and teams the role appropriate to their responsibility. Common patterns include:

  • administrators manage access, connectors, and API keys;
  • editors create and version HubItems;
  • readers inspect definitions without changing them;
  • testers run deployed items and manage tests as permitted.

Custom roles and policies can provide finer separation. See Access control.

API Keys​

API keys are created for the selected solution and environment. Their creation form includes optional name, permission preset, resource permissions for Restricted keys, and expiration.

The full secret is shown once. Later views show prefix, status, dates, rate limits, usage, and activity. Use one key per consumer and environment so it can be rotated or revoked without affecting unrelated services.

Example naming:

Loan Origination - Test
Loan Origination - Production
Nightly Regression Runner - Test

Do not reuse an OData reporting key for execution.

Connectors​

Connectors belong to the solution but have environment-specific configurations. A Salesforce connector named Core Salesforce can therefore use sandbox credentials in Test and production credentials in Production. Test each configuration separately.

Connector permission does not imply permission in the external system. The external account or connected application still needs appropriate least-privilege access.

Share HubItems across solutions​

The Hub item menu can share/copy an asset to another solution you can access. After sharing:

  1. Review its name and description for the destination context.
  2. Confirm referenced Data Models and HubItems are available.
  3. Reconfigure connectors and Global Variables.
  4. Recreate saved payloads/tests where needed.
  5. Assign destination-solution access.
  6. Create and deploy destination versions through its normal process.

Sharing does not transfer source-solution permissions or environment secrets.

Retire a solution safely​

Before deactivation or deletion, identify deployed HubItems, active API keys, event subscriptions, connectors, external consumers, pending deployments, execution-retention requirements, and shared assets. Revoke credentials and coordinate consumers before removing access.