Frequently asked questions

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Quick answers to the questions that come up most often, each with a link to the full story.

#Access and sign-in

#Can visitors sign in to a Confluence site with Google or Microsoft?

Yes. A Confluence admin picks Google or Microsoft in the site's Access settings and lists the Workspace domains, accounts or Microsoft organisations that may sign in. No OAuth app, client ID or secret is needed. See Restrict access to sites.

#Why does Microsoft say Need admin approval?

Your Entra user consent settings require an admin to approve Capable Sites once. An Entra admin signs in and chooses Consent on behalf of your organization. See Let visitors sign in with Microsoft Entra ID (Azure AD).

#Can guests in our Microsoft tenant sign in?

Only if you turn on Allow guests, which needs exactly one organisation. Personal Microsoft accounts are always refused, even as guests.

#Do visitors need an Atlassian account to read a published site?

No. With Public access anyone can read the site, and Confluence anonymous access can stay off. Visitors only need an Atlassian account if you choose Sign in with Atlassian. See Make a Confluence space public without anonymous access.

#Do Confluence page restrictions carry over to a published site?

No. Every page in a published space is on the site. Use the capable-sites-exclude label to keep a page off it. See Keep a Confluence page off a published site.

#Why was everyone signed out of our protected site?

Any access change signs everyone out, as does Sign everyone out. Occasionally a platform update ends sessions too. See Everyone was signed out of my protected site at once.

#How long do visitors stay signed in?

You choose 1 hour, 8 hours, 24 hours, 7 days or 30 days. Google and Microsoft sign-in stop at 7 days. See Access modes.

#Why does saving Access settings fail?

Usually the limit of 12 access changes an hour across all your sites. The message says so; save again later to apply what you stored. See Saving Access settings fails with a generic error.

#Cookies and analytics

By default the container waits until a visitor selects Accept all. Turn on Tag Manager handles consent to load it straight away and let its own consent settings decide which tags fire. See Use Google Tag Manager with a published Confluence site.

With the Cookie settings link in the footer of every page. A choice lasts 12 months. See Integrations and cookie consent.

#URLs, search engines and publishing

#How many redirects can a site have?

Up to 100,000 characters of rules, roughly 1,300. Redirects have their own card in Settings, which collaborators can edit. See Redirects.

#Why does /docs now open the space when it used to show page not found?

Space addresses without a trailing slash now forward to the space homepage. Each site picks this up on its next Update and Promote. See Spaces, URLs and navigation.

#Does a published site have a sitemap and robots.txt?

Yes. When you promote, the live site gets /sitemap.xml, with one sitemap per space, and a robots.txt that allows crawling and points to it. Both use your custom domain once it is active. Staging previews are never indexed. See SEO and metadata.

#Can I remove the Report content link from my site footer?

No. Every published page and homepage has it, below the Created with line, so anyone can report content to Capable. See What becomes a page.

#Why are my changes not on the live site?

Content and most settings need Update, then Promote. Access, collaborator and custom domain changes apply straight away. See Update a published Confluence site after editing pages.

Short answers. Full stories one click away.