Manage Configs
Being able to edit a config depends on several factors, such as whether or not it is mapped to an integration or flow, if it is mapped to more than one integration, if the flow is published, or if you have the correct permissions.
See the following sections for details on the specific fields you can edit and changes you can make to configs.
Manage integration configs
You can always add a new integration config.
You can delete an integration config only if it is unmapped.
For all integration configs—those mapped and unmapped to flow configs—you can edit the fields as outlined in the table below.
Edit Permissions for Integration Configs
Manage flow configs that are mapped to integration configs
You can add a new flow config, but you can publish the flow only if all active flow registrations have all required config values filled out.
You can delete a flow config only if it is not used in the published flow definition. Before deleting, you must remove any config mappings.
You can’t make edits from the flow builder for flow configs mapped to an integration config. Edits are restricted because changes to flow configs that have more than one mapping would cause issues for all other mappings.
Edit Permissions for Mapped Flow Configs
Manage flow configs not associated with an integration
You can always create a new flow config if the flow is not used by an integration.
You can delete a flow config only if it is not used in the published flow definition.
For flows unassociated with an integration, you can edit fields as outlined in the table below.
Edit Permissions for Flow Configs Not Associated with an Integration
