Sharing a Macro document is more than copying its title into a conversation. The surface where you mention it can change access. Review who should read, edit or receive the material before using channel or email mentions as a shortcut.
Choose the intended audience
The document guide describes owner, editor, commenter and viewer roles, plus sharing and public-link options. Start with the smallest audience that needs to do the work. An internal draft, a client-approved proposal and an external reference file may need different access arrangements.
For an illustrative customer project, the delivery team may need editing access while the customer should only read an approved version. Write those roles down first. The same document name appearing in both conversations does not mean both groups should have the same permissions.
Understand the effect of an email mention
Macro’s mentions documentation explains that mentioning a document or file in an email can set it to view-only for anyone with the link, with a confirmation. If the sender cannot change sharing, Macro warns that recipients may lack access. Mentioning a person adds them to CC.
| Action | Review point |
|---|---|
| Email a document mention | Check the link-sharing confirmation and recipients |
| Mention a file in a channel | Check current channel membership |
| Mention a person inside a document | Do not assume they were notified or granted access |
| Send a client-facing version | Check the actual content and permission as a recipient |
Do not generalise file behaviour to every object
The mentions guide describes document and file sharing through channels, but treats contacts and company records differently: their sharing is determined by Teams. A CRM record mentioned beside a document therefore does not necessarily inherit the document’s sharing behaviour.
Keep a simple register for important customer material: owner, intended audience, link policy and replacement version. This is an operating aid, not a claim that a register is a required Macro feature.
Test from the recipient’s position
Use a harmless sample document and an account with the intended recipient’s access. Open the link outside the author’s session. Check whether reading and editing behave as expected, and whether an unsigned browser can access anything intended to be public.
Repeat after changing channel membership or replacing the document. An author who remains signed in can easily miss an access problem that affects a customer. Record the result and resolve the sharing setting before sending sensitive project material.
Make approved versions easy to identify
Label working drafts and approved customer copies clearly. Tell staff where the authoritative version lives and who can publish changes. A well-configured permission model is most useful when the recipient can also tell which document they are meant to rely on.
Mapping Document Journeys Before You Choose a Sharing Method
Before selecting a channel, a public link or a direct permission grant, it is worth tracing the full journey a document will take from creation to its final resting place. That journey typically crosses several distinct moments: initial drafting, internal review, stakeholder approval, external delivery and archiving or replacement. Each moment may involve a different group of people with different legitimate needs, and the sharing method appropriate at one moment may be actively inappropriate at another.
A practical way to conduct this mapping exercise is to write out each document's intended lifecycle in plain language before touching any sharing control. For a fictional illustrative scenario, consider an account team preparing a project scope document. In its earliest form, only the lead and their manager need access. During peer review, two colleagues join temporarily. After internal sign-off, a redacted version goes to the client contact, who needs to read but not alter it. Once accepted, a final version is archived and the working drafts are restricted so no one accidentally circulates a superseded copy. Each of those stages calls for a different permission state, and treating them as a single continuous sharing decision will eventually produce an access error, a version confusion or an unintended disclosure.
When mapping this journey, note separately the identity of the customer as an organisation, the identity of the individual receiving the document on the customer's behalf, and who inside your own team bears responsibility for each permission decision. Those three are often conflated. An individual contact at a client organisation may leave or change role, making their personal access link obsolete or misdirected. Responsibility for updating that access should be clearly assigned to a named internal person, not left as a shared assumption among the team.
Distinguishing Read, Comment and Edit Access by Practical Role
The distinction between viewer, commenter and editor roles is not merely administrative. Each role affects what a recipient can do to the document's content and, in some systems, what they can see of the document's history and metadata. When deciding which role to assign, frame the question around what task the recipient actually needs to complete, rather than defaulting to the most permissive option for convenience.
Viewer access suits any situation where the document is evidence, reference or a deliverable the other party is meant to receive without altering. A client reviewing a proposal does not need to edit it. Giving them editor access introduces risk that changes will be made without proper sign-off, that the document's accepted state will become ambiguous, and that version history will record external edits alongside internal ones in a way that complicates any later dispute about what was agreed.
Commenter access is appropriate when feedback is specifically invited and the receiver's input should be visible but not directly applied. This is a useful middle position for review cycles where the document owner wants to retain editorial control while gathering structured input. In an illustrative internal review scenario, a legal colleague asked to flag concerns in a contract summary should be a commenter, not an editor, so that the original text remains intact and any suggested changes are traceable as suggestions rather than silent alterations.
Editor access should be reserved for people with an active responsibility to maintain or complete the document. When more than one person holds editor access, it becomes important to establish whose edits take precedence, when the document is considered finished and who has authority to change sharing settings. Without those decisions, concurrent editors can introduce conflicting changes that are difficult to reconcile after the fact.
Evaluating Public Link Decisions Systematically
A public or anyone-with-the-link sharing setting is a qualitatively different choice from granting access to named individuals. Once a document is publicly accessible, access is no longer tied to a specific identity. You cannot know who has opened the link, cannot revoke access for a particular person without replacing the link entirely, and cannot audit individual viewing behaviour in the way that named-user access might allow.
Before enabling a public link, a team should be able to answer the following questions with confidence. First, does the document contain any information that should not be visible to an unidentified reader, including draft commentary, internal pricing notes, client names or operational detail that is sensitive outside its intended context? Second, is the link being used because it is genuinely the right access model for this material, or because it is faster than configuring named permissions? Third, if the link were forwarded or discovered by someone outside the intended audience, what would the consequence be, and is that consequence acceptable?
Where a public link is appropriate, for example a general reference document, a publicly available template or a non-sensitive resource meant for broad distribution, the decision should still be recorded. Note who made the decision, why public access was judged appropriate and whether the link should be reviewed or revoked after a specific trigger, such as the conclusion of a project or a change in the document's content.
Where a public link is used as a workaround because named-user permissions are cumbersome, that is a process problem worth addressing directly. The convenience of a public link does not reduce the sharing risk; it simply moves the effort of managing that risk to a later, less predictable moment.
Handling Channel-Based Sharing With Care for Membership Changes
When a document is shared through a channel or group context, its effective audience is determined by channel membership at the moment of access, not only at the moment of sharing. This distinction matters in any team environment where channel membership changes regularly, whether because projects close, staff change roles or external guests are added and later removed.
In an illustrative scenario, consider a document shared in a project channel that includes both internal staff and a client representative. If the project closes and the client representative remains in the channel, they retain whatever access the channel-based sharing confers. Conversely, if an internal team member joins the channel after the initial share, they may or may not gain access depending on how the system handles retrospective channel membership, and assuming they have access without checking is a source of confusion during handovers.
A practical discipline is to review channel membership alongside document access whenever a project milestone is reached. At project close specifically, it is worth checking which documents were shared through the channel, whether any of them contain ongoing sensitive information and whether the channel itself should be restricted or archived. This does not require a sophisticated system; a brief checklist item at project closure is sufficient.
When a document is replaced, for example when a working draft is superseded by an approved version, channels may still hold links to the old document. Recipients who follow those links will reach outdated material unless the old document has been restricted or clearly labelled. Updating the channel with a note about the replacement, and restricting the old version's access, closes that gap without relying on recipients to remember which version is current.
Designing a Lightweight Document Register for Client-Facing Material
A register does not need to be complex to be useful. For any document that is shared externally or that represents an agreed position with a client or partner, maintaining a short record alongside the document itself reduces the risk that access decisions become invisible over time.
A functional register entry for a single document might include the document's plain-language name and its purpose, the name of the person responsible for its accuracy and access settings, the intended audience described in terms of role rather than individual names, the current sharing method in use, and any planned review or expiry point. That is enough information for a colleague covering during absence to understand what the document is, who should have access and whether anything needs to change.
The register is most valuable when it is consulted before sharing decisions are made, not only after problems arise. When a new team member asks to share a client proposal, the register tells them whether a version already exists, who owns it and what access model was agreed. This avoids the situation where multiple versions of the same document circulate under similar names with inconsistent permissions, which creates genuine confusion about which version a client has seen and approved.
For teams that work with external parties on a recurring basis, the register also supports handover conversations. A colleague taking over an account can review the register to understand which documents are live, which are archived and whether any access arrangements are tied to individuals who may no longer be involved. That is a more reliable foundation for continuity than searching through past conversations for sharing links.
Conducting a Practical Acceptance Exercise Before Distributing Sensitive Documents
An acceptance exercise is a structured check, performed before a document is sent to its intended audience, that confirms the sharing configuration actually behaves as intended from the recipient's perspective. The principle is simple: do not rely on the author's view of the document to verify what a recipient will experience.
To carry out a basic acceptance exercise, identify the lowest-privilege account that should be able to access the document and use that account, in a separate browser session or on a separate device, to attempt to open the document. Confirm that the content visible matches what was intended for that audience, that no additional tabs, linked documents or embedded references reveal restricted information and that the actions available to the recipient match their assigned role. If the recipient should only read, confirm that editing controls are unavailable. If the recipient should not be able to download or copy, confirm that restriction holds in the session.
A second part of the exercise involves attempting to access the document from an account with no permissions at all, to confirm that access is appropriately denied to an unintended party. This is particularly important where documents contain information about one client that should not be visible to another, or where a document that was previously public has had its access restricted.
Documenting the result of this exercise briefly, even a single line noting who performed it, when and what they confirmed, creates a record that is useful if a question about access arises later. It also creates a natural moment to catch configuration errors before they reach the intended recipient, when correction is straightforward rather than requiring a potentially awkward follow-up message.
Managing Access When Personnel or Relationships Change
Access decisions made at the start of a project do not automatically remain appropriate as circumstances change. Staff turnover, role changes, the conclusion of a contract and the departure of a client contact all create moments where previously granted access may become misaligned with current intent.
Where a named individual held editor or viewer access and that individual leaves either organisation, the access grant tied to their account may persist unless it is actively reviewed and removed. In an illustrative scenario, a former employee of a supplier who was given viewing access to a shared specification document during a project may technically retain that access after their employment ends, unless the document owner reviews and revokes it. Building a prompt to review external access into offboarding procedures, or into contract renewal and close-out processes, addresses this without requiring constant monitoring.
When the nature of a relationship changes, for example when a client moves from a pilot engagement to a full contract, or when a partnership arrangement is renegotiated, the documents shared during the earlier phase may no longer be appropriate to maintain in their current access state. Some may need to be archived, some restricted and some replaced with updated versions that reflect the new terms. Treating access review as a routine part of relationship transitions, rather than a response to a problem, reduces the chance that outdated material remains accessible when it should not be.
For internal personnel changes, the most immediately consequential situation is when the document owner or the person responsible for a sharing decision leaves the team. If no one else knows what access arrangements were made, or who the external recipients are, responding to a later access question becomes unnecessarily difficult. Ensuring that ownership of important documents is assigned to a role or a team rather than a single individual, and that the register is updated when ownership transfers, provides continuity without depending on any individual's memory.
Effective document sharing rests on a small number of decisions made clearly and reviewed at the right moments: who needs what access at each stage of a document's life, whether the sharing method in use actually reflects that, and who is responsible for keeping those decisions current as circumstances change. Getting those decisions right before distributing material is consistently easier than correcting a sharing error after the fact.
Related guides
- Macro Team Memory: Scope, Sharing and What to Verify
- Macro Tasks vs CRM Pipelines: Pick the Right Board
Comparing business systems? Explore Sysevo document vault or book a Sysevo demo against the same requirements. This is an independent Sysevo editorial guide based on the linked vendor documentation, reviewed 2 November 2026. Examples are illustrative; no hands-on vendor test or guaranteed result is claimed. Sysevo publishes this guide and sells its own software.
For current Sysevo subscriptions and usage options, compare plans and pricing.



