Master project management basics

[Andrea_Mayer]

Hey @Marine_Winterstein we work/worked on projects for crypto companies as well.

The most important point in my opinion is that you restrict the relevant Asana team so nobody can see or access unless they are invited.

Be careful with custom fields if they are shared on an organizational level as @Bastien_Siebman pointed out here

@Bastien_Siebman

A few months ago, I learned that there is a small “gap” in asana’s security regarding custom fields: if someone can see a task, they can see all its custom fields, even if originating from a project they don’t have the rights to see!

Today, I learned that the situation is actually a bit more “secure”: users will only see values for custom fields within the library of the organization, and not custom fields restrained at the project level. So if you want to store sensitive information, make sure to not include the field in the organization library.

Be careful!

Now I think you are also referring to Asana security in general, these 2 links might be helpful:

Trust at Asana • Asana

Privacy and security

Hope this helps