One channel, shared by everyone who needs the files
A DocEvent channel isn't a point-to-point pipe — it's a shared route. Create it once, invite as many members as you like, and every file sent in is delivered to every member allowed to receive it, each on an endpoint they choose and manage themselves.
Get started for free — channels are free during beta.
How a shared channel comes together
Three steps, and only the first one is yours.
1
Create the channel
A channel is a named route for one kind of file flow — invoices, orders, data feeds. Create it in the console and attach your own send or receive endpoint to it.
2
Invite one member — or many
Invite people by email or DocEvent username. Each invitee joins the channel on their own DocEvent account — there are no shared logins and you never exchange credentials.
3
Everyone connects their own way
Each member attaches the endpoint that suits them — an S3 bucket, HTTPS uploads, email, FTP or SFTP push, a webhook, or a folder on their own server via the Filerouter agent — and manages it themselves.
Every receiver gets every file
Sending into a channel isn't addressing a single recipient — the channel delivers a copy of the file to each receiving member, over whatever endpoint that member configured.
Files sent in
By one member or many — S3, HTTPS, email, or a watched folder.
Shared channel
Member A receives to their SFTP server
Member B receives to a folder on their own server
Member C receives to their webhook
- Every file sent into the channel is delivered to every member permitted to receive — one upload, many deliveries
- Many members can send into the same channel; their files all flow through the same audited route
- Senders and receivers can be mixed freely: one-to-many broadcast, many-to-one collection, or many-to-many exchange
- Each delivery is queued, retried and logged separately, so one slow receiver never holds up the others
Each member, their own rules
Membership is governed by permissions, and endpoints belong to their members — how each member sends or receives is up to them, within the permissions you grant.
- Per-member permissions decide who may send into the channel and who may receive out of it
- A member can be send-only (they can submit files but see nothing else), receive-only, or both
- Each member chooses and manages their own endpoint type and credentials — you never configure their side
- Both sides see the delivery status and audit trail for the files they exchange
What teams share channels for
Anywhere the same files need to reach more than one place — or come from more than one place — a shared channel does the wiring.
Exchange files with partners
The classic case: you keep one end of the channel, a customer or trading partner keeps the other. They pick where their files go and change it whenever they like — your only job was the invite.
Migrate or upgrade a server
Switching from version 1 to version 2 of a system? Add the new server as a second receiver and both get every file. Run them side by side for as long as you need, then remove the old endpoint — no big-bang cutover, no missed files.
Replicate production to staging
Feed the same production files to more than one environment. Add staging (or a test rig, or an analytics store) as extra receivers on the channel and each gets its own copy of every file — real data in staging, without touching production.
Broadcast to many recipients
Distribute price lists, catalogues, reports or configs to every subscriber at once. Publish one file into the channel and each member receives it on their own endpoint — FTP, folder, webhook or inbox.
Ready to pick your endpoints? Browse all channel integrations — any source, any destination, in any combination.