Skip to main content

Ideas

Filter by idea status

10000+ Ideas

RAshley
RAshleyLevel 3

View access should not grant Edit access on lower objectsNew

We recently discovered an "intended behavior" that smells an awful lot like a bug to me.Our intent is for users to be able to add issues to tasks assigned to them, but not add issues to projects themselves. We set up permissions in such a way as to provide this, but our users are still able to add issues to the projects.We entered a ticket, and after three weeks of research Adobe provided this response:"Our engineers were able to find that when a user has View access to a higher object (such as a program or portfolio), the system is designed to allow those users to enter in issues for projects and tasks. This design has been implemented for quite some time, but our documentation didn't reflect the described behavior. I have included the updated documentation below.User <redacted> has View access to the portfolio of the project where he can add issues. The system will take those assigned rights (on the portfolio level) and it will not be overridden by the selection on the project level (marking for the user to not be able to add issues). In order to prohibit users from adding issues to projects or tasks, you will need to remove view access on the portfolio level."So giving users VIEW access to a high-level object also grants them certain EDIT permissions on lower objects. This is a) not intuitive in any way and b) poor design. There is currently no way to achieve our goal without removing view access to portfolios (which we want them to have). This "link" needs to be broken. If we want a group of users to have edit on an object type then we'll use the existing permissions structure to grant them that access.  

Selliers
SelliersLevel 4

Administration and maintenance of TagsAccepted

We are experience that maintenance of Tags is hard do to access rights, especially deleting Tags. It must be easier to change the name and/or to delete a Tag that is not wanted or not just any more. It the Tag feature shall work and be trusted by the users the Tag must be spelled right be generic and have some sort of structure. This is work that is always going on - and the need of change and maintenance will always be there. We see misspelled words, not generic enough  and the list includes many tests. This is hard to change and make the tool full of "bad data" - and the user experience will drop over time.  During the development of AJO there has come better features regarding deleting audiences. When deleting a audience it will be checked it this audience is connected to another audience and/or a journey. If so you get a error message and info about that connections there is regarding the audience you want to delete. We see the need of the same mindset here regarding Tags. All user should be able to change or delete a Tag, but when deleting there should be a check if the Tags is been used somewhere before it is deleted. Changing name should be able as is since this is dynamic data. Is should be able to delete Tags without disable the Tag first. Use of Tags and the need of using Tags is growing along with the extend use of AJO. And if Tags should be used Tags must also be able to be maintained fast and easy, like other features in the tool. With the possibility to also have a folder stricture it would even be more easy and more relevant to use.  Today we can create but in a real working environment we cant change and maintain the Tags easy - and will therefor not been used. I see that a good Tag strategy can help us working better with audiences etc where the Tags is part of how we find and target customer. 

The Email Performance Report IS INACCURATENew

I discovered an interesting issue with the Email Performance Report that I will assume less than 10% of Marketo users are aware of.   This issue is detailed below in a note at the bottom of this help doc:  "Multiple sends from the same campaign to the same person are counted only once." Email Performance Report Help Doc   So does that issue mean?  For those of us who use tokens all across our Marketo instances and use them particularly to swap in/out content via those tokens for scalability and efficiency, (maybe in an automated nurture) this is a BIG problem.    When a person is sent an email from the same campaign multiple times over any timeframe, the Email Performance Report only records a single email send    Example Notice the three email sends below.  Two of the sends are via the same campaigns.     The below report only displays 2 emails were sent - and this is our issue   Solution To me, every email send in the activity log should appear on this report.  I am unsure what the use case is for the current methodology, where email sends from the same campaign to the same person are grouped together.  I would think most customers would just want to report on all email sends and what the outcome of those sends were (bounce,open,click) over the course of time.  Two versions of the Email Performance Report would also suffice.    For now - it looks like the only solution to this is via API exports of your email activity.      For fun, feel free to include in your comments if you were aware of this!   Best, Mike