Prepare a client-facing proposal, choose the right sharing permissions, test recipient access, and keep a clear record of the version you sent.
A proposal is ready to send when the client can open the intended version and see the information meant for them. An internal working document can contain supplier notes, unfinished pricing discussions, or details about another customer. A polished cover does not make that document ready to share.
Use a short handover checklist before putting a proposal link into an outreach conversation. The workflow below is editorial guidance for agency teams using document-sharing tools; it does not describe an AllProfiles file-sharing feature.
1. Create a separate client-facing version
Keep the internal master and the external deliverable separate. Build the client copy from the information the recipient needs to evaluate the offer, rather than sharing an entire working folder.
Illustrative example: an agency prepares ExampleCo-Proposal-v03.pdf for one prospective client. The filename, company, and workflow in this article are examples, not customer records.
| Include in the client copy | Keep in the internal workspace |
|---|---|
| Approved scope and deliverables | Supplier negotiations and internal cost notes |
| Client-facing price and billing schedule | Draft pricing calculations and unapproved alternatives |
| Assumptions, dependencies, and next steps | Unresolved comments and internal review discussions |
| The relevant contact and version date | Other clients' names, documents, and account details |
Open the exported file itself. Check its pages, links, and attachments rather than assuming the export matches the editor. Give each approved revision a clear version identifier so a later message can refer to the exact document.
2. Remove information properly before exporting or sharing
Delete unnecessary material from the source document and check the output again. If an existing PDF needs sensitive text or images removed, use an actual redaction workflow. A colored rectangle placed over text is not the same operation as removing it.
Adobe's documented workflow marks content, applies the redactions, continues with sanitization, and saves a new file. Sanitization addresses hidden information such as comments, metadata, and hidden layers. The tutorial specifies Acrobat Pro, Premium, or Studio, so do not assume every Acrobat edition provides these tools. Follow the instructions for your available software and inspect the saved result. Adobe's redaction and sanitization tutorial
Preserve the internal original separately. Only place the reviewed external copy in the location you will share.
3. Choose the audience and permission deliberately
For a proposal intended for one prospect, start with named recipients and viewing access unless they need to edit. Check the actual settings before copying the link.
In Google Drive, files and subfolders inherit access from their parent folder. A file cannot simply give someone less access than the parent grants. Check the containing folder and group access; use a suitable separate location or a limited-access folder where supported. Work or school administrators can also limit external sharing. Google Drive sharing guidance
In Microsoft's sharing model, an Anyone link is transferable: someone receiving a forwarded link can use it. A Specific people link works for the specified users, who must authenticate as those users. Choose the link type that matches the audience, and remember that a person may also have access through another permission. Microsoft's sharing-link types
Viewing access is not a promise that content cannot leave the document. Google documents controls for downloading, copying, and printing, but also explains that they cannot stop people from sharing the content in other ways. Treat these as controls with limits, not a substitute for removing internal information. Google Drive sharing limits
4. Test the exact link as the intended recipient
Your own successful visit proves that your account has access. It does not establish what the client will see.
Ask the intended recipient to confirm access using the exact email address granted permission. An approved reviewer account can help test the workflow beforehand, but its successful access does not prove that the client can open the link. Check the document version, the intended viewing or editing permission, and whether the link exposes an unrelated folder.
A signed-out browser is useful for checking whether a link opens publicly. It is not a complete test of named-recipient access: a restricted document asking an anonymous visitor to sign in may be behaving correctly. If access fails, inspect the recipient address, link type, folder permissions, and organization restrictions before changing the audience to Anyone.
5. Make the handover unambiguous
Record enough information to resolve a later question without searching through several conversations. Keep private sharing URLs in the approved workspace rather than a public reporting sheet.
Illustrative handover record:
| Field | Example |
|---|---|
| Deliverable | ExampleCo proposal, version 03 |
| Audience | The named client contact |
| Permission | View |
| Owner | The assigned account manager |
| Next check | After the client's proposal review |
The accompanying message can be simple: “Here is version 03 of the proposal, including the scope, monthly price, and proposed start date. Please review it before our call. If the link asks you to request access, tell me which email address you are using.”
6. Review access when the work changes
When a proposal is superseded, a contact leaves, or the engagement ends, review the access routes you created. Check links, direct recipients, groups, and parent folders. Creating a narrower new link does not establish that older access has disappeared.
Remove access that is no longer needed and keep the current deliverable clearly identified. Revoking access does not recall a copy someone already downloaded or captured. The dependable habit is to share a reviewed client copy with a deliberate audience, verify the recipient experience, and keep a record of the handover.
