Let visitors sign in to a Confluence site with Google

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

To let visitors sign in to a Confluence site with Google, a Confluence admin opens the site's Settings, chooses Access, selects the Google card, adds your Google Workspace domain under Workspace domains and selects Save changes. Only accounts in the domains and individual accounts you list get in, and the change applies straight away.

#Before you start

  • You need to be a Confluence admin. Collaborators cannot turn on Google sign-in or change who it lets in.

  • You do not need a Google Cloud project, OAuth app, client ID or secret. Capable runs the sign-in app.

  • If your Google Workspace blocks apps that have not been configured, ask a Workspace admin to trust Capable Sites once. Restrict access to sites has the Admin console steps.

#Steps

  1. Open Capable, choose Sites, open your site, and select Settings, then the Access card.

  2. Under Who can view this site, select Google.

  3. In Workspace domains, type your Workspace domain, such as acme.com, and press Enter. Add every domain your people sign in with.

  4. Optionally, in Individual accounts, add exact addresses such as a contractor's Gmail account.

  5. Under Sessions, choose Stay signed in for. Google sessions last at most 7 days.

  6. Select Save changes.

  7. Open the site in a private window, select Sign in with Google and check you get in.

#If it does not work

  • Save changes is greyed out with Choose who may sign in. Add at least one domain or account.

  • Your organisation does not have access to this site. The account belongs to a Workspace domain you have not listed. Workspaces with several domains need each one.

  • This site does not accept personal accounts. Sign in with your work account. The visitor used a personal Google account. List it under Individual accounts if it is a Gmail address you want to let in.

  • Google says the app is blocked. Your Workspace does not trust Capable Sites yet. The Admin console link on the Access page takes a Workspace admin there.

A refused visitor can select Try a different account on the Access denied page.

Your Workspace, your people, no OAuth app to build.