Functionality to allow multiple domains to use newsletters
Hi Marcus,
I think the Newsletter studio is a great product. One of our requirements we are looking at right now is to allow multiple users from different domains to create their own newsletters. So for example if we have domain1, domain2, domain3, domain4, etc
We would like domain1_admin user to be able to send out newsletters and domain2_admin to send out their own but each domain is not able to see each others newsletters. We are using Umbraco to host 10+ domains on one instance.
There is no limitations on user/domain bases today every user on every domain can se the Newsletters. If this is something that many users would like to see implemented will concider that for futher releases.
Looks like a great product with documentation and intros that are very professional.
Similar to James, I'm looking at muItiple users of a system from different organisations (though on the same domain) sending out newsletters and managing mailing lists independently. I dont want users to be able to see other users mailing lists or their newsletters though. Is this something that may be possible with your system?
I'm sorry to say that at the moment this is not possible. The feature is not currently in the pipeline but we do have this request in the backlog. I can't tell you when or if we will implement it.
I have seen some other requests like this and I'm thinking of how to implement it. I have one idea where every newsletter will be bound to its creator. That means that user X would only see it's own letters and user Y would only see its own letters but they would not be able to see each others.
That would be nice but something a little bit more general would be nicer :).
We need to separate newsletters, that's for sure, but the mailing lists also need to be visible only to their owners... Furthermore I'm not sure whether showing everyone only newsletters/mailing lists they created would be enough. Imagine a situation when newsletter owner gets sick and admin has to take over his account in order to access his newsletters. Some solution with more users linked to newsletters/mailing lists would probably be better... Pavel
Just to join the discussion I would also like to request this functionality. I currently have 5 sites running in a single Umbraco instance and I would like to be able to offer each of the content managers for each site to be able to run their own newsletter campaigns.
With the current Newsletter studio there doesn't seem to be any way of doing this? I'm happy to supply any information that may help you in developing this functionality.
I think the creator seeing his own newsletters / mailing lists etc would probably be enough for what I want - obviously as an admin i'd be setting this all up for the creator so i'm presuming that i'd have the ability to set the creator to be a specific user within the system? If I have a different template for each site I would only want the creator to also only see the template assigned to him.
In an ideal world then I would like to have multiple instances of the Newsletter node for each site which can be configured seperately each time and then I can limit access into each area - I currently do this with uBlogsy in multiple sites as in the image below, the News folder can be added into sites and this top level node also contains the general settings for uBlogsy. I obviously have no idea how viable this is as a solution...
I can then limit through the standard Umbraco security who can see what nodes etc..
We have the same requirement. We manage two umbraco installionns. One with 10+ sites and another one with 2. It is imperative that they only see thier domains content (letters, lists, etc).
Using the Send Out Data Type with multiple domains also doesn't really work.
I had to give up trying to use Umbraco in the end and set the client up in mail chimp. Unless you are sending thousands and thousands of newsletters or have > 2000 subscribers it's free and easy to setup.
I think it would probably be fine for multiple domains if they are all the same client. I believe the issue I had was the segregation of the admin parts of the system for different clients (domains) and also the segregation of the templates for each of the clients (domains).
It looked like a nice little package and if I ever set up a single domain that requires a large amount of newsletters sending or has a large subscriber base I would be downloading the package and installing straight away :)
Functionality to allow multiple domains to use newsletters
Hi Marcus,
I think the Newsletter studio is a great product. One of our requirements we are looking at right now is to allow multiple users from different domains to create their own newsletters. So for example if we have domain1, domain2, domain3, domain4, etc
We would like domain1_admin user to be able to send out newsletters and domain2_admin to send out their own but each domain is not able to see each others newsletters. We are using Umbraco to host 10+ domains on one instance.
Thanks,
James
Hi James!
Thank you very much!
There is no limitations on user/domain bases today every user on every domain can se the Newsletters. If this is something that many users would like to see implemented will concider that for futher releases.
// M
Hi Markus,
Looks like a great product with documentation and intros that are very professional.
Similar to James, I'm looking at muItiple users of a system from different organisations (though on the same domain) sending out newsletters and managing mailing lists independently. I dont want users to be able to see other users mailing lists or their newsletters though. Is this something that may be possible with your system?
Regards,
Adrian
Hi Adrian!
Thank you for looking at the package!
I'm sorry to say that at the moment this is not possible. The feature is not currently in the pipeline but we do have this request in the backlog. I can't tell you when or if we will implement it.
// Markus
Hi Markus,
here another one who would find this feature useful :-). Still no chance of getting it in some future version?
Thanks,
Pavel
I have seen some other requests like this and I'm thinking of how to implement it. I have one idea where every newsletter will be bound to its creator. That means that user X would only see it's own letters and user Y would only see its own letters but they would not be able to see each others.
Would this suite you?
That would be nice but something a little bit more general would be nicer :).
We need to separate newsletters, that's for sure, but the mailing lists also need to be visible only to their owners... Furthermore I'm not sure whether showing everyone only newsletters/mailing lists they created would be enough. Imagine a situation when newsletter owner gets sick and admin has to take over his account in order to access his newsletters. Some solution with more users linked to newsletters/mailing lists would probably be better...
Pavel
As you say internal mailing lists (Newsletter Studio lists, not from custom providers) would be applayed as well.
About the admin situation admins could probablt have access to see everything.
How would you like it to be? Describe your setup...
Hi Markus,
Just to join the discussion I would also like to request this functionality. I currently have 5 sites running in a single Umbraco instance and I would like to be able to offer each of the content managers for each site to be able to run their own newsletter campaigns.
With the current Newsletter studio there doesn't seem to be any way of doing this? I'm happy to supply any information that may help you in developing this functionality.
Cheers,
Mark.
Hi Mark!
I see, would it be OK with you that the creator only see's its own emails? Or is there any group policy stuff you are looking for?
Hi Markus,
I think the creator seeing his own newsletters / mailing lists etc would probably be enough for what I want - obviously as an admin i'd be setting this all up for the creator so i'm presuming that i'd have the ability to set the creator to be a specific user within the system? If I have a different template for each site I would only want the creator to also only see the template assigned to him.
In an ideal world then I would like to have multiple instances of the Newsletter node for each site which can be configured seperately each time and then I can limit access into each area - I currently do this with uBlogsy in multiple sites as in the image below, the News folder can be added into sites and this top level node also contains the general settings for uBlogsy. I obviously have no idea how viable this is as a solution...
I can then limit through the standard Umbraco security who can see what nodes etc..
Cheers,
Mark..
We have the same requirement. We manage two umbraco installionns. One with 10+ sites and another one with 2. It is imperative that they only see thier domains content (letters, lists, etc).
Hi!
I see! Its on the todo-list but I have not started the development and can't really say when that will happen.
Until then your best solution is to put the newsletters in the content section with the Newsletter Studio Send Out Data Type.
http://www.youtube.com/watch?v=9fRSGgMCYaM
Cheers!
Using the Send Out Data Type with multiple domains also doesn't really work.
I had to give up trying to use Umbraco in the end and set the client up in mail chimp. Unless you are sending thousands and thousands of newsletters or have > 2000 subscribers it's free and easy to setup.
Hi Mark!
I would for sure work with multiple domains, I have serval customers that uses this approach. I see Mail Chimp is great as well!
Cheers!
Markus,
I think it would probably be fine for multiple domains if they are all the same client. I believe the issue I had was the segregation of the admin parts of the system for different clients (domains) and also the segregation of the templates for each of the clients (domains).
It looked like a nice little package and if I ever set up a single domain that requires a large amount of newsletters sending or has a large subscriber base I would be downloading the package and installing straight away :)
Cheers,
Mark.
is working on a reply...