There’s a workaround for when an employee is terminated until Asana wakes up and realizes the person who pays for the account should full access to the account.
You log in to the employees’ email, reset their Asana password, and then log in to Asana as the employee.
You shouldn’t have to do this but Asana thinks the users’ privacy is more important than your ability to run your company. Thankfully email providers like Google have a brain when it comes to Super Admin rights and privileges.
We have three people at our company who are Super-Admins, which includes myself and the business owners.
We have a lot of projects here that we cannot archive. We’re on the teams, and we’re even on the Projects listed as Editors.
But, we cannot archive them. We are the ones who first become aware that a project is ready to be archived. Currently we have to assign a task to whomever the Project Admin is.
Seems to me like a Super-Admin ought to have the right to do this. Sometimes, we have to archive 20 projects or more. Not being able to simply click and archive is exceptionally frustrating.
Honestly there shouldn’t be ANYTHING in Asana for our company that should be off-limits, its the entire point of being a Super-Admin.
Likewise along with that, there should be ways that the Super Admin can do things like place a task (like, a calendar entry) on all projects within the company, such as major holidays, business closed days, etc. Just mentioning it here are part of a Super-Admin discussion but I know it’s been discussed elsewhere also.
@Matt5 - I’ve merged your post with the existing request thread on this topic. Please consider voting for it with the purple button near the title!
Totally agree! It is a huge issue that a superadmin can’t manage all areas of the work, especially since this is a project management tool and needs to be agile and flexible. Would love an ETA on when this is being addressed!
I recently removed an employee who left our org from Asana and transferred all of their projects and tasks to their supervisor, but the supervisor cannot delete their old projects. What is the point of transferring ownership if the new owner is stuck with the dead weight? And why is Asana so obsessed with individual privacy, when I think that those policies should be set by the organization using the product? How many of us have workplace policies stating that the company owns all of the information in our apps and workstations? This is pretty standard stuff, right? This thread was started in November 2023. Will Asana take action in less than a year? Please?
I ran into this issue again and am posting that it is a major grievance, again.
+1 to this thread.
As a Super Admin - should be easy to be able to at least move projects to another team. For instance, we have an ALL USER team just for Training and Tips. Now it is flooded with projects from New Users that forgot to put on the privacy settings and now all employees can see the info… some of those people aren’t in Asana anymore and I have no way of cleaning it up.
I just ran into this issue. We have a GUEST user that created a project in a certain team, and they are now the sole owner of the project, despite not even being a full user of that team, let alone the org.
Despite me being a Super Admin on the Enterprise org, I can’t even go in and delete that project without reaching out to the GUEST himself? Seems unreasonably restrictive.
@FreshyJon - in the interim for your specific case, I would use a service account and the API (you can use the web-based explorer) to just delete the project. That’s obviously not a real solve for the underlying issue, but it at least gets that done now instead of you having to wait for them to do it.
Nice, we just upgraded to Enterprise and didn’t realize that was a feature. That’ll be useful. Thanks!