Embedding a live Google Doc inside a Confluence page is one of the easiest ways to keep your team aligned without switching tabs or dealing with outdated files. Whether you’re documenting requirements, drafting content, sharing meeting notes, or collaborating on internal policies, a Google Doc embedded directly in Confluence keeps everything visible, editable, and always synced.
In this guide, you will learn the most reliable ways to embed Google Docs in Confluence, from the old iframe method to the modern and secure approach using the Google Docs for Confluence app by ikuTeam. You will also understand how permissions work, how real-time updates sync automatically, and how to choose the best method for your team’s workflow.
Embedding Google Docs directly into a Confluence page gives teams a smoother, clearer, and more collaborative way to work with shared documents. Instead of juggling tabs, searching for links, or wondering whether the file in the issue is the latest version, the document simply lives where the conversation happens.
Here’s why teams rely on this workflow:
Requirements, meeting notes, drafts, and project updates stay visible on the same Confluence page where teams comment, plan, and decide. No extra steps, no context switching.
Teams jump between tools less. Instead of editing in Google Docs and documenting in Confluence, everything is done from a single page.
Because the embedded Google Doc is the real document from Google Drive, there are no duplicate uploads or conflicting versions. What you see in Confluence is always the latest version.
Edits made in Google Drive appear immediately inside Confluence. Edits made from within Confluence sync back to the original Google Doc in real time.
Instead of hiding behind links or attachments, the document is displayed directly on the page, making it easier for product managers, developers, designers, and leadership to stay aligned.
Requirements documents and product specs
Meeting notes and collaborative agendas
Policies and internal guides
Shared writing and content drafts
Project briefs and proposals
Embedding Google Docs in Confluence turns static pages into dynamic, real-time collaboration hubs while preserving the structure and organization Confluence is known for.
When teams want to embed a Google Doc in Confluence, they usually fall into one of three approaches. Each method works, but they vary widely in security, ease of use, and long-term maintainability.
Here’s the quick overview:
1. Paste the Google Doc link (quickest, but not embedded)
Fastest method: just paste the URL into a Confluence page
Confluence converts it into a clickable link
Document opens in a new tab
Not an actual embed
2. Publish to Web + HTML / iframe macro (manual workaround)
Uses Google’s “Publish to web” feature
Requires iframe or HTML macro
Embeds the doc visually, but with major security drawbacks
3. Google Docs for Confluence app by ikuTeam (recommended)
Paste the Google Doc URL
The app embeds a live Google Doc directly in Confluence
All permissions remain managed by Google Drive
No HTML, no iframes, no public sharing
The only secure and scalable method for daily use
Below, we dive into each method so you can choose the one that fits your workflow.
The most basic option is simply pasting the Google Doc URL into a Confluence page.
Go to your Google Doc
Copy the URL
Paste it into the Confluence page editor
Confluence automatically turns it into a hyperlink
Extremely simple
Zero configuration
Fully respects Google Drive permissions (users only see it if they have access)
No embedded view
Opens the document in a new browser tab
Breaks page flow and context
Poor for collaboration visibility
Quick internal references
Temporary documents
Links you don’t need visually embedded
If you need the Google Doc to actually appear inside Confluence, this method isn’t enough.
This is the old-school workaround teams used before secure integrations existed. It works, but it comes with significant limitations and important security concerns.
Inside Google Docs:
Go to File → Share → Publish to web
Select Embed
Copy the generated <iframe> code
Important warning: Publishing a Google Doc to the web makes it publicly accessible to anyone who has the link or can load the embed. This bypasses Google Drive permissions entirely.
For most teams, this is a deal-breaker.
In the Confluence page editor:
Type /iframe (iframe macro)
or
Type /html (HTML macro, often restricted by admins)
Paste the iframe embed code
Adjust iframe parameters, such as:
width="100%"
height="600"
frameborder="0"
This creates a static embedded view of your Google Doc.
Pros
Works without installing any add-ons
Creates a visible, inline embedded document
Fully customizable HTML/iframe sizing
Cons
Requires HTML macro (often disabled for security)
Publishing to the web exposes your document publicly
No control over toolbars or UI elements
Manual maintenance if the embed code changes
Cannot enforce Google Drive permissions
Not suitable for confidential or internal documents
If your team needs a secure, permission-aware, and reliable way to embed Google Docs in Confluence, the iframe method is not recommended. The next method solves all these issues.
If you want a secure, modern, and fully supported way to embed a Google Doc in Confluence, the Google Docs for Confluence app by ikuTeam is the most reliable choice. Unlike links or iframes, this approach gives you a real, live Google Docs embed inside Confluence with proper authentication and enterprise-level security.
This method removes every limitation of traditional embeds:
No iframe code
No HTML macro
No publish-to-web
No public access
No security exposure
No manual maintenance
Instead, you get a direct and fully synced Google Docs embed, supported natively through a secure macro.
The workflow is simple:
Install the app from the Atlassian Marketplace
Paste the Google Docs URL inside Confluence
Confluence renders the live document instantly
Each user authenticates with their own Google account
Google Drive permissions remain fully enforced
This is the only method that provides a truly embedded Google Doc with real-time editing while keeping your organisation’s security, governance, and access controls fully intact.
The app is built to behave exactly the way modern teams expect. Here’s what happens behind the scenes:
When you paste the URL, the app automatically creates a macro that renders the document directly inside Confluence.
This is a real Google Doc, not a screenshot, not a static embed.
Each viewer must be logged into Google in their browser.
The app uses their Google identity to retrieve the doc.
Meaning:
If they have view access → they can view in Confluence
If they have edit access → they can edit in Confluence
If they are not authorized → they cannot see the document
Exactly the same behaviour as Google Drive.
No copied files.
No stored versions.
No exposure through “publish to web”.
All access control continues to be managed by your Google Drive settings.
Any edit made:
in Google Docs
in Confluence
or directly in Google Drive
appears instantly for everyone.
Nothing is stored in Confluence; the app acts as a secure viewer/editor linked to your Drive.
Because the app runs on Forge:
No file content is stored anywhere outside your Google Drive
Data compliance follows Atlassian’s strict platform rules
Nothing leaves your environment except permissions-validated requests
In short: This is the safest, fastest, and most accurate way to embed a Google Doc in Confluence.
Once you use the Google Docs for Confluence app, embedding a live Google Doc becomes a simple, secure, and fully integrated workflow. Here’s the complete step-by-step guide.
You’ll find the app on the Atlassian Marketplace.
Open the Marketplace listing for Google Docs for Confluence
Click Try it free
The app installs instantly, it’s Forge-based, secure, and fully GDPR/CCPA compliant
There’s nothing to configure. It works immediately across your Confluence environment.
Embedding a document takes only a few seconds:
Open the Google Doc in your browser
Copy the URL from the address bar
Go to your Confluence page and enter Edit mode
Paste the URL directly into the editor
The app automatically transforms the link into a live Google Docs macro and begins rendering the preview.
You don’t need to use iframes, the HTML macro, or publish anything to the web.
Every user must authenticate with Google before they can view or edit the embedded document.
If the user is already signed in, the document displays immediately
If not, the app prompts them to sign in with their Google account
The app respects Google Drive sharing rules
This ensures:
Only authorized users can see the embedded Google Doc
Editing follows the exact permissions defined in Google Drive
No public links, no exposure, no bypassed security
You can fine-tune how the Google Doc appears on your Confluence page.
Select the macro → click Edit to open layout controls.
Width
Set to 100% for a full-width experience
Or specify a fixed pixel width for tighter layouts
Height
Adjust to control the visible area before scrolling
Hide preview on load
The document loads but stays collapsed
Perfect for pages with multiple embedded docs or long reports
Show toolbars
Enable or disable the Google Docs toolbars
Useful for choosing between a clean viewer mode or an editable workspace
Show headers/document interface
Toggle visibility of title, headers, and interface elements
Ideal when you need a minimalist embed for documentation pages
Full-width policy document → Width 100%, toolbars on
Compact meeting notes → Fixed width, minimal toolbars
Dashboard with multiple docs → Hide preview on load for each macro
Once you click Publish, your Google Doc appears instantly inside Confluence.
Edits made in Confluence update in real time
Edits made in Google Docs update in real time
The document always reflects the single source of truth in Google Drive
Multiple embedded docs? Just paste each URL, and every document becomes its own macro with its own layout settings
This method gives your team a seamless blend of Confluence structure and Google Docs collaboration, without duplicating files or breaking permissions.
When embedding a Google Doc in Confluence, you have two main options: the classic HTML/Iframe macro approach or the modern, secure method using the Google Docs for Confluence app by ikuTeam. Here’s a clear comparison to help you choose the right method for your team.
|
Feature |
Iframe or HTML Macro (Traditional Method) |
Google Docs for Confluence App (ikuTeam) |
|---|---|---|
|
Ease of Setup |
Manual setup, copy and paste of iframe code, publish to web required |
Paste the URL and the macro loads instantly |
|
Security |
Public exposure of the document, no control over access |
Fully respects Google Drive permissions, only authorized users can view or edit |
|
Permission Handling |
Anyone with the link can view the file |
Users authenticate with Google and see only what they are allowed to see |
|
Document Type |
Works only with publicly published Google Docs |
Embeds live documents with no public links or publish to web |
|
Maintenance |
High effort, code must be updated when the document changes |
Zero maintenance, no iframe code, no HTML macro, no embed upkeep |
|
Editing Experience |
View only, no real collaboration inside Confluence |
Real-time editing directly inside Confluence |
|
Layout Control |
Limited to width and height in iframe code |
Full layout controls including width, height, toolbars, headers, preview options |
|
Compliance |
Often blocked by admins due to security concerns |
Forge-built, secure, compliant with enterprise governance |
|
Best For |
Small teams, temporary embeds, non-sensitive content |
Secure teams, enterprise use, long-term documentation, collaborative workflows |
If your goal is to embed Google Doc content in Confluence securely, cleanly, and without breaking permissions, the Google Docs for Confluence app is the clear winner. You avoid public exposure, eliminate messy code, and gain a real editing experience directly inside Confluence with seamless Google Drive integration.
For modern Confluence spaces, especially in Google Workspace environments, the app is the enterprise-ready solution.
Even with the correct setup, a few common issues can affect how embedded Google Docs appear or behave inside Confluence. Here’s how to quickly diagnose and fix them.
Most common cause: The viewer is not authenticated or lacks Google Drive access.
How to fix:
Make sure the user is signed into the correct Google account in the same browser.
Verify the file’s Google Drive permissions (View, Comment, or Edit).
Confirm that the user has access to the folder where the document lives.
Cause: The toolbar may be disabled in the macro settings.
Fix:
Enter Confluence edit mode
Select the Google Docs macro
Click Edit
Enable Show toolbars
This restores the familiar Google Docs formatting and editing menus inside your Confluence page.
Cause: The width or height settings need adjustment.
Fix:
Open the macro’s layout options
Increase Width (100 percent for full-width pages works best)
Increase Height for longer documents
Optional: Use full-width Confluence layout for maximum viewing space
This ensures the entire document is properly displayed.
Cause: Your Confluence instance may be blocking external embeds.
Fix:
Ensure https://docs.google.com/ is added to the Confluence allowlist (admin setting)
Confirm firewall or security tools aren't blocking Google Docs
Refresh after authentication prompts
Cause: The app may not have rendered yet, or you pasted a non-standard link.
Fix:
Ensure you’re pasting the full document URL from the browser bar
Wait a moment for the automatic macro creation
Try reloading the page editor
Cause: Google Drive permissions restrict access.
Fix:
Google controls visibility, not Confluence
In Google Drive, confirm the user has at least View access
Avoid “restricted to myself” settings when collaborating in Confluence
Check the app documentation or reach out via the Atlassian Marketplace support link. ikuTeam support can help diagnose authentication, permissions, or layout problems quickly.
Yes. When you embed a Google Doc using the Google Docs for Confluence app, any changes made in Google Drive update instantly inside the Confluence page. There is no need to re-embed or refresh links.
Visibility is controlled entirely by Google Drive permissions.
Users must have access to the document in Google Drive and must be authenticated with their Google account in the browser. If they can open the doc in Google Drive, they can view it in Confluence.
Yes. Every viewer must sign in with a Google account so the app can verify permissions.
Confluence does not bypass or override Google Drive security settings.
Absolutely. Each time you paste a Google Docs URL, the app creates a new macro. You can embed multiple documents, each with its own layout settings.
No. Publishing to the web is only required for iframe/HTML embeds, and that method makes documents publicly accessible. With the ikuTeam Google Docs for Confluence app, you only paste the URL, and permissions remain private and secure.
No. The document stays in Google Drive. The app shows a live embedded version, but never stores or copies the file inside Confluence. This ensures full compliance with your organization’s storage and governance policies.
Yes, if they have edit permission in Google Drive. The embedded view includes optional toolbars so editors can write, comment, and format content right inside the Confluence page.
Embedding Google Docs inside Confluence is one of the strongest ways to keep documentation, collaboration, and decision-making in a single shared space. But not all embedding methods deliver the same security, speed, or reliability.
Here’s the quick recap:
Pasting the Google Docs URL is fast and permission-safe, but it opens in a new tab and doesn’t display inside the Confluence page. Good for quick references, but not ideal for real collaboration.
It works, but only if your admin enables HTML.
It also requires publishing the Google Doc to the web, which makes the file publicly accessible, meaning a major security downside for most teams.
Maintenance is manual, layout control is limited, and the experience is inconsistent.
The dedicated ikuTeam app provides the cleanest and most modern workflow:
Paste a URL, and it embeds instantly
No publish-to-web required
Google Drive permissions fully enforced
Real-time editing directly inside Confluence
Layout controls for width, height, toolbars, headers, and more
Zero storage inside Confluence (file stays in Google Drive)
For teams who want the safest, fastest, and most future-proof way to embed Google Docs in Confluence, the Google Docs for Confluence app is the recommended approach.
If your team relies on Google Workspace and wants a unified workflow for Docs, Sheets, and Slides, all embedded, editable, and permission-safe inside Confluence, we strongly recommend reading: Confluence + Google Drive Integration: The Practical Guide to Working from One Source of Truth