Good point, @Henry_Remington! I wasn’t even thinking of the Asana staff who are acting as project valets for us. It seems like such a no-brainer to give this work to the people paying to use the app.
3 Likes
I’m adding @Richard_Sather in hopes that this discussion gets some traction. Does anyone here in this forum have access to discussing this issue with Asana devs?
1 Like
Hi @Henry_Remington , thanks for looping me in. I’ve been watching this thread for a while and agree that Super Admins should be given rights to manage private projects (but perhaps without seeing it’s contents due to privacy concerns). I’ve had this issue with several clients that I’ve consulted and I’ve had to resort to Asana support to unlock certain projects, which I’m sure they have better things to do!
I can safely say that the Asana product team monitors such threads in the forum and all voices are taken into account.
All I can do is ping @Marie who could kindly escalate this feedback thread but there is no assurance as to when or if this will ever get implemented. Note, I don’t work for Asana and they don’t make their roadmap public.
4 Likes
Hi @Richard_Sather and thanks for including me! I have escalated a task to our Product team to highlight this request again. While I can’t promise if and when it will be considered, I commit to keeping you posted here as soon as I have an update.
3 Likes
Thought it was just me and that maybe I was missing something. I realize this is a big issue and has been for some time. Very disappointed. Huge issue. I have a team of newbies who have been learning Asana and creating projects. As I need to train and edit, I have no power other than to wait on their availability to fix. This should not be.
5 Likes
Just like Chrystal wrote it before me, this causes us many headaches. We are just rolling out Asana in a team that has a lot to learn and I can’t even move projects around from one team to the other if they opened them in the wrong team. I did a similar deployment with a competitor tool and I had super admin powers which helped me coach the team when i saw something that did not make sense or to correct major mistakes quickly before they got out of hand. Please, make this happen fast !!!
5 Likes
+1 on this. We have a bunch of Teams we’d love to clean up, but we don’t know what projects are in those teams. So we also risk deleting work without knowing it if we delete those teams. @Marie
3 Likes
+1 on this… I realize there must have been some reason for how this was implemented in the first place, but there has to be a role that has access to everything, and not being able to edit details on some projects really drives me nuts.
2 Likes
We keep encountering situations where the two Super Admins at our company cannot do things that it seems our top-tier admin people should be able to do.
I am one of the super admins, so is our business owner.
We have a lot of Projects that neither he nor I are a member of (in Asana) because we didn’t have any direct dealings with it. Now that the jobs that these projects represent are complete and basically “old news”, we want to clean up the teams by archiving them.
We can’t. I understand why normal members cannot archive each other’s projects, but the Super Admin is the top-tier control level we have available to us, and I am really surprised/disappointed that we cannot.
I realize we could technically ask the project owner to go ahead and archive it, but that’s adding a lot of steps to the whole thing when it should just be a click or two, for a Super Admin.
4 Likes
@Matt5 - I merged your topic with a similar popular one. Technically, your ask is slightly different, but I think the outcome you want (ability to manage project details, including archiving, as a super admin) is aligned.
As Superadmins in Asana, I believe we should have the highest level of permissions to effectively and efficiently manage all aspects of the organization. However, currently, there exists a limitation that prevents Superadmins from accessing and modifying or deleting all projects.
This limitation can lead to issues, particularly in larger organizations or teams with complex project structures. Without the ability to centrally manage all projects, Superadmins cannot fully ensure that the organization is working effectively and consistently.
Therefore, I urge the Asana team to reconsider this functionality and provide Superadmins with the necessary permissions to manage all projects. This would enhance flexibility and control and significantly streamline the administration process.
6 Likes
This is a very good thread and something that requires addressing.
I personally do not agree that super admin should by default get access to all private projects. I think the feature should be a little more nuanced to protect certain privacy matters that are still managed in a private project.
For example, I am not in HR but I am the Asana Super admin of a company. I should not be privy to all projects running by HR that may include sensitive information.
What I would suggest (and I agree there should be a super admin control on projects), is a security feature that allows project owner to differentiate between:
- Private Project - Org Workflow
- Private Project - Personal / Confidential Workflow
Something between these lines that can be properly mapped out and defined would be more suitable.
I also think that as a super admin should be able to view them both in a list, but I think the super admin should only be granted admin rights to the Private Project - Org Workflow. The other type of private should not be accessed by default, but by invitation only.
I added my vote to this thread.
@Marie - FYI. something to consider and better define perhaps.
4 Likes
@Rashad_Issa, I’m curious what privacy concerns or situations you are referring to. As a super admin, as someone in IT, we have to be trained in all aspects from legal to HR. So we see the good the bad and the ugly and that’s just apart of the job. And we have NDA’s to hold us accountable in that regard.
4 Likes
I have seen in this thread a number of times. Also my org isn’t big enough to go enterprise. I don’t have 10,000 users. So upgrading is not an option.
From a privacy standpoint, if there are privacy concerns about SuperAdmins seeing something then that person shouldn’t be a SuperAdmin. People in that position need to be trusted to see everything. It’s a compliance, regulatory and data compliance issue among many other things that are mentioned in this thread.
4 Likes
Asana is playing the role (Top tier super admin) that should be given to the company who is paying Asana to use the app. It’s backwards. As a company, we own the information that is in Asana, not the employees and NOT Asana. We are currently considering moving to another platform and we have been using asana for almost 10 years. Unbelievable. It’s a no-brainer. I’ve never heard of anything so ridiculous where a super admin doesn’t have access to everything. Why are we called “super admins” when we clearly are not. We are the non-super admins with a twist of limited permissions.
8 Likes
I can see having limited visibility for standard administrators, but I think that the Super Admin role really needs to be a step beyond that which does have complete authority to maintain the tool including visibility, editing, and deletion controls. Perhaps what we really need are configurable roles. Then, you can have the head of HR managing that and someone at a very senior role as the end-all-be-all super admin.
2 Likes
Anyways, I’m really surprised that we still do not have an answer to this. In two different Asana workspaces that I’m in charge of, I have had people unintentionally create boards and its a serious chore to have to get a hold of these people to delete the boards. Then I have to explain the situation to them and walk them through the process. Its a serious annoyance.
5 Likes
Hello @Marie , Just reaching out again to see if there are any updates from the Asana staff. This thread continues to have repeated concerns about super-admins not having proper IT super-admin levels of visibility. Please let us know if there is anything moving on this.
Hello @Henry_Remington, I’ve recently raised this feedback with our team as part of our Voice of Customer program. While this is something our team is considering, I don’t think we have (yet) any formal plans. I will keep you in the loop on this thread as soon as I have an update!
3 Likes
How is this still not a thing? If someone creates workflows and leaves the org, how can we take ownership of them?
6 Likes