Sender of automated emails
Hi,
I want to send emails triggered by moving one deal to a specific stage. No problem with one person.
If I have this automisation triggered by everybody else as well, the email is sent with MY email address. So if I want my team to send the email with their own email address, they have to recreate the automisation.
It would make very much sense, if I could find this option in the automisation (I could live with a permission request for all users - I understand that I can not create automisations which allow me to send emails with other email addresses). But at least it should be possible to duplicate my workflow.
Comments
-
Hi @Bernd Auer !
I did some investigation on my end and it seems you're trying to duplicate an automation that was created by another user - that's why it won't let you (check if you're in the "created by others" tab).
You can only duplicate automations created by yourself (in the "created by me" section).
That being said, I can absolutely see how it would be useful and time-saving. We've made sure your feedback reaches the team. Let's see what the future brings!
0 -
Sam Karim said:
Definitely agree. I would rather have some of these email being sent from my support inbox and not my own even though I created the automation.
Hi @Sam Karim ! Automations will send the email from whatever email account its creator has synced with Pipedrive. I'm guessing in your case, you've synced your own individual work email account with Pipedrive but would like the automation to send the emails from another general email account, like "support@companyname.com" , is that correct?
0 -
Sam Karim said:
Definitely agree. I would rather have some of these email being sent from my support inbox and not my own even though I created the automation.
Thank you for clarifying. I'm afraid that first possibility is not in our plans at the moment, but I sent the team your feedback.
To send from the deal owner, each owner will have to replicate the automation in their own account, and ideally I'd say it's best that they set it to be "Triggered by me only".
0 -
Changing Sender Email
Hello,
I am looking to change the sender email.
I am sending many email on behalf of the founder and I need to be able to change the sender email.
I don't want the receiver to see ME as the sender, but the FOUNDER as the sender.
How can I do this from my login. I don't want to send from Founder's login.
Please advise.
0 -
Amanda Torabi said:
Changing Sender Email
Hello,
I am looking to change the sender email.
I am sending many email on behalf of the founder and I need to be able to change the sender email.
I don't want the receiver to see ME as the sender, but the FOUNDER as the sender.
How can I do this from my login. I don't want to send from Founder's login.
Please advise.
Hi @Amanda Torabi ! Please see the answer to your question in this other thread.
0 -
Hi, you can now create duplicates of existing automations and assign those duplicates to other users! For more details on how it works, please have a look at our knowledge base here.
0 -
Hi @Manuel Oliveira !
the automations can only be transferred to admins. Could you explain why that is?From my perspective, this doesn’t really make sense— in most cases you want to transfer them to regular users. So having to switch someone to admin, transfer the automation, and then switch their rights back adds unnecessary extra work.
Is there a specific reason for this limitation?
0 -
By the way: My original question comes from 2020 :) I am very happy that you and your colleagues listened in the meantime :)
1 -
Hi @Bernd Auer I double-checked your question with the team. It was designed that way as a security step, since global admins are meant to be responsible for company settings and changes that may affect other users, such as automations.
So in this case, as the global admin receives an automation from a regular user, they should confirm that everything checks out with all automation steps, and then forward the automation to the final recipient.0 -
But the recepient has to be "account settings level user" = Superadmin!
It makes perfectly sense that just an admin is able to transfer automations. But if you open the "transfer ownership" button you will see this:
And you don't want all your colleagues being able to do these things also if it is temporarely ;-)
0 -
Hi @Bernd Auer, hope you're doing well!
Thanks for pointing this out. The current behaviour is that you can transfer automations to users with global admin permissions - they do not need account settings access. We'll make sure that info notification is updated with the correct content, but in the meantime you can transfer away!
Jess0 -
Hello @Bernd Auer,
Also, I want to mention the possibility of sharing automations with other users so that you do not need to duplicate them and change owners in the first place.
With this feature, you can add multiple users to an automation. Once each user has activated the automation, it will be triggered from the respective accounts. The action, like sending an email, will be done from each account as opposed to the automation owner as long as all users have their email synced. You can learn more about it here.
We hope this helps!
0 -
Hi @Jess Stacey,
Are you sure? We tested it recently. I wouldn’t bet all my money on it, but I think it didn’t work.
It should be possible to transfer without admin rights. From my point of view, the key restriction (or permission) is whether Global Regular Users have the right to create automations:
A Global Admin is able to export data, see all items, etc. So, things that are very sensitive — and if you forget to withdraw the Global Admin rights, you can get into serious trouble.
Hi @Tony Xavier, Thanks for pointing this out! It’s new to me that it works now. My latest knowledge was that I wasn’t able to create a workflow that triggers an email from another email account — which would make perfect sense from a security point of view.But there are two new features I just discovered while testing:
You can switch the “from” email address:
And I am not allowed to activate the workflow in my colleagues account:
But it’s still a security issue. I could change a template, and the "approved" workflow from someone else could send emails I didn’t approve. I’m sure there are many people who wouldn’t want to allow just any content to be sent from their email address. Therefore, I can imagine that these people would prefer to be the actual owner of the workflow and use their own templates. But who are not able to create a difficult workflow.
And here’s a use case that requires ownership: I don’t think I can trigger an email that’s sent from someone else’s account, right? The use case is this: The sales reps are at a fair, collecting leads. The back office wants to research these leads and send emails from the deal owner’s address on the same day (speed counts), such as: "Hi, it was nice to meet you today! Please find my booking link attached and my contact details in the signature."
But these are edge cases. If you know how to handle it, you can achieve great things! But there is still a risk… Good for us as Pipedrive partners because our common customers will ask us just to be sure :-)0
