Hi @Arthur K_ Amistoso Jr_, the profile half of that has an endpoint and the visibility half doesn't.
Profile is PATCH https://api.atlassian.com/users/{account_id}/manage/profile, in the user management REST API. The body takes name, nickname, zoneinfo, locale, and extended_profile with job_title, organization, department and location inside it. It wants an org admin API key as a bearer token, only reaches managed accounts, and it refuses on any account synced in from an external SCIM or Google directory. There is an email endpoint next to it, a PUT on that same path ending /email, but it changes the address. Careful with that one: the target domain has to be verified first because the new address gets treated as verified, and the spec says the call invalidates all active sessions. Email is readOnly in the profile schema anyway.
Visibility isn't in that API anywhere. I pulled the OpenAPI spec to be sure. Nine paths, and the string "visibilit" appears zero times in the file. The privileges parameter on GET /users/{account_id}/manage is a closed enum of eight values covering profile read and write, setting the email address, enable/disable, delete/cancel-delete, and API tokens. Nothing either side of it. Zero hits in the SCIM user provisioning spec, and the four in the org admin spec are all read-side, the sort that tells you email "will be absent" when someone has restricted it. So it stays where you found it, id.atlassian.com/manage-profile/profile-and-visibility under Contact, and the account holder is the only one who can move it.
If you're after this for a whole directory, ACCESS-668 is the open request for org admins to set it centrally, currently Under Consideration: https://jira.atlassian.com/browse/ACCESS-668
That's the documented surface. The settings page is driving something internal, I haven't found anything supported you'd point a script at.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.