How do I securely share internal onboarding documentation with freelancers or short-term contractors?
Share onboarding documentation with contractors by creating a limited-access section of your knowledge base that contains only what they need — role-specific SOPs, tool guides, and project context — without exposing internal policies, pricing data, or other sensitive company information. Use read-only permissions and revoke access when the engagement ends.
How do you set up contractor access?
| Platform | How to Share Securely |
|---|---|
| Notion | Create a separate "Contractors" workspace or use guest access with page-level permissions |
| Confluence | Create a space with restricted access, add contractor as guest |
| Google Drive | Shared folder with view-only permissions |
| Glyde/Scribe | Share individual guide links (view-only) |
What should contractors see vs not see?
| Share with Contractors | Keep Internal Only |
|---|---|
| SOPs for their specific tasks | Company-wide policies and org chart |
| Tool access guides for their assigned tools | Admin panel access or credentials |
| Project briefs and brand guidelines | Pricing and financial data |
| Communication protocols (who to contact) | Internal Slack channels beyond their scope |
| Quality standards and examples | Performance review criteria |
| Deadline expectations | HR policies and employee benefits |
Best practice: create a contractor onboarding template that you reuse for every engagement. Generate the task-specific SOPs with Glyde, store them in your contractor folder, and share the folder link with appropriate permissions. When the engagement ends, revoke access in one click.
This answer is part of our guide to employee onboarding documentation.