Files connected to people
Keep the people behind a file in view without granting access by association.
Associate a file with a customer, contact or employee so the working relationship is clear while sharing remains a separate choice.
Who a document concerns is different from who may read it.
A file name may explain what a document is, but not the relationship behind it. Drive associations connect supporting material to customers, contacts and employees. They help organize the context without turning a business relationship into an access grant. A private budget may concern the same customer as a proposal while remaining intended for different people.
Choose the record that explains the relationship.
Use customer, contact or employee associations according to what the file concerns. Distinguish a company relationship from a particular person's involvement. This is a business context feature rather than an invitation mechanism, so the selected record should explain relevance, not be used as a workaround for sharing with someone whose access has not been checked. A linked record therefore remains an association, not a file-access grant.
- Customer, contact and employee associations
Review access as a separate action.
Connecting a record does not add that person to file grants and does not make the file company-visible. Choose private, selected-person or company access explicitly. Folder authority still applies. The same distinction matters if the linked record describes an employee: being the subject of a file is not itself permission to read internal material.
- Associations without implicit sharing
Keep context and delivery decisions understandable.
Use the association to orient internal colleagues, then review the material and audience before external delivery. A version-specific external link is a separate sharing mechanism and does not expose the internal file conversation. When a customer contact changes, review both the relevance of the association and the continuing suitability of existing shares rather than assuming either updates the other.
- Separate context, internal grants and external shares
A concrete workflow
Identify
Determine whether the file concerns a company, contact or employee.
Associate
Connect the appropriate record to explain the file's business relationship.
Review permissions
Choose who needs to read or edit, including the parent-folder boundary.
Handover
Review the intended version separately before creating an external link.
An illustrative working example
Illustrative scenario: a contact-specific proposal
A team links a proposal to the customer company and the contact who discussed the requirements. The file remains private until the owner grants the internal review team access. A later external link shares the reviewed version; the contact association did not create that link or permission. The pilot tests the distinction with one document and asks a colleague to explain who is related, who can read internally and what an external recipient receives.
Questions about this topic
Does a customer association give the customer access?
No. It records relevance to the customer. File sharing, internal grants and external links remain separate choices.
Can an employee be associated without seeing the file?
Yes. An employee association describes whom the file concerns, not who has permission to inspect its contents.
Does this copy the whole CRM record into Drive?
Do not treat the association as a full data replication feature. It connects records for context while each surface retains its authority.
What if the contact changes?
Review associations and existing shares deliberately. Changing contextual relevance is not automatically the same as removing or creating access.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Application concept: Review a HubSpot company reference as file context while keeping customer association separate from file access.
Salesforce
Application concept: Plan a mapping between Salesforce contact identifiers and reviewed file associations without granting the contacts workspace membership.
Notion
Application concept: Use a Notion project brief to identify which customer and employee relationships should be recorded for selected files.