@Shaun McGuire As Michael suggested Refined Vendor App is also what I've seen used most for custom branding and themes confluence and JSM.

I attended a webinar. The most useful part was a visual representation using work item views classifying whats they define as in-app data and whats defined as meta data. It is concerning to me for many reasons, and with meta data you can only switch off if you move to enterprise or are "exempt based on industry, but you won't know if you're site will really be exempt unless you check with them via Support prior or if you wait too see if the button pops up the UI when they rollout, if it does, then you'll have to contest I suppose if you deem they got it wrong.

Wow, cool niche requirement. I have not had this migration requirement drop on my desk before. If you get gold nuggets from Atlassian Support Engineers please share. I'm invested now to know the outcome

I've heard the rumour. Rumours like this (often planted I'm told) positively boost stock markets based on speculation. Atlassian won't mind a little boost in that department. I think the timing and changes that they are making to their privacy policy is the type of data that the likes of AI beasts would really love to have access and insights to. If the rumour is just a stock market ploy, maybe Atlassian is starting to gear up for some future negotiation options/power. Anything is possible, but also rumours and speculation. Time will reveal 🙂 I will be sad if true.

Too much to type in great detail, but can guide you what to read up on if applicable to your use case: - You can selectively manually claim your accounts in bulk using csv method after claiming your domain. It's just pain in the butt then to maintain with new user onboarding from there on when you don't opt for the automatic claim account option. - Read up on how Atlassian Directory / Guard handle/not handle nested - One Okta Tenant only, if you have more than one to connect you'll need enterprise - Every licensed app user you claim as managed account under your domain is billed a guard seat once. But good news if the user is only granted "customer role" atlassian doesn't bill guard seats for them even if its a claimed account on your domain. - You may come across external users that you invite to your site, that can't login with their external atlassian accounts if their org admin that claimed that domain and account suspended or deactivated their atlassian account within their org. That user either need to be given a email from your domain then or they have to ask their org admin to restore their atlassian account. - Non-billable policy can be used if useful in your scenario. Read up on it. - Don't know if its still the case, or if Atlassian fixed it since (i'll need to check) but if there's issues with your credit card when guard bill is due, you lose your guard setup and have to it again. I do hope they have put a fail safe in to stop that now, but thought I'd mention to be diligent. Two of my 2024/2025 clients had that happen with no warning when their credit card expired and payment didn't go through. There were no smiles in the room that day 😬

@Shaun McGuire I revisited the open bug on that payment failed scenario. It's shows still In Progress, but improvement that has been made if you restore payment within 14days, you can get your configuaration settings restore. After 14 days you're still toast: https://jira.atlassian.com/browse/ACCESS-690