Confluence Joint Venture Sync: One Space, No Full Access

Two companies, one joint venture, and neither wants to open its front door to get shared documentation working.

Joint ventures and consortiums generate a lot of shared paperwork — engineering specs, schedules, permits, safety logs — but the JV itself isn’t a company with its own IT department. It borrows infrastructure from whichever partner is willing to host it, or it gets none at all, and the documentation ends up scattered across whoever happened to write it down first.

The obvious fix is guest access: one partner invites the other’s project team into its Confluence Cloud site as guests. But guest accounts, once security reviews them properly, don’t stay scoped to just the JV space — they sit inside an instance that also holds unrelated spaces neither company wants the other looking at. Legal teams on both sides slow-walk or reject the request, and the JV team can’t wait months for a security review to finish. So they default to something neither company actually uses for its own documentation — a shared SharePoint site or a Google Drive folder — which solves “somewhere to put files” but pulls the JV’s records outside of wherever either parent company’s real knowledge base lives. That’s the gap Space Sync for Confluence closes.

What this looks like in practice

Halvorsen Energy, a Nordic offshore wind developer, and Meridian Marine Construction, a marine and subsea engineering contractor, form a joint venture — Kestrel Point Offshore Wind JV — to build a 38-turbine wind farm over a 30-month construction program. The JV project team is 22 people, 11 seconded from each company, and it needs one current space covering engineering specs, permitting correspondence with the regional Maritime and Coastal Authority, the construction schedule, and the HSE incident log.

Both companies already run their own Confluence Cloud site. Halvorsen’s instance also holds spaces for three other offshore projects it’s running with different marine contractors, some of them direct competitors of Meridian. Meridian’s instance holds engineering work for other energy developers that compete with Halvorsen. Legal at both companies reviews the guest access request and rejects it inside three weeks — not because either side distrusts the other on Kestrel Point specifically, but because guest access would expose unrelated client relationships neither company is willing to risk.

The JV project office falls back on a shared SharePoint site, since it’s the fastest thing both sides can agree to use. That gives the team a common folder, but not a connected one. Halvorsen’s engineers still maintain the live specs in their own Confluence space, Meridian’s HSE team still logs incidents in theirs, and someone has to remember to re-upload the current version to SharePoint every time something changes. Within a month, three copies of the same documents exist, and none of them are reliably the current one.

What breaks without cross-site sync

The construction schedule diverges — Halvorsen’s engineers update the master timeline in their own Confluence space, but the SharePoint copy lags days behind, so Meridian’s site supervisors sequence barge deliveries against an outdated version.

HSE incident reports filed by Meridian’s marine crews sit in Meridian’s own Confluence tracker before anyone copies them to SharePoint, so Halvorsen’s safety officer learns about a near-miss after the next site walk instead of before it.

Permitting correspondence with the Maritime and Coastal Authority gets logged in whichever company’s Confluence handled the submission, and the other company’s compliance lead has to email and ask for a copy instead of checking the shared space.

The 22-person steering committee spends the first 10 minutes of its biweekly meeting reconciling which version of the risk register is current, because the Halvorsen copy, the Meridian copy, and the SharePoint copy have already drifted.

A new subcontractor joining the JV project team can’t get one link to everything — onboarding means separate SharePoint and Confluence logins across two companies, and a week of asking where things actually live.

Over a 30-month build, that gap compounds. The SharePoint site turns into its own stale archive, and the “real,” current version of every document stays locked inside whichever company’s Confluence instance produced it — invisible to the other side of the JV.

How Space Sync for Confluence fixes this

Instead of granting guest access or exporting to a shared drive, each company designates a Kestrel Point JV space inside its own Confluence Cloud site, and Space Sync for Confluence keeps the two in sync. Halvorsen’s team keeps working in their own instance under their own permissions; Meridian’s team does the same in theirs. The JV space looks identical on both sides because it’s synced, not because either company let the other one in.

An admin on either side sets the sync scope once — which spaces, what schedule — and updates flow automatically from there, or on demand when a workstream owner needs a push before a deadline. Page content, titles, attachments, and macros all make the trip, so a Gantt macro on the schedule page or a PDF attached to a permit application arrives intact, not flattened into a static export.

Key capabilities for this scenario:

• Cross-site sync between separate Confluence Cloud instances → each company’s tenant boundary stays closed while the JV space mirrors identically on both sides
• Scheduled or on-demand sync → the construction schedule and HSE log update automatically, or immediately after an incident report goes in
• Attachment and macro sync → permit PDFs, engineering drawings, and schedule macros carry over as working content, not screenshots
• Bulk sync → the full JV documentation set — specs, permits, HSE, schedule — syncs in one setup pass instead of space by space
• No guest licensing or cross-tenant access grants → satisfies both legal teams, since nobody gets a login into the other company’s instance

What changes for your team

Before Space Sync for Confluence, the biweekly steering committee opened with a version check — whose risk register is current, whose schedule reflects this week’s barge delivery, and which SharePoint upload is actually the latest. That reconciliation routinely ate the first 10 minutes of a 60-minute meeting, for the length of a 30-month build.

After Space Sync for Confluence, the JV space is the same document on both companies’ Confluence sites, because it’s synced automatically. The steering committee meeting starts with status, not archaeology. When Meridian’s HSE team logs an incident Tuesday morning, Halvorsen’s safety officer sees it that afternoon — no email, no waiting for the next SharePoint upload.

Built for the people running this

Partner/Client Collaboration Lead — you’re the person Halvorsen or Meridian calls when the shared schedule doesn’t match what the other side is working from. Space Sync for Confluence keeps both companies’ JV spaces identical across the organizational boundary, without asking either team to change how they work inside their own Confluence instance.

Multi-site Confluence Admin — you manage your company’s Confluence Cloud instance and you’re the one legal calls before approving any cross-company access request. Space Sync for Confluence gives you a sync you can scope and audit, instead of a guest access grant you have to defend.

A joint venture doesn’t need a shared instance — it needs a space both companies can trust without unlocking the rest of the building.

Ricksoft, Inc., is ISO/IEC 27001:2022 certified. Space Sync for Confluence complements your Confluence Cloud permissions model rather than replacing it, syncing a defined space across company boundaries instead of opening your instance to guest accounts.