Delivery partners

A delivery partner is an outside organisation that exchanges files with your project continuously — a contractor, a consultant, a supplier post-award. Instead of emailing files back and forth, you give them a delivery space: their own portal onto exactly the folders you choose.

This is different from a share link (one document, one recipient, expiring) and from a tender (a structured bid with a checklist). A delivery space is a standing, two-way exchange.

Inviting a partner

On the project’s Partners page, press Invite a partner and fill in:

• Organisation — picked from (or added to) your organisation list.
• Email — the first person at the partner; they’ll claim the space and become its first member (you can add more people afterwards — see People at the partner).
• Title — what the space is called on both sides, e.g. Level 12 — Fit Out.
• Presented as — the client name the partner sees (white-label: they see the client’s brand, not ddx, unless you choose otherwise).
• Brief (optional) — a short note shown at the top of their Files view.

The partner receives an email — “You’ve been invited to a file exchange” — with a claim link. The link is also copyable from the Partners page, so you can send it yourself. Claiming it, they sign in (or create a sign-in) and land in their delivery space. Until they claim, the row shows invited; you can resend a fresh link or revoke the invitation at any time.

Choosing what they see

Each partner row has a folder access editor — tick the folders that make up their slice of the tree:

• A ticked folder covers its whole subtree.
• Inside those folders they see Shared, Published and issued documents — never anyone’s WIP, never unissued drafts, and never a folder you didn’t tick. The rest of the tree is structurally invisible to them — with one deliberate exception: the parent folders above a granted one show in their portal as greyed, context-only waypoints (name only, no files, no uploads), so a partner with folders in several packages can tell which 00_Reference belongs to which package.
• Their own uploads are always visible to them, whatever the state.
• Need to share most of a folder — a package minus the other partners’ WIP folders, say? Use ⋯ → Share folder… in the file browser and untick what they shouldn’t get; see Sharing with delivery partners.

The folder list is empty?

The project predates the filing standard and has no tree yet. A workspace admin can instantiate trees for existing projects with one button — see Filing standards.

People at the partner

A partner organisation is rarely one person. The People panel on the partner’s detail page manages everyone at that organisation who can enter the space — add a colleague by email, and they get their own claim link and their own sign-in. Each person carries a role, Drive-style:

Role	Can do
Viewer	Browse and download everything the space can see.
Uploader	…plus upload files, and create subfolders inside the granted folders.
Editor	…plus add versions, hand documents over (issue), transmit them to your team, and delete their own un-issued files (soft — the file lands on your pending-deletions queue).

You can change a person’s role, resend their invitation, or revoke just that person at any time — revoking one member never touches the rest of the space.

What the partner can do

In their portal (see The supplier portal for the full tour) a partner can:

• Browse and download what you’ve issued, shared or transmitted to them.
• Upload files into their granted folders. Uploads with a valid container name register as controlled documents (starting at WIP — private to them until they hand them over); anything else files as a descriptive draft.
• Hand work over — issue their own document at a suitability, which is when your team first sees it, marked from partner.
• Acknowledge transmittals you issue to them.
• Keep company details current — legal name, address, contacts.

Emails the partner receives

When	Email
You invite them	You’ve been invited to a file exchange with the claim link.
You issue/share files their way	A file was issued to you with a link to their space.
You send a transmittal	Transmittal RCT-TX-0001 with the acknowledgement ask.

All of it is branded with the presented-as name, and replies go to the inviting operator.

Housekeeping

• Revoke ends access immediately (their uploads stay on the project).
• One organisation can hold several spaces on one project (e.g. separate packages) — each has its own folder access.
• Everything a partner does is audited and feeds the exchange register with an external actor label, so provenance survives.