product-example 2 linked patterns checked

Atlassian profile and visibility settings

Documents profile visibility controls, profile photo defaults, public name versus full name behavior, where profile information appears across products, and how profile visibility affects third-party app access.

Read with a purpose

What this source can teach

Use this source to inspect a concrete implementation and the decisions visible in its context.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. Check the setting. Compare the source's platform, people, and constraints with your own decision.

Pattern Decisions This Source Supports

Pattern Supported decision Required contract Claim note
Create user profile Choose create user profile when the user is defining visible identity information that other people or public surfaces will see. The form states which profile fields are required, optional, managed, hidden, or public before users save. Atlassian supports visibility controls, public-name behavior, profile photo fallback, and warnings about where profile information appears.
Profile setup Choose profile setup when an existing profile is usable but incomplete, stale, or missing recommended details that improve collaboration, discovery, trust, or public presentation. Opening profile setup loads the current saved profile and clearly distinguishes already-complete, missing, recommended, optional, managed, and visibility-sensitive fields. Atlassian supports profile visibility controls, profile photo fallback, public-name behavior, and warnings about profile information surfaces.

Comparisons supported by this source

Evidence Role

This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.

Publisher: Atlassian Support. Last checked: .

Saved items