I think more importantly than permissions for individual workflows is the need for separation between workflow "enroll" capabilities and workflow "edit" capabilities.
Use case is: Representatives that work for our company may need to enroll a customer in a one-off campaign. But in order to allow that, I either have to create a dummy property that, when checked, enrolls them into that campaign (which means each campaign would need it's own property) OR I have to grant "God-Mode" to every rep who MAY need to enroll a customer into a marketing workflow for a one-off request for additional educational content.
Why is this a risk? Simple. I can NOT allow representives in the dozens (we have nearly 30 users soon to be transitioning into HubSpot Service Hub) to have access to not only enroll but ALSO go in and EDIT the workflows that our marketing and sales teams have spent nearly a year building. It's a massive risk to infrastructure.
My proposal is for the following: Workflow EDIT abilities are moved to the MARKETING tab in permissions. Workflow ENROLL abilities go under CRM permissions.
There is a toggle for creating and editing workflows. Just turn that off for your sales team. They can still enrol people in workflows with this turned off, can't they?
We definitely need the separation of authority for enrolling contacts in workflows and the access to edit workflows. We are very concerned to give staff access to edit workflows. One incorrect change or the wrong enrolment criteria and it could cause major embarassment or worse.
Super admin and developers can have access to create/edit workflows.
General support staff should only have access to enrol contacts to existing workflows. At present we use additional triggers via adding to a list or a custom field to trigger a workflow for a contact. Having access to see history might also be useful.
What will be in the workflows partitioning update? We're running Enterprise.
I agree! I work for a real estate firm. We would like for our agents to be able to create workflows for their email marketing. However, that would give them access to edit all of the company's workflows, which is a huge risk. It would be nice if there was a permission set feature limiting workflow access to something like "Owned Only" or "Created by agent."
This may be far fetched, but it would also be nice if the WF filters limited the agent to applying the WF only to their contacts and contacts with no owners, and not to contacts owned by other people.
@mgeorgieva -- we have the enterprise account and this feature does not appear to be rolled out. I can allow an agent to view or edit ALL workflows, but I cannot limit which workflows the agent can view/edit. Thanks!
Currently, it seems to allow edit access to specific workflows, one has to:
1. provide overall edit access to workflows in the permissions (user or permission set)
2. Then use the team level access in permissions to grant edit access by team
The challenge I see with this is that we are unable to:
1. Provide view access to all workflows
while also
2. Providing edit access to selected workflows
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.