You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
So in your Atlassian account there's a full name and a public name. I'd like to use my full name only inside of my organization and the public name for all public things. The problem is that de visibility of my full name is set to 'everyone' and it's greyed out, zo i can't change it. Could anyone please help me with that?
Thanks for your response!
Top one can't be changed
An organization inside Atlassian is defined when someone who is an administrator of the company sets up the organization concept inside Atlassian's admin panel. When they do this they prove ownership over the email domain of the users in the organization.
Once this is done, the accounts of the users inside that organisation become managed which allows you to specify privacy settings to allow different profile fields to be shown only to other members of the organization. If your administrator hasn't set up your organization yet you account is considered unmanaged and as you are not a part of an organization you will not be able to set privacy restrictions to only organization members.
I'm not sure how (or why, rather) a single organization restricts changes to my global Atlassian account, that is completely independent from that? I joined a public project and now I can't change my profile visibility anymore. I can't seem to get hold of the admin. And apparently, it's also impossible to leave an organization/project by yourself, so now I'm stuck with either having private info visible publicly where I don't want it or deleting my entire Atlassian account.
Surely this can't be the intended scenario?
Hi @Christian Syska
To clarify my statement above, if you are part of an organization you have more profile visibility opens than if you are not, as you are able to set fields to public, private or collaborator where the collaborator option only exists for managed accounts.
Some of these fields might be restricted if, for instance, your admin is syncing your details from a company IdP. If you have a managed account, your organizational admin has proven ownership over your email domain which we check on a daily bases by ensuring that they have set tokens on their DNS record or at the root of their server. Any account with an email address of the claimed domain is considered a managed user of that organization.
If you wanted an unmanaged account which isn't part of the organization, you will need to create an Atlassian account with a personal email address.