Loading
PLATFORM
CAPABILITIES
ASANA AI
PLANS
Company Type
Teams
Industries
Use Cases
LEARN
SUPPORT
SERVICES
Help Center
search-icon

Topics

Visibility settings in mixed domains

In This Article

Mixed domains include a mix of paid and free users in the same organization. To help these organizations collaborate more openly, Asana is introducing expanded visibility options: Public Teams and Shared with Organization projects.

These settings make it easier for people to see high-level initiatives, find and join relevant work, and get up to speed quickly, which in turn reduces duplicative efforts created when teams can’t see each other’s projects. They also lower admin overhead, since admins no longer need to manually add or invite every user to widely shared work. This guide explains what these settings do, when to use them, and how they behave in mixed environments.

What are mixed domains?

Domains that contain divisions are called mixed domains, because they can have a mix of free and licensed users in them. Read more about license assignment in divisions.

New visibility settings are now available in projects and teams across mixed domains.

Public teams

A Public Team is visible and discoverable to everyone in the organization except guests.

Members can:

  • Join the team without needing an invite
  • See public projects shared with that team
  • Participate more easily in cross-functional work

Shared with Organization projects

A project Shared with Organization allows anyone in the domain to:

  • Discover the project
  • Request access or join where appropriate
  • View project metadata even if full access isn’t granted

This supports transparent collaboration outside of a specific team.

Note iconNote

Guests won't see public teams or org-shared projects unless they are added directly to them

How these settings work in mixed domains

Public teams and shared-with-org projects become discoverable by the entire domain with guests being the exception. Free users can still see these objects, but they will not be able to edit or create public content.

These visibility settings do not change existing project privacy settings or access levels within the project.

Opting out before feature launch

If your domain is eligible for the feature, super admins (or division admins if no super admin exists) will see a banner at the top of the Security page in the admin console. This banner provides information about the upcoming change and includes an option to opt out.

Steps to opt out before launch:

  1. Open the admin console
  2. Navigate to Security
  3. At the top of the page, click the link in the banner to review the update
  4. In the modal which opens, choose the option to opt out
  5. Confirm your selection

Once confirmed, the feature will not be enabled when the rollout begins. If you change your mind later, you can re-enable it after launch or reach out to Support for assistance. A small number of domains are excluded from this initial rollout. If your domain is excluded and you would like access to the feature, you can reach out to Asana Support to request it. If your domain is not included in the launch, you will not see a banner.

How to disable or enable the feature after launch

Once the feature is live, super admins can adjust who in the domain can create Shared with organization projects from the admin console.

Managing Shared with organization projects after launch

  1. Open the admin console
  2. Navigate to Security > Project settings
  3. Under Project privacy and access find Select who can share projects with the organization
  4. Choose one of the following options:
  • Anyone at yourdomain.org
    • Any full member in your domain can share projects with the organization
  • No-one at yourdomain.org
    • Sharing projects with the organization is turned off for everyone

Managing public teams after launch

  1. Open the admin console
  2. Go to Security > Team privacy settings
  3. Under Team privacy and access find Select who can create and make teams public to the organization
  4. Choose one of the following options:
  • Anyone at yourdomain.org
    • Any full member in your domain can create or make teams public
  • No-one at yourdomain.org
    • Creating public teams is disabled for everyone

Frequently asked questions

What are the best practices for mixed domains?

Recommended when:

  • You want high transparency across cross-functional teams
  • You rely on organization-wide initiatives, OKRs, roadmaps, or onboarding spaces
  • Teams frequently need visibility into one another’s work
  • You want to reduce admin manual work

Use with caution when:

  • Your domain uses divisions as data boundaries

Does this change the privacy of my existing teams/projects?

No. Nothing existing changes. This only affects new teams or projects created using the public settings.

Do guests see public teams or org-shared projects?

No — they only see what they’re added to.

Can free-tier users suddenly create public projects?

No, they can not create public objects, but they can see projects that are shared with org with limitation to how they can collaborate.

Can admins reverse the setting later?

Yes. Super admins can disable or re-enable it.

Does this expose private information?

No. Private teams and private projects remain private. The update only applies to items intentionally created or changed to public or org-wide.

Related articles

Loading
How to manage mixed domains | Asana Help Center