Article content
Access to Flows Building is controlled through user permissions.
Managing access correctly helps protect your workflows, prevents accidental changes, and ensures only authorised users can publish live flows.
Understanding Access in Flows Building
Not every user needs the same level of access.
Permissions determine what a user can:
-
View
-
Edit
-
Publish
-
Manage
Access should be granted based on responsibility, not convenience.
Common Permission Levels
While permission names may vary, access typically falls into the following levels.
View Only
Users can:
-
View existing flows
-
Review configuration and logic
Users cannot make changes or publish flows.
Edit Access
Users can:
-
Create new flows
-
Edit existing flows
-
Save draft changes
Users cannot publish changes unless granted publishing rights.
Publish Access
Users can:
-
Publish flows
-
Make changes live
-
Unpublish active flows
This level should be restricted to trusted users.
Administrative Access
Administrators can:
-
Manage user access
-
Assign or remove permissions
-
Oversee all flows
Administrative access should be limited to a small number of users.
Best Practices for Managing Permissions
To keep Flows Building secure and stable:
-
Grant the lowest level of access required
-
Limit publishing access to experienced users
-
Review access regularly
-
Remove access when staff change roles or leave
-
Avoid shared accounts
Clear ownership reduces errors and accountability issues.
Why Publishing Access Matters
Publishing directly affects live behaviour.
Incorrect publishing can:
-
Trigger actions unexpectedly
-
Interrupt automated processes
-
Cause downstream system issues
Restricting publish access reduces risk.
Reviewing and Updating Access
You should review permissions when:
-
New team members join
-
Roles or responsibilities change
-
Issues occur due to unexpected changes
-
Regular security reviews are performed
Access reviews help maintain long-term stability.
Troubleshooting Permission Issues
If a user cannot perform an action:
-
Confirm their assigned permission level
-
Check whether publishing rights are required
-
Verify they are accessing the correct environment
If access still doesn’t behave as expected, support can help investigate.
When to Contact Support
Contact Pickle Support if:
-
A user cannot access Flows Building
-
Permissions appear incorrect
-
Publishing access is blocked unexpectedly
-
You need help assigning the correct access level
Providing the affected user name and flow details helps resolve issues faster.
Related Articles
-
Setting up your first flow
-
Editing, versioning & publishing flows
-
Common mistakes when building flows
-
Troubleshooting Flows Building issues