What would be the best route to post a page that would be viewable from all accounts in our two domains and would they need a license to do this, since we use managed accounts or is there a way to separate the one page and the user access?Thank you
Hi @D_Anna Oller ,
If both domains are under one Atlassian org:
Create a group with users from both domains (admin.atlassian.com → Groups)
Add that group to the space permissions with View access
Users need a Confluence license (Free tier counts)
If you don't want to deal with licenses:
Use Public Links (Premium/Enterprise plans) — anyone with the link can view, no login needed
Or enable Anonymous Access on the space — but that makes it visible to everyone, not just your domainsIf anything is still unclear, feel free to reach out to us.Best Regards,Venkateswarlu KuruvaAtlassian Community Contributor
Apart from what Venkateswarlu said, there are some other methods you could use:
We've constructed both of those in different sites, but maybe you could have some better flexibility with the second one as JSM does provide domain-based configuration and access. 👀
Cheers,Tobi
Hi @D_Anna Oller and welcome to the Community.
If you have two Confluence sites with separate license (and thus seats), then your options are limited to what @Tomislav Tobijas and @VENKATESWARLU KURUVA said.
But there is an app for that.
Scroll Sites for Confluence creates a static website from Confluence content - including blogs.
Two crucial things:
Possible solution:
Disclaimer: I work for K15t, maker of Scroll Sites. But to my best knowledge, it's the only app that allows you to publish Confluence blogs to a website that you can protect access to.
Hi @Tomislav Tobijas Guests would work but if the two Confluence sites are in the same org, that would push the terms and conditions for Guests fair use a bit too far
@Kris Klima _K15t_ true that. Although Rovo does actually suggest that as a solution, despite stating that you're looking at users from the same org 😅
But yeah, just to confirm what Kris said, and it's stated here:
Important policy information You may not convert current or former paid users to guests. The purpose behind the guest feature is to invite users outside of your organization. Atlassian reserves the right to restrict your access to the feature if you're not using it in compliance with this purpose and the guidelines outlined in Atlassian documentation. Atlassian also reserves the right to change the ratio of guests to paid users.
You may not convert current or former paid users to guests. The purpose behind the guest feature is to invite users outside of your organization.
Atlassian reserves the right to restrict your access to the feature if you're not using it in compliance with this purpose and the guidelines outlined in Atlassian documentation. Atlassian also reserves the right to change the ratio of guests to paid users.
It looks like you're new here. Sign in or register to get started.
