Skip to main content
The Integration Management page gives Org Admins centralized control over which integration steps are available to users across their organization. From a single page, you can enable, restrict, or disable any integration that makes network calls—including source steps, destination steps, AI steps, and API-based steps like Enrich with API.
The Integration Management page is available on the Advanced and Enterprise plans. If you’d like to enable this feature and do not currently have access, please reach out to your Account Manager or contact help@parabola.io.

​
Who can access the Integration Management page?

Only Org Admins can view and modify integration settings. The page is accessible from the left-hand sidebar on the Flows page, labeled “Integrations”.

​
Understanding integration statuses

Each integration on the management page can be set to one of three statuses:

​
Enabled

This is the default status for all integrations. When an integration is enabled, any user in your organization can add the step to a flow, configure it, and run it as expected.

​
Restricted

When an integration is set to “Restricted,” the step can still be added to flows and will continue to run on schedule - but only the user who owns the credentials associated with the step can edit its step configuration. If a teammate opens a shared flow containing a restricted step, they will see a read-only view of that step. If they have edit access to the flow, they can switch to their own credentials (if they have existing credentials for that integration) or create new ones in order to edit the step. This is useful when you want flows to keep running but need to lock down who can modify sensitive integration configurations.

​
Disabled

When an integration is disabled, it is fully restricted across the organization:
  • The step remains visible in the step bar but cannot be dragged onto the canvas. Users will see disabled styling and a message directing them to contact their Org Admin.
  • Any existing flows that contain a disabled step will fail at that step during runs. The run history will indicate that the step failed because it has been disabled by an admin.
  • The AI assistant will not suggest or insert disabled steps when helping users build flows.

​
How to change an integration’s status

  1. Navigate to the Integration Management page from the left-hand sidebar.
  2. Find the integration you want to update. You can scroll through the list or use the search functionality.
  3. Click the status dropdown next to the integration name.
  4. Select your desired status: Enabled, Restricted, or Disabled.
Your change takes effect immediately. If you are disabling an integration that is currently used in existing flows, you will see a warning letting you know that active flows may be impacted.

​
Setting a default status for new integrations

By default, any new integrations that Parabola releases will be set to Enabled for your organization. If your organization prefers a stricter posture, you can change this default so that new integrations launch as Disabled instead. To change this setting, look for the default behavior option at the top of the Integration Management page. Once set to “Disabled,” any newly released integrations will require an Org Admin to manually enable them before users can access them.

​
FAQs

​
Does restricting an integration affect scheduled flow runs?

No. Setting an integration to “Restricted to credential owner” does not impact any flow runs. Flows will continue to run on schedule as expected. The restriction only limits who can edit the step’s configuration.

​
Does disabling an integration affect scheduled flow runs?

Yes. Any step in a flow that has been disabled will fail during a run. The run history will show that the failure was caused by the integration being disabled by an admin.

​
What types of steps appear on the Integration Management page?

The page includes all third party integrations. This covers source steps (like Pull from Google Sheets), destination steps (like Send to Snowflake), AI steps, and Enrich with API.
Last modified on March 31, 2026