Hi @Omer_Buttt , are you by any chance in a Division or Team subscription, instead of an Organization?
See below point 3, here.
Yes, this is the reason why your project’s access settings are locked to just ‘Private to members’. In a Division, a project cannot be shared to the entire organisation.
@Richard_Sather even not with the admin accounts?
I doesn’t have to do with user permissions - an Asana Admin will see the same. It has to do with the data model.
But, it could very well be that you are unintentionally setup as a Division, rather than an Org.
It’s best to discuss with your Asana Admins and understand the reasons why they chose a Division. Then, you could contact Asana support to see what your options are.
3 Likes
If I’m understanding correctly, now when you mark a project as part of a different team from the team in which it was originally created, it will show in both teams? I was using this feature to move completed projects out of a team and into a “completed projects” team for housekeeping purposes. Otherwise the team project list will become incredibly long. If this is now the intended behavior, that attempt at housekeeping is worthless. I chose to move projects rather than archiving them in case we wanted to do a full text search to access any of our closed projects. I guess full text search still does not work on archived projects?
@Lara_Strain Yes, this is what I mean, but we still don’t have the solution for that yet. We have other ways to tackle it.
In your case, you need to remove the previous team from the share settings after moving it to ‘completed projects.’ This way, the project will no longer exist in the previous team.
1 Like
Hi,
Is there now a way to actually move a project from one team to another (such that it’s not showing up in both teams and without the various permissions changing that don’t seem possible on my plan)?
Hi @Shumaisa_Khan , welcome to the forum 
Yes, there is! 
Perhaps you missed it posted above, have a look at point 3 in my post here:
1 Like