Skip to main content
The operational side of being an admin isn’t glamorous, but it matters. A well-organized account — with the right people having the right access, flows in sensible folders, and production workflows monitored for failures — is the difference between a team that trusts Parabola and one that’s constantly firefighting.

​
Adding team members

1
Navigate to the Team page and click + Add teammate.
2
Fill in their name and email, then assign a permission level: Admin, Editor, or Viewer.
3
Click Add teammate. They’ll receive an email with instructions for creating their account.
Adding a new user does not automatically give them access to all flows on your account — only flows in shared Team folders. To grant access to a specific flow, use the sharing modal within that flow.
You can also add a new team member directly from within a flow by clicking Share → Invite someone new to your team at the bottom of the sharing window.

​
Removing team members and offboarding

When someone leaves your organization, removing them from the Team page is only half the job. Any flows that rely on their integration credentials will break as soon as their account is gone.

​
Before you remove the user

  1. Identify who will take over their flows — confirm the new owner exists in Parabola and has access to the external systems those flows connect to
  2. Find flows with authenticated steps — look for any flows that use credentials belonging to the departing user (Google Drive, Shopify, etc.). These need to be transferred before you remove the account

​
Transferring authenticated steps

1
Open the flow containing the authenticated step.
2
Click the step and open the account dropdown.
3
Click Edit Accounts, find the credential (the 🔒 icon indicates a private account), and click Sharing settings.
4
Share the credential with the new owner and grant them Edit access.
5
The new owner opens the same step, finds the shared credential, clicks the three-dot menu, and selects Reconnect Account to re-authenticate with their own credentials.

​
Removing the user

1
Navigate to the Team page and find the member you want to remove.
2
Click the gear icon next to their name, then click the trash icon in the window that appears.
3
You’ll be prompted to select a new owner for the departing user’s flows.
When you remove a user, their owned flows transfer to the admin who removed them by default. To ensure ownership goes to a specific person, complete the transfer through the Remove User flow (step 3 above) rather than just deleting the account. Transferring ownership doesn’t change anyone else’s existing view or edit permissions on those flows.
Schedule offboarding before the employee’s last day — ideally with enough time to re-authenticate affected flows and verify they’re running correctly under the new owner’s credentials.

​
Pre-offboarding checklist

  • Confirm new flow owner exists in Parabola and has access to relevant external systems
  • Share and re-authenticate all integration credentials used in affected flows
  • Remove user via Team page and assign new owner
  • Run and verify all affected flows
  • Remove the offboarded user from your identity provider (if using SSO)

​
My flows vs. Team flows

SpaceWhat’s in itDefault visibility
My flowsFlows you created but haven’t shared broadly, plus flows others shared with you directlyPrivate
Team flowsFlows accessible to your entire organizationVisible to everyone
When a flow is moved to Team flows, your entire organization automatically receives viewer access. You can update specific individuals to editor access at any time after that.

​
Using folders

Team flows can be organized into folders. Anyone on your team can create a folder, and all folders are visible to the entire team.

​
Creating a folder

Click New Folder on the Team flows page, enter a name, and save. You or your teammates can update the name at any time from the folder’s overflow menu.

​
Organizing with sub-folders

You can create sub-folders up to three levels deep. For example:
Operations → Vendor Management → Weekly Reports
Access your complete folder structure from the left sidebar or from within the Team flows page.

​
Deleting a folder

Deleting a folder also deletes all of its contents. This cannot be undone.
A folder can only be deleted by the folder creator (and only if they have editor access to all flows within it). To delete, navigate to the parent folder and select Delete from the overflow menu.

​
Moving flows

Flows can be moved between My flows and Team flows at any time. Select Move from the flow’s overflow menu and choose the destination.
Only flow editors can move flows.
Parabola will warn you if the move will change who has access:
  • Moving into Team flows — automatically gives your entire organization viewer access
  • Moving out of Team flows — removes organization-wide access; users with direct sharing permissions retain their individual access

​
Managing changes to production flows

Once a flow has been published and is running in production, there are two ways to update it:
  • Edit the live flow directly — fine for small changes like renaming a column or adjusting a filter
  • Create a draft — recommended for any larger change that could affect how the flow runs
Only one draft can exist at a time. When you’re ready to deploy the changes, publish the draft and it immediately replaces the live version.
Use drafts for any change that touches data sources, outputs, or step logic on a flow that’s running automatically and processing critical data. Editing the live flow while it could be triggered mid-run can cause unexpected behavior.

​
Keeping your flows healthy

Automated flows fail sometimes — a credential expires, a source API changes, or a file arrives in an unexpected format. The goal is to make sure those failures get caught quickly, not three weeks later when someone notices the data is stale.

​
Failure notifications

By default, anyone with edit permissions on a flow receives an email when it fails or pauses. Users can configure their notification preferences per flow:
  • Email only on failure or pause (default)
  • Email on every run
  • Never email
This is a per-user setting managed in each flow’s settings panel. As an admin, make sure the right people have edit access on your team’s critical flows — otherwise they won’t receive failure alerts.

​
Auto-pause after consecutive failures

By default, scheduled flows automatically pause after 10 consecutive failures. This prevents a broken flow from silently running (and consuming credits) in a failed state indefinitely. If a scheduled flow has paused, check the flow’s Schedules/Triggers panel to see its status and resume it once the underlying issue is fixed. You can configure this behavior in flow settings — but in most cases, leaving auto-pause enabled is the right call.
If you get a failure notification and aren’t sure where the flow broke, open the flow’s Run History panel. It shows successful and failed runs, which step failed, and what the error was.

Building challenge

Take a few minutes to audit the health of your team’s most important flows.
  • Which flows are running on a schedule or triggered automatically?
  • Do the right people have edit access on those flows so they’ll receive failure notifications?
  • Are there any flows that have paused due to consecutive failures?
Last modified on March 5, 2026