Field filters for refining access to credentials

You can restrict access to the credentials that are used to create integrations and workflows or any workflow that includes a block, such as an API block, that requires the user to select credentials.

About adding filters

For example, you can add a filter to restrict access to the user who created it. The user who logs in can only use the credentials that they created. 

Created by Equals Current user

You can restrict access to one or more types of authorization. The user who logs in can only use credentials that use an API key to authenticate.

Note
Although the user can still add basic authorization and signed requests, these credentials will be unavailable to the user. That is, they won’t be able to use these credentials to authenticate.

Authorization type Equals Static API key

You can restrict access to the owner of the credentials. The user who logs in can only use the credentials that they own. That is, that they are named as the owner of the credentials.

Owner Equals Current user

Or to specific owners:

Owner Equals Static FirstName([e-mail])
Owner Equals Static FirstName([e-mail]) 

Note
If the field filter is Owner Equals Current user, the user can edit the credentials, such as  changing the name of the owner. In such cases, when the user saves the credentials, the  credentials will be removed from the list of credentials available to the logged in user.

Procedure

1. Click Configuration > Security > Roles.
2. Click a role.
3. Click PERMISSIONS.
4. Expand the Configuration section.
5. Click ADD FILTER.
6. Make your changes.
7. Click SAVE.

Related articles

See Using field filters to refine access to roles overview

See Using field filters to refine access to roles