Workflow Access Control

Workflow-level permissions introduce access control at the workflow level, as well as a new ‘User’ role into Go.

Workflow-level permissions allow you to configure permissions so that you can be precise about who has editing and viewing access to which workflow. We have also created the User role (alongside the Admin and Owner roles) which you must use in combination with Workflow-level permissions.

How does it work?

By clicking Share, you can then configure the default permissions for the workflow using the dropdown. Here, you can set the workflow as private ("Has no access") or public ("Can view" or "Can edit").

“Has no access” means that workflows are invisible to users who haven’t been expressly granted access (except for Admins and Owners, who have access to all workflows regardless of workflow-level permissions). Users will not be able to see nor access this workflow under any circumstance.

You are also able to assign specific users with their own permissions to an workflow. These user-level permissions will override the workflow's default permission setting – for instance, setting an workflow as "Has no access" by default, then inviting two specific team members with "Can edit" permissions, would mean that only the Workflow Owner and the two specific users will have access to this workflow.

We’ve also created a new role, the ‘User’ role. You must use the new User role in combination with workflow level permissions, since Admins and Owners are able to see all workflows, irrespective of agent level permissions.

Newly created workflows are by default public.


Did this page help you?