
Secure File Sharing in Companies: Managing External Access

Collaborating on files is part of everyday working life. Project documents, proposals, and coordination need to reach the right people, including those outside the company. Cloud services make this easy. What is less obvious is who can actually access the files after they are shared and how long this access remains in place.
For CISOs, information security officers, and awareness managers, this presents a shared task: secure collaboration requires appropriate settings and understandable decisions. This article highlights which questions should be clarified before sharing, where technical boundaries are necessary, and how handling access rights can be effectively integrated into awareness efforts.
A message addresses someone. A link can grant more permissions.
When sharing, two things must be distinguished: to whom is the message sent, and who is authorized by the link contained within it? The selected email address does not automatically restrict access to the file.
For SharePoint and OneDrive, Microsoft differentiates, among others, between links for anyone, members of your own organization, and explicitly selected people. An "Anyone" link can be forwarded and requires no sign-in. In contrast, a link for specific people requires authentication as an authorized person. Organization-wide links are also not restricted to the colleagues originally addressed. Microsoft describes the exact functionality in its documentation on sharing links.
The editorial takeaway for awareness work is: convey the meaning of the available options, not just the action of clicking "Share." Employees should be able to distinguish whether they are creating access for designated individuals or distributing access that can be forwarded. The company's internal policy must then clarify which variant is permissible for which content.
Secure boundaries belong in the configuration
Training should not have to carry the burden of choices that the company fundamentally wants to rule out. Therefore, work with those responsible for collaboration systems to define where external sharing is permitted and which content remains excluded from it.
In SharePoint, settings at the organization and site levels work together; if settings differ, the more restrictive one applies. For confidential information that should not be shared externally, Microsoft recommends appropriately isolated areas. This is a documented capability of this system, not a statement about your company's configuration. The overview of external sharing explains these relationships.
A clear division of roles is ideal for internal coordination: information owners determine the permissible group of recipients, system administrators implement the technical options, and the awareness team makes the remaining decisions understandable. Where a required workflow is missing, there should be a designated point of contact. Otherwise, the rule remains abstract while employees still need to share a specific file.
Turning "Please share carefully" into a verifiable decision
The following questions are an editorial decision-making guide, not an additional approval process that must look identical in every company. Use them to check existing rules for clarity and completeness:
Recipients: Are individual people, a defined group, or anyone with the link authorized? Does this group match the content and the purpose?
Scope: Is a single file needed or an entire workspace? What other content becomes accessible via the selected location?
Permissions: Is viewing or commenting sufficient? Who actually needs editing rights, and who is allowed to grant permissions to others?
Duration: How does the responsible person recognize that access is no longer needed? Is there an appropriate technical expiration date or a mandatory trigger for review?
Responsibility: Who answers inquiries and reviews sharing permissions when there is a change in projects or personnel?
Particularly important is the difference between an individual file and its parent folder. Google explains for Drive that folder permissions apply to all contained files and subfolders. An individual file cannot simply be given narrower permissions than the parent access; instead, the storage structure must be designed accordingly. The Drive Help on access management also shows the different roles. This is a concrete reason to review your own storage structure, not a universally valid menu path for other systems.
Awareness makes the remaining decisions discussable
For communication, it is worth focusing on the tools actually in use: What options do employees see, what do they mean, and when do they need to ask for clarification? A generic presentation on confidential data does not yet answer these questions. In security awareness onboarding, such operational workflows should be made understandable before the first independent use.
Alongside instruction on the specific tool, discussions about security decisions also have their place. What The Hack! is a serious game for security awareness: employees discuss security scenarios and agree on an answer as a team. Their common goal in the game is to catch the hacker. The What The Hack! awareness platform thus provides a complementary framework for collectively addressing security topics.
For the initiative described here, sharing policies, system configuration, and instruction on your own tools remain distinct tasks. A game is one building block of awareness work, not an authorization concept. It is precisely this division of tasks that aids planning: not every problem requires more training, and not every necessary explanation can be replaced by a setting.
Collaboration ends – does access end as well?
Secure sharing involves a second decision after setup: is access still required? Appoint a responsible person and establish a review trigger tailored to the work's purpose. A completed assignment or a change in the project team should at least prompt a review of existing permissions.
An expired link does not automatically mean that access has been completely revoked. Microsoft points out that other permissions may continue to persist despite link expiration. For revoking external access, the documentation cites removing permissions or deleting the corresponding link, depending on the sharing type. Therefore, a review should look at the actual remaining access and not just the date of a single link.
Time limits must also match the service and account type being used. Google, for example, describes prerequisites and limitations for expiration dates. Therefore, do not adopt a blanket deadline into training materials before system administrators have verified whether and how it is implemented in the intended workflow.
What actionable reporting should show
As an editorial recommendation, CISOs should consider two perspectives separately: is the technical sharing landscape manageable, and do employees understand their decisions? A completed training module does not answer the first question. A technically restrictive setting does not answer the second either.
For an inventory review, you can first record which areas were examined, whether external access has a traceable purpose and owner, and what unresolved questions arise from this. A report should state its coverage: an audited department does not equate to an audited organization. A declining number of shares would also not, in itself, be a success if necessary collaboration simply migrates to other channels.
On the awareness side, recurring questions regarding comprehension serve as a starting point for better explanations. Whether this leads to fewer unauthorized accesses must be investigated separately. The article on measuring security awareness reliably explains why participation, learning, and operational outcomes should not be equated.
Conclusion: Clear sharing options facilitate responsible collaboration
Sharing files securely is a joint design effort. The authorized group of recipients must match the purpose, the technical scope must be limited, and the end of collaboration must be accounted for. Employees need understandable options and support when uncertain. The most sensible next step is therefore an alignment: do your sharing policies, actual system settings, and explanations for employees match?
Sources

Your Contact Person
Thorben Steenmanns
Chief Gaming Officer & Head of Sales
What if your next awareness training remained a positive experience in the minds of your colleagues?
A vibrant security culture is the most powerful defense against hackers. I help you build yours—using our serious business game What The Hack! for cybersecurity, data protection, and compliance.


