Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Embedding Atlas into Confluence Behavior


We have a case raised with support regarding embedding Atlas data into Confluence. Depending on the embed/display option, the following message appears: "This integration requires storage access" in Confluence:2023-05-17 10 42 04.png

The message only appears for the "Display embed" option and not for a live link or live card.

Support are working on the case and have suggested disabling third party cookies on the domain. I have concerns about this as a viable/scalable approach but my question here is, is there something different about how Atlas has been architected that it behaves differently from other Atlassian products? For instance, I don't experience the issue when embedding a Jira roadmap into a Confluence page.

1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 21, 2023

Hi Sing,

Thanks for the feedback and sorry for the friction this authorization screen creates. We have indeed built some of the Atlas integrations with Confluence and Jira in. a manner that can cause this message to appear. Historically, using a method that requires cross-site cookies didn't cause this problem, but recently certain browsers (notably Safari) have taken a very aggressive stance against cross-site cookies, resulting in repeated auth screens.

The short term solution is to adjust your third party cookie settings or try using a different browser. Longer term, the Atlas team is investigating the best way to solve this problem

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events