How permissions in integrations and Catalytic interact

When your Catalytic processes integrate with your apps or services, the permissions in the app affect permissions in Catalytic. Catalytic will “inherit” the permissions from your app—when setting up permissions in Catalytic and your apps, take this inheritance into account.

In the following diagram, the outer most boxes affect all boxes inside of them. For example, the “Integration App” box affects all other levels inside of it. In other words, the permissions you set in your Integration App affect how permissions work through the integration and Catalytic.

screen readers look here
If something is more granular, it inherits the permissions from something less granular

For example, say you integrate with a file storage service “Orange Cart”.

  • In Orange Cart, you create a private folder, and a public folder—these are at the “Integration App” level.
  • In Orange Cart you have two users, an Admin and a Regular user—these are at the “Integration App User” level.
  • And when you create a connection to Orange Cart in Catalytic, you log in with an Orange Cart user—this is the “Catalytic Integration Connection”.

If you want to use Catalytic to automate work in Orange Cart, but you don’t want regular users accessing private data, you must set up permissions across all of these levels. Here’s an example of this:

screen readers look here

The lower levels (Catalytic Users and Workflows) inherit permissions from the higher levels (Integration App and App Users). This means when you create a connection in Catalytic using the Admin User account, anyone using that connection in Catalytic has access to everything the Admin User can access.

If you create a second connection and log in with Regular User, then that connection and anyone who uses it can only interact with regular data. Then in this way, when you set up integration permissions you can choose which Catalytic users can access the Admin or Regular data.