How is this for privacy reasons? This is a professional platform. It should be treated like emails, which a super user has access to all company related property. If the company is paying for the tool to do work, then it should allow the company to access all the related data.
It seems like the dev team is not interested in fixing this and we will be moving our business elsewhere.
In short, not giving access to all data handled by the platform that the company is paying for puts us in legal liability since we cannot control, if any, illicit use of software paid for and operated by our corporation.
This is a massive limitation.
I find it incoherent that as a Super Admin I can add myself to a Team and potentially delete that team with all related Projects. Still, I cannot see those projects or add myself to them unless I am being given admin rights by someone who is not a Super Admin.
This really happened as I was requested to clean up our Asana structure, reducing the amounts of Teams created and relocating Projects under those, meaning I had to move all projects and delete the team after that. Long story short, I ended up deleting projects by mistake as they were set up as private, and I had no visibility on that. Therefore I had to recover the Teams and related projects and reach out to everyone to ask to either relocate the projects, which delayed the process massively.
Now I have to restructure Goals and I am finding the same issue as I am not being given access to the Projects that should be used to fulfill the goals.
Finally being a Super Admin doesnât really simplify managing AsanaâŚ
Our team is new to Asana so I often need to add data points â even things as simple as updating project dates â so I was surprised at my lack of access to such everyday tasks, especially as a Super Admin.
For peace of mind I explored ways to âfixâ this in case changes are needed in a bind.
The only thing that has worked â 100% â was to completely duplicate projects and to be sure that every box is checked for the data transfer. This allowed me to keep all of the ownership levels the same, but basically added me as a co-owner. It also seems to keep all project assignments, collaborators, and dates the same as they were. But of course, the original projects then need to be deleted, which is both risky and unfortunate.
All said, this may only work for us because our projects are not terribly complex. Iâm just happy we have some sort of solution. Regardless, Iâm in agreement with most here that the limitations on Super Admins are quite surprising.
I just want to point out to you and others that itâs important to be very careful if you check the box for Task details > Associated projects. That can get confusing because the result of duplicating the project would, if any tasks are multi-homed (assigned to more than than one project), affect other projects besides the one youâve duplicated.
For me/us, itâs just a work around if ever needed.
Related to your thoughts, I agree. And my gut (also) says if any other projects rely on a project that needs to be duplicated, confusion may insue.
Even today, when duplicating projects, itâs important to remember to delete the original to avoid all tasks being duplicated in the calendars of all involved.
Again though, the limitations seem to be the issue ⌠especially considering you canât become a Super Admin without accessing the company server, etc.
Getting to the root of the âwhy notâ is still the issue. Itâs definitely not a privacy issue when dealing with a company server.
And this is another place to be careful (when deleting the old project).
When you delete a project, it will only delete those tasks that are neither a) assigned, nor b) multi-homed. Thereâs a warning to this effect but many disregard it and then wonder why not all tasks were deleted after requesting the project deletion.
This pain point just came up again. We have a project with only one Project Admin and that left the company with no way to assign a new project admin. I am working with Asana support to make this change on the back end. (Request #1053766)
Honestly, is there an official roadmap/statement from Asana regarding this? I just went through the super admin verification process just to find out that even the super admin cannot change/edit projects. I think itâs obvious that this is not any extravagant feature request but a basic one users a seeking to have.
Yet again, I google how to do something pretty basic in Asana to find a long thread of angry customers and forum leaders responding with âits by designâ.
Yes - this is such basic functionality that every other tool I use. There just must be the option to give someone complete editing power. What if someone created something defamatory as they left the company and no-one else could access to edit or remove it?
Welcome to the forum. Agreed 100% that this level of admin control is necessary. That said, if you are on an Enterprise or Enterprise+ plan, you can create a service account that gives you access to all data within your organization. This is the workaround Iâve been using to accomplish this for now (I basically pull a list of all projects in the organization, then add myself as the owner of anything I need to alter/delete). It is not a great solution, but it does work in a pinch.
Thanks @Stephen_Li , appreciate the advice. We are using an Advanced account. Frankly the Enterprise version doesnât provide enough to warrant it. Donât get me started on the inability to easily incorporate subtasks into workflow which I thought Enterprise would give me!
@Martin.Conroy - Understood, youâre probably already aware but subtasks are supported in rules now (although thatâs also true at the Advanced tier, I believe, so Iâm assuming that doesnât offer you what you need).
I totally agree. I am locked out of so many projects that Iâm supposed to be managing. Now we donât allow anyone to create projects except for a couple admins. Isnât the role of the admin to be able to access everything. This has to change asap. We are considering moving to another platform.
+100 - this is such a massive limitation to Asana I am pretty shocked. As an owner of the business and the main stakeholder for Asana, we are unable to manage the structure and setup of our project management tool. Interns whoâve never used Asana before have greater project permissions than Super Admins- how does that make sense?
We are evaluating leaving Asana for this plus several other limitations.
Hello @Stephen_Li , @lpb , @Danielle-GenD, @Ka_Nishiyama . Judging by the amount of responses this issue is still not fixed. Saying its not an issue and therefore its not a problem is cognitive dissonance.
Upgrading to Enterprise and submitting tickets is not a fix.
Submitting tickets is not a fix.
This was a feature until about a year ago when Asana made a change in permissions.
Myself and the 5 Ambassadors, 7 Users claiming that this is a critical feature and would push us tot leave the platform should be an indicator that at some point Asana needs to respond accordingly. The company is paying for the product, and therefore owns the data of the users paid for by the company, this is unacceptable.
@Henry_Remington we are not saying it is ânot a problemâ but we are trying to offer assistance - forum leaders are not Asana employees or developers we are ambassadors like yourself in a way but just have committed to helping on the forum more than others.
@Danielle-GenD understood. Thank you for the clarification. As a third party distributor/seller of this platform. How can we as a community express to Asana to make this a priority. What method of communication would you suggest?
I would like to express my support for Super Admins to be able to manage projects as well. Aside from the annoyance of not being able to delete or archive projects for former staff without opening up a ticket with Asana, this type of admin cleanup work may not be a great use of the current staff project ownerâs time. We use Asana as a productivity tool, so it really shouldnât seem like a chore. And if I have to ask, ask again, and remind staff to archive their own projects, then itâs just wasting multiple peopleâs time.
@Hillary_Kantmann thank you for your support on this. Hopefully this thread gets some visibility and the changes are reverted. This has been such a hassle. We just removed a user from our platform and found that there are a number of private projects that they created, now we have to create a ticket to remove them. I cannot imagine that this is a efficient way to run a SAS platform.
