In the Studio platform, roles define the scope of actions for each user, with the goal of protecting flows, safeguarding sensitive information, and enabling secure and seamless collaboration.
Below, we explain what each role can do and when it is best to use them:
Read & Write Role
This role is intended for users who build, maintain, and operate flows on a daily basis.
What permissions does it have?
Can edit flows and make changes to nodes, configurations, and logic.
Can deploy flows to production, making changes effective.
Can lock flows.
Who is this role useful for?
Development teams.
People responsible for the maintenance and evolution of the Virtual Assistant.
Users who need full control over the flow lifecycle.
Read-Only Role
This role is designed for monitoring, analysis, and support without putting operations at risk.
What permissions does it have?
Can access the Studio instance.
Can view the debug panel, ideal for tracking and analysis.
If a flow is NOT locked:
Can open nodes.
Can make local changes.
Cannot deploy those changes to production.
What is this role useful for?
Code review.
Monitoring flow behavior.
Technical audits.
Supporting teams without operational risk.
Flow Locking
Flow locking is a key access control tool:
Prevents unwanted changes.
Protects sensitive information.
Restricts visibility of the internal flow content for unauthorized users.
When a flow is locked, read-only users will not be able to open nodes or access technical details, but they will still be able to monitor its execution from the debug panel.