Editing control working with email content and Journeys

[#1]

We have in several occasions experienced that created content in a email templates disappears - and needs to be redone. This is extremely annoying and time consuming for the content producers. There are several theories what this happens, some from you at Adobe also. Like: there is several tabs open with the same template open, or there are several users working on the same Journey and/or email at the same time. 

To avoid this kind of situations where content actually disappears, we would like to have a features that lock the content to the user that has it open - and changes can not be done to the content by other than one user at the time. When open and try to change content when it is open already a warning message should appear and inform that this template/journey is blocked be user xxxxx. You can take over the editing role by overtaking the role. 

What we would like is basically a build in control feature that makes it possible for just one user to make changes at the same time to emails and Journeys.   

[#2]

@Selliers 

There is a feature released last year called content locking. Not sure if it's exactly what you're looking for your use case but you can give a try

[#3]

Hi

Yes I am aware of this locking feature, but it not exactly what I was thinking of. In the main menu you have all your fragment listet, and from here you can access the fragments. We are looking for a way that the fragments cant be changed from here, put to Draft my a mistake etc. Now the list is open for everyone. When you use the fragments to create master templates for different parts of a organization, it is dangerous of some of this fragments that is been used as a base in templates is toggled with so the templates and Journeys stop working. Therefor we see the need for some kind of access control over who can edit this and not. We are exploring if Labels can solve this, something we think. But there is again a huge hassle to be able to put a Label on a user group, need to be done from Application owner etc. So this is not straight forward eighter.