Home/Process library/Sharing and receiving through a client hub
Process library · EngineeringSharing and receiving through a client hub
Approved documents appear on the client’s hub, and the client gets a mail with a link. What the client has to send, they upload into the placeholder waiting for it, and it lands straight in a review in M-Files.
See the flow HubShare and M-Files
In short
In this blueprint an engineering firm shares documents with its client through a hub (HubShare) connected to M-Files, instead of by mail. An approved revision is moved to publish and appears on the client’s hub; documents in review are never visible there. The project manager then sends a notification from the master document list: the client receives a mail that there are new documents on their hub, with a link. The other way round, documents the client must send wait as placeholders open for upload. The client uploads the file on the hub and fills in their own review number. M-Files picks it up, and a reviewer gets a task to check it: OK, or back to the client for a new upload. SoftAdvice built and documented the process.
Documents go both ways, and mail loses track of them
The client mails its specification to three people. Two weeks later, nobody has checked it and two versions are in circulation.
An engineering firm sends drawings and calculations to its client, and the client sends specifications and test procedures back. Both sides want to know what they have and what is still missing.
By mail, attachments go to three people, versions cross each other, and a received specification sits in an inbox instead of in a review.
- Only approved revisions on the hub
- A mail with a link when there is something new
- The client uploads into the waiting placeholder
- Every received document goes into review
What happens on the way out and on the way back
Out: approve, publish, notify. Back: upload, pick up, review.
After approval
Publish
The approved revision appears on the client’s hub.
When a batch is ready
Notify
The client receives a mail with a link to the hub.
When the client delivers
Upload
The client uploads into the placeholder that waits for it.
Right after
Review
A reviewer gets a task: OK, or back for a new upload.
From approved document to reviewed answer, step by step
People decide what to share and whether what came back is right. The hub and M-Files move the files and record every step in the history.
Publish to the hub
An approved revision is moved to publish and appears on the client’s hub. Documents in review stay hidden.
Notify the client
From the master document list, the project manager sends the notification: a mail that there are new documents on the hub, with a link.
Upload by the client
On the hub, the client opens a placeholder that is open for upload, adds the file and fills in their own review number.
Pick up
M-Files picks up the upload by itself, marks the document as added and sends a review task to the reviewer.
Review what came in
The reviewer marks the document OK, or sends it back to open for upload so the client can deliver a new version.
One route out, one route back
What goes out is approved first. What comes in is reviewed first.
Document to the client
Document from the client
From attachments to a shared place
The client always finds the latest approved revision, and what the client sends is checked before anyone builds on it.
Before
- Attachments to several people
- Drafts sent by mistake
- Client files stuck in an inbox
- Nobody checks what came in
Now
- One hub per client
- Only approved revisions shared
- Uploads land in their placeholder
- A review task for every received file
M-Files, HubShare and the Engineering Pack
Configured and documented by SoftAdvice.
Client hub with HubShare
A secure place per client, connected to M-Files, for documents going out and coming in.
Placeholders open for upload
What the client must send waits as a placeholder on the master document list.
Questions about this blueprint
Does the client need an M-Files licence?
No. The client works on the hub with their own login; M-Files stays your internal system.
Which documents can the client upload?
The ones you prepare as placeholders open for upload, for example specifications and test procedures. You decide this per document type.
Can suppliers use the hub too?
In this blueprint the hub serves the client. A route for suppliers can be set up the same way, with its own placeholders and review.
How do your clients get your drawings today?
In a one-hour demo we publish a drawing to a client hub and receive a document back into review.
