product-example 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.
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. |
Evidence Role
This source is treated as product-example evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: Atlassian Support. Last checked: .