Dear Atlassian, can you please stop asking my users to violate corporate policy?

[Darryl Lee]

Someone on our Identity team asked me yesterday:

Why is google drive an option to connect?  This is not a [company] standard which is onedrive.

Which is a fine question indeed.

And I'm not alone. My fellow champions mentioned that they don't use Slack, but their users continue to get prompted to connect Rovo to Slack.

Conversely, another says they're getting prompted [in Confluence - sorry, I'll add a keyword to this question] to connect to Microsoft Teams, when they already have connected Slack.

So, two things:

1. You're confusing our users. I can easily imagine somebody saying "Oh man, we have Slack now? Sweet! I hate Teams!" (I have a hard time imagining the converse, but sure, ok, maybe.)
2. You're compromising our security by encouraging users to connect to services that are outside of our approved corporate policy. As the same person from the Identity team wrote: "just dont want users encouraged to connect their personal non [company] google drive"

Yes yes. We all know the origin story of Atlassian. Part of your explosive growth was that anyone could download your cool little bug tracking software Jira and install it on a spare machine and they didn't HAVE to ask permission or get approval from corporate IT, procurement, legal, or trust teams.

Nope, just download and go! Shadow IT be damned!

Welp. You're a real company now, selling to other real companies. Please act like it.

[Bill Sheboy]

Hi @Darryl Lee 

As you are aware from other community threads and open JAC suggestions to prevent "marketing" prompts, this is definitely an ongoing problem.  A related problem is the confusion and extra work created by pushing UX experiments as the previous opt-out of "lab features" toggle no longer works predictably.  These things create non-value adding work (i.e., waste in lean terms) for customer admins tracking down if something is broken and / or undoing mistakenly used features, and for Atlassian Support when those same customer admins submit tickets to track down root causes.  As we have seen from the scale of some recent changes, it also reduces the trust of customers in Atlassian...and leads us to wonder: how aligned are the marketing, product, operations, and support teams within Atlassian?

I wonder about a re-thinking of the apparent approach: rather than too much "bias toward action" and "maybe apologize later if we were wrong", consider instead using positive control for enterprise tools.  Specifically...

• add the ability for customer admins to enable / disable such features / prompts,
• by default disable them all,
• directly notify customer admins (i.e., email, text, change control feed, etc.) of what is potentially happening (including a change management and risk plan), and
• for customers and admins who want it, allow a single toggle option to "give me everything you are trying / releasing immediately, regardless of any potential risks".

Free-license level customers will likely still be "stuck" as they have limited admin features.  And, allowing paid-license teams to positively control the features / push notifications on their timeframe will provide tools to make better choices aligned with their own enterprises.  Atlassian product leaders stated they will share more about their release planning in December 2025, so let's see what that includes.

Kind regards,
Bill

[Darryl Lee]

Bill! The ego to my id! (Is that right? I just had to google it. Ok yeah, close enough. Maybe I should've stayed in college. :-)

Let us count the ways Bill is great:

1. No provocative, sarcastic language that might turn people off of the real message?
2. Concrete, well-considered suggestions rather then just off-the-cuff ranting?
3. Bullet points!

Once again, I will make the plea of many fellow Champions as well as probably countless Atlassian Community Managers: please join us!

[Darryl Lee]

Hum.

So assuming best intentions, MAYBE Rovo is only supposed to present that choice if they notice you have existing Google, Slack, or Microsoft session cookies, although... I'm pretty sure that's not how session cookies are supposed to work.

Has anybody gotten prompted to add Rovo connectors for products that they NEVER use and so therefore should not give off any signals that it's OK to ask the user to connect?

BUT ALSO, Connections to other sources should be at the Admin level, not the User level. Argh.