Macro's channel-based sharing model fundamentally changes how client files remain accessible or become restricted during project closure and staff transitions. This guide walks you through the mechanics of file access in Macro, tests you should run before relying on the system for sensitive client work, and decisions that affect both active collaboration and offboarding workflows. Understanding the difference between channel membership, document ownership, and public links is essential for home-services teams managing contractor portfolios, inspection reports, and customer estimates.
How Channel-Based Sharing Controls Access to Client Files
Macro organizes file access through channels rather than granular per-document permission dialogs. When you mention a document, task, or file in a channel message, that content becomes accessible to all current and future channel members. If a person is added to a channel, they gain access to the entire history of shared materials in it; if they are removed, access to those materials ends. This is a critical operational difference from systems where files are shared individually and removal requires separate actions for each item.
According to Macro's permissions documentation, "When someone joins a channel, they can see all messages from the beginning, not just messages sent after they joined. They also gain access to everything that was @mentioned in the channel (docs, tasks, files, etc.)." This retroactive visibility applies the moment membership changes. For a home-services business managing multiple concurrent projects, this means a new team member onboarded to a channel immediately sees completed projects, closed jobs, and historical client communications shared within it. Conversely, removing someone from a channel immediately revokes access to all materials mentioned there, but not to materials they may have accessed individually before removal or that exist outside the channel context.
The system distinguishes between channel types. Team channels are discoverable by all team members and can be set to auto-add new hires. Private channels are visible only to explicitly added members and do not appear in team search. For client work, this distinction matters: a private channel reserved for an active project ensures only assigned staff see the files, while moving to a team channel makes historical records visible to future hires, which may or may not align with your data retention and privacy policies.
Document Ownership and Sharing Levels
Beyond channel membership, documents in Macro support individual sharing with four access levels: owner, editor, commenter, and viewer. These operate alongside channel-based access. If a document is owned by a departing employee and mentioned in a private channel, removing that employee from the channel does not automatically change the document ownership or transfer it to another person. The document remains owned by the original creator unless explicitly reassigned before their departure.
According to Macro's documents documentation, "Documents use the standard access levels: owner, editor, commenter, and viewer. You can share documents with people outside Macro by using their email address, or by giving them a URL link if the Public Link has been enabled in the Share menu." This means a client file can exist in multiple permission states simultaneously: owned by one person, explicitly shared with another as an editor, visible to all members of a channel, and potentially accessible via a public link if that feature has been enabled in the share menu.
Critically, enabling a public link creates a new vector for access that is not controlled by channel membership. Anyone with the link can read the document without signing in or being added to any channel. Hiding or removing a public link is a distinct action from removing channel access. If a document containing a client estimate, inspection photo library, or work schedule has its public link enabled, removing the staff member who created it from channels and teams does not automatically prevent external sharing if the link was already distributed.
Default Sharing Behavior for Tasks and Calls
Tasks and calls have auto-sharing rules that differ from documents. Tasks are by default added to team memory, meaning all team members can see every task assigned to themselves and others without those tasks being explicitly mentioned in a channel. This is useful for transparency but requires careful configuration if you have contractors or part-time staff who should not see all active jobs. When someone is assigned a task, they receive an inbox notification; @mentioning them in the task body does not notify them, but @mentioning in comments does. This notification behavior affects both discovery and accountability trails.
Calls default to recording and transcript sharing with team memory. The toggle at the bottom-left of an active call switches between team and personal-only sharing. The default state is team-sharing; opting out is an active choice during or after the call. This means client calls, walkthrough recordings, and diagnostic conversations are typically added to shared team memory by default unless explicitly disabled. For home-services teams recording client property inspections or consultation calls, this auto-sharing default needs review against your privacy commitments and customer consent requirements.
Inherited Sharing and Linked Material Chains
A practical challenge arises when documents mention or link to other documents, or when files are embedded in tasks that are shared via channels. Removing access to the parent object does not automatically restrict access to linked children if those children are shared through other routes. For example, a project summary document mentioned in a client-facing channel may reference inspection photos stored in a linked document. If you remove someone from the channel, they lose access to the summary, but if the photo document was also directly shared with them or mentioned in another channel they still belong to, they retain access to those images.
Testing this behavior requires creating a representative file structure and verifying access from a secondary account before relying on channel removal as your sole method of revoking access to sensitive materials. The mechanics are: identify all channels where a document or its references are mentioned, trace any explicit sharing grants on those documents, check for public links, and then remove the person from channels while verifying they can no longer retrieve the materials through each route. If a document is owned by the departing employee and not transferred, ownership can become orphaned; someone needs to be assigned ownership to maintain administrative capability after they leave.
Testing Access Revocation with Controlled Accounts
Before implementing Macro as your primary client file system, conduct a controlled test with two user accounts: a "manager" account and a "contractor" account. Create a private channel for a sample project, add the contractor to it, and mention a client document in the channel. Verify the contractor can access the document. Record this as the baseline access state. Next, add a second document to the same channel and explicitly share it with the contractor account via email at the viewer level. Finally, enable a public link on a third document and share that link outside Macro.
Now remove the contractor account from the channel. Attempt to access the first document (shared via channel mention); confirm access is denied. Attempt to access the second document (explicitly shared); confirm access remains. Try to access the third document using the public link; confirm it works. This test proves the limits of channel-based revocation. To fully revoke access, you must: remove channel membership, revoke individual share grants, and disable or delete public links. Missing any step leaves a backdoor open.
Repeat this test with a document owned by the contractor account. When they are removed from channels, can another manager view or take ownership of that document? Try to change ownership while the creator is still active in a channel; verify the workflow. Some systems allow only the owner to transfer ownership; others allow workspace admins to do so. Macro's documentation does not detail the admin override capabilities for ownership transfer, so test this with your planned admin account before needing it during an actual offboarding.
Preparing Files for Project Closure
A structured offboarding process for client files involves several sequential steps. First, audit which channels contain active client work and which are historical archives. Move completed projects to archive channels that are team-discoverable but not auto-joined by new hires. Second, identify the owner of each critical document. If a project manager who is leaving owns the estimate templates, inspection checklists, or client file indexes, assign ownership to a remaining manager before the departure date. Do not wait until after they have left; some systems restrict access to the transfer interface once an account is suspended.
Third, export or archive any documents that should be retained for compliance or reference. Macro allows exporting a document to markdown text via a keyboard shortcut or menu option. If your business operates under service guarantees or warranty periods, export the scope-of-work documents, before-and-after photos, and customer acceptance records to a secure archive location outside Macro before removing channel access. Fourth, audit public links on all client-facing documents. If an estimate or quote was shared via public link for customer review, decide whether that link should remain active indefinitely (useful for future reference) or be disabled after project closure. Disabling a link prevents further access; anyone who bookmarked it will encounter a "not found" error.
Fifth, communicate the timeline to the team. If you are removing a contractor from the "Active Projects" channel on a specific date, notify the team so they can extract any needed contact information, notes, or work summaries before access ends. This is particularly important in home services where job handoff requires documentation: the contractor finishing a job must be able to retrieve the inspection report from a closed channel or have it transferred to a central archive channel they will remain in during their final days.
Offboarding a Contractor or Employee
When an employee or contractor is leaving, the offboarding checklist for Macro files should include: transferring document ownership, removing channel membership, revoking explicit share grants, disabling public links on sensitive materials, and archiving any reference materials they should not carry away. The order matters. Removing someone from all channels first means they lose access to channel-shared files immediately, but if you have not yet transferred ownership of their documents, no one else can modify those files afterward. A transfer-then-remove sequence is safer.
Start by identifying every document or file the departing person owns or has explicitly shared. Use Macro's search or filter by "owner" to list these. For each owned document critical to ongoing work, edit the document properties to assign it to a peer or manager. For each explicitly shared file, review the share settings and decide whether to keep the share grant for the new owner, revoke it, or add a replacement person. For each task assigned to the departing person, reassign it to a peer or mark it closed if the work is complete. Tasks in team memory remain visible by everyone, so reassignment ensures accountability is clear and the incoming person knows they now own the follow-up.
Next, remove the person from channels. Start with channels directly related to their role: if they are a field technician, remove them from the "Field Technician" channel and any client-specific private channels. Then remove them from broader channels like "All Staff" or "Random" where they may have seen company-wide communications. If they are a contractor, consider whether they should retain access to historical archive channels for reference (with read-only or viewer access) or be completely removed. Document the removal dates for audit purposes.
Finally, audit the public links they may have created. If a contractor created a public quote link and shared it with a customer, that link is still live even after they leave, but they are no longer working on that account. You may want to keep the link active so the customer can still reference their quote, or disable it if the contract is complete. Check the "Share" menu on any document they created or edited to see whether public sharing is enabled, and make a conscious choice about keeping or disabling each one.
Distinguishing Link Hiding from Access Removal
An important operational distinction in Macro is between making a link inaccessible and actually removing a person's access. If a document has a public link, disabling that link in the share menu makes the link itself non-functional, but only for people who do not already have access through other means. Someone who is a channel member will still access the document through the channel. Someone with an explicit share grant will still access it through their email grant. Hiding the link does not affect them; it only prevents new people outside those routes from discovering the document.
Conversely, removing someone from a channel immediately revokes their access to channel-shared materials, but public links remain active for anyone with the link. If you intend to fully restrict a document, you must act on all three mechanisms: remove channel access, revoke explicit shares, and disable the public link. Testing this distinction is critical. Create a document, share it via channel, add an explicit share grant, and enable a public link. Then remove the original sharer from the channel while keeping the public link active. Verify that external people with the link can still access it, but the channel member cannot. This ensures your team understands the independence of these sharing models.
Sample Workflow: Closing a Client Project
Consider an illustrative scenario in a home-services context. Your company completes a kitchen renovation for a customer. The project involved multiple contractors: a project manager, electrician, plumber, and carpenter. All were members of a private channel called "Jones Kitchen Renovation." The project manager created and owns three documents: the scope of work, a schedule, and a final invoice. The electrician contributed photos and notes in a shared folder. All materials were mentioned in the channel.
Project closure happens on Friday. On Thursday, the project manager transfers ownership of the three documents to you (the office manager) by editing the document properties. The electrician, plumber, and carpenter have already been removed from the channel as their work phases completed; only the project manager and office manager remain. On Friday morning, you move the "Jones Kitchen Renovation" channel to a new category called "Completed Projects" (a structural change, not a removal). You then remove the project manager from the channel, leaving you as the sole active member.
The project manager logs in later that day to retrieve their final notes and finds the channel still in their sidebar but with an error message: "You don't have access to this channel." Their locally cached version of the channel messages may still load, but they cannot edit or retrieve new updates. All linked documents, photos, and tasks are now inaccessible to them unless they had been explicitly shared outside the channel context.
The next week, the customer calls with a question about the warranty coverage. You retrieve the scope document from the "Completed Projects" channel—you still have access because you are the current owner and the channel owner. You reference the final invoice and payment confirmation, both still visible to you. Everything the customer asks about is in your hands, and the departed contractors cannot inadvertently modify or delete the record because they are no longer channel members.
Managing Multi-Channel References and Archives
A mature home-services operation may maintain multiple channel types: "Active Jobs" (team channel, auto-joined), "Project Templates" (team channel, read-only for some roles), "Archived Projects" (private, growing over time), and client-specific channels (private, disbanded after project close). Documents referenced across channels complicate offboarding. If a template for inspection checklists is mentioned in "Project Templates" and a specific completed project's checklist is mentioned in "Jones Kitchen Renovation," removing someone from the specific project channel does not affect their access to the template through the template channel, even if they should no longer see projects at all.
To prevent this confusion, establish a filing convention: client-specific files stay in client-specific channels, templates stay in shared template channels, and only the tools or metadata that clients should see are given public links. When archiving a completed project channel, do not delete it; instead, move it to an archive category and change its membership to read-only or remove new members from auto-join. This preserves historical access for anyone who remains in the company while preventing new hires from being overwhelmed with old job details on day one.
Considerations for Contractor vs. Employee Offboarding
Contractors and employees may warrant different file access timelines. An employee departing on friendly terms may be given a brief grace period to retrieve personal work or transition materials; a contractor's access might be revoked immediately after their final deliverable. Macro does not have a built-in "suspend account" state that restricts access gradually; removal is binary. Plan for this by deciding in advance whether departing people should be kept in read-only channels for reference or completely removed. If you want to preserve their ability to view completed work for portfolio purposes, assign them to an "Alumni" channel where they keep access to selected completed projects but cannot edit or receive notifications.
Another consideration: calls and task recordings. If a contractor conducted a client call that was recorded and auto-shared to team memory, that recording remains in team memory even after the contractor is removed from channels. The team can still view the call recording and transcript. The contractor themselves cannot access it unless you explicitly share the call with them afterward or they remain in the team. This is usually the desired outcome—the work product stays with the company, but the individual loses access. However, if the contractor claims they need a copy for their portfolio or legal purposes, Macro's export options allow exporting tasks and call transcripts as markdown or text, which you can provide separately if your policy allows.
Regulatory and Compliance Checkpoints
A sharing configuration alone does not establish that a deployment meets the organisation’s contractual or regulatory requirements. Confirm the relevant agreements, operating procedures and access tests with the responsible team.
Use channel-based access control as one layer of your data governance, not the only one. Audit your offboarding process annually to verify it prevents unauthorized access. Document which documents are exported for compliance archival and where they are stored. Test that removing someone from channels actually prevents their access by using a test account, then verify access is denied before declaring the offboarding complete. If your business operates across multiple teams or locations, consider whether Macro's team-level channels are granular enough or whether you need to add metadata tags to further filter who can see which projects.
Key Decision Points and Acceptance Criteria
Before committing Macro to managing client files during project closure and offboarding, establish and test three acceptance criteria. First, verify that channel removal revokes access within 60 seconds and is not queued or eventual. Log in as a test contractor account, confirm they access a channel-shared document, then have an admin remove them from the channel and check immediately whether the document becomes inaccessible. If caching or eventual consistency delays this, plan for that lag in your offboarding timeline. Second, verify that document ownership transfer works correctly and does not lock the file during transfer. Transfer a document you own to a peer, confirm they can edit it, and confirm you can still access it as an editor. Third, test public link disabling: enable a public link, share the URL externally, disable the link, and confirm the external user receives an error when accessing it.
Additionally, establish a worksheet or checklist you will use for every offboarding. Include fields for: employee name, departure date, channels they belonged to, documents they own (to be transferred), explicit shares to revoke, public links to disable, task reassignments, and sign-off date. Have your office manager or HR lead complete this checklist 48 hours before the departure, then again 24 hours after to ensure all items are closed. This operational discipline prevents accidental retention of access and provides an audit trail for compliance reviews.
Frequently Asked Questions
Can I prevent a departing contractor from downloading or forwarding files before I remove them from channels? No. Macro does not have a "read-only" mode that prevents downloads or forwarding. Once someone has access, they can export or copy content. To control this, limit their channel membership duration and remove them from channels as soon as their work is complete, before they become aware they are leaving or before a notice period allows them to copy your files. Alternatively, store highly sensitive files in a separate workspace they do not access until the day they need it for a specific task.
If someone is removed from a channel, can an admin restore their access later if we realize we need to share something with them? Yes. An admin can add them back to the channel at any time, and they will regain access to the full channel history, including all documents and messages from before they were removed. This is the magic of channel-based sharing, but it also means offboarding is not permanent if you need to retrieve and re-share specific files. Keep the offboarded person's account active in Macro (do not delete it) so you can temporarily re-add them if needed for handoff or reference.
Does Macro provide an audit log showing who accessed which files and when? Macro's documentation does not specify audit logging features. Before committing to Macro for client files subject to audit requirements, contact Macro support to confirm whether access logs are available and how to export them for compliance reporting. Assume access logging is not available in the public feature set unless explicitly confirmed.
What happens if a document owner is the only person in a private channel and then leaves? The document remains in the workspace and is still owned by their account. You, as a workspace admin, should be able to transfer ownership or delete the document, but this depends on admin-level permissions that are not detailed in the public documentation. Test this scenario with your planned admin account before relying on it during an actual offboarding.
By implementing a deliberate offboarding process rooted in Macro's channel-based sharing model, testing access revocation with realistic scenarios, and maintaining an audit checklist, your team can confidently manage client files through project closure and staff transitions. The key is understanding that hiding access through channel removal is distinct from deleting files or revoking public links, and that multiple sharing routes (channels, explicit grants, public links) must be acted on independently to fully restrict access.
Official sources and related guides
This independent Sysevo guide uses the following official documentation. The workflow and trial scenarios are evaluation proposals, not reported customer results or a hands-on benchmark.
- Macro official product documentation
- Macro official supporting guide
- GoHighLevel for Gyms: Follow Up Membership Pauses and Visit Requests
- Macro for Contractors: Hand Over Projects Without Lost Decisions
- Zanus AI for home services
Compare the same requirements with the relevant Sysevo product, Voice Agents and CRM. Review Sysevo plans and pricing or book a demo to discuss the proposed setup. Sysevo sells its own business software and is not affiliated with the competitors discussed here.



