How to handle Teams and People visibility in Atlassian Home

[Patrick Alexander]

Hello everyone,

I’ve been looking into the visibility settings for Teams and People in Atlassian Home and would like to hear how others are dealing with this topic. Based on my research, here’s what I’ve found so far:

1. Teams:

   • There doesn’t seem to be a way to restrict who can see a Team.
   • The Team name and Team members are visible to everyone in the organization.

2. People:

   • Users can set visibility restrictions in their profiles, but first and last names (Full name) still appear for others to see.
   • Also the user needs to know about the behavior and the option to limit the visibility by their own

We work with multiple customers in our system, so this unrestricted visibility is far from ideal. Additionally, we use an Enterprise environment with multiple connected sites, and the Teams and People lists appear to pull data from all systems within the enterprise organization.

This creates several challenges for us:

• Customer names and contacts might unintentionally become visible across the organization.
• It’s unclear how to manage or restrict this visibility across multiple sites effectively.

How are you managing this issue in your organization?

• Have you found any workarounds or best practices to control the visibility of Teams or People?
• Are you aware of any upcoming changes in Atlassian’s roadmap related to this?

Looking forward to hearing your insights!

Best regards,

Patrick

[Adamcalgary]

Managing Visibility of Teams and People in Atlassian Home

Hi Patrick,

Thank you for raising this critical point. We face the same challenges in our organization, and the current visibility model in Atlassian Cloud is a known concern, especially for multi-customer or multi-tenant environments.

Based on our experience, here’s how we are managing the situation:

1. Current Workarounds and Mitigations:
Naming Conventions for Teams: We have implemented a strict naming convention for Teams that avoids using customer names directly. For example, we use project codes or internal descriptors (e.g., `PRJ-205-Dev` instead of `Acme-Corp-Website`). This helps obscure the customer's identity while maintaining clarity for our team.
Proactive User Training: We actively educate our users about the profile visibility settings. This includes mandatory onboarding sessions and documentation that clearly explains how to set their profile information (like email, title, and department) to 'Private' or 'Only to people in these sites,' limiting exposure across the entire organization.

2. Engaging with Atlassian:
This is a common feature request. We have found the most effective action is to vote for and comment on existing feature requests in the Atlassian Community. This signals the priority to Atlassian's product team.
Relevant Request for Team Visibility: 
Relevant Request for Granular Profile Control: 

We encourage you and your team to add your votes and use cases to these tickets.

3. Official Recommendation:
Unfortunately, there are no administrative-level settings to override the global visibility of Teams or the full name field in People directories at this time. The behavior you described is by design for the "organization" level in Atlassian Cloud.

To my knowledge, there are no immediate upcoming changes on the public roadmap addressing this specific granularity. Therefore, the combination of internal naming policies and user education remains the primary mitigation strategy.

I hope this is helpful. How have other teams in your organization adapted? It would be valuable to share best practices.

Best regards,

Adam Gary

[Prachi Bolar]

Hello,

Welcome to Community :) 

Please check this : https://support.atlassian.com/platform-experiences/docs/work-with-atlassian-teams-across-your-products/ 

It has all the details on how to work with team accross products 

Thank you,

Prachi