How to Onboard Remote Employees With Docmost

Set up remote employee onboarding in Docmost with pages for the first day, week, and month, plus a questions log that improves the pages with every new hire.

TL;DR

  • Remote employee onboarding works best when the new hire has one place to read.
  • In Docmost, that place is a dedicated onboarding space with pages for the first day, week, and month.
  • Add a questions log from day one. And at day 30, turn each question into a page or an edit so the next hire has fewer questions to ask.

A new hire who works remotely can't ask the person at the next desk where to find something. They type the question into chat and wait for someone to come online, which can take a while when the team is spread across time zones.

Each of those questions also tells you something. A question the hire had to ask means a page is missing, or the page exists and they couldn't find it. In an office, the question gets answered out loud and nobody writes anything down. But when the hire works remotely, the question is already in writing, so you can see what's missing.

This guide shows how to set up remote employee onboarding in Docmost. You'll build a dedicated space with a page tree for the first day, week, and month. Every page ends with a "done when" line, and the hire keeps a questions log of every question they had to ask. At day 30, you turn each logged question into a new page, an edit, or a better link, so the next hire can find the answer without asking.

What a Wiki Does in Remote Employee Onboarding

In your remote job onboarding process, the wiki's job is to give the hire one place to read how the company works, in the order they need it.

Not everything belongs there, and it's important to decide that before you build anything.

Content

Where it goes

Why

How we work: tools, meetings, who to ask, role guides

Onboarding space in Docmost

Applies to every hire and changes as the company changes

Contracts, right-to-work documents, personal details

HR system

Belongs to one person and has retention rules

Hardware shipping and account creation

IT ticket or HR task list

Needs an owner and a due date, not a page to read

Welcome messages and introductions

Team chat and video calls

Needs a person, not a page

For the reasoning behind that split, see what belongs in your wiki and what stays in your HR system.

This guide is about running onboarding in a wiki you've already chosen. If you're still choosing one, start with wiki software for remote teams.

Set Up the Onboarding Space in Docmost

Create a Dedicated Space

Give onboarding its own space instead of a section inside a bigger one, so you control exactly who's in it. Go to Settings, then Spaces, and click Create Space. Enter a name such as Onboarding, choose a slug (the short name in the space's web address), and add a short description. You become the Space Admin with Full Access.

If your onboarding documents are already kept somewhere else, you can bring them in with the import and export guide. Details on spaces are in the Spaces docs.

Choose the Right Role for New Hires

Docmost spaces have three roles: Full Access, Can Edit, and Viewer. Give each person the role that fits where they are in onboarding:

  • Before the start date: Viewer, so the hire can read "Start Here" without changing anything.
  • From day one: Can Edit, because the hire writes in the questions log and fixes pages.
  • Managers and buddies: Can Edit.
  • You, as Space Admin: Full Access.

To add someone, open Space Settings, go to the Members tab, and click Add Space Members. If you onboard people in batches, create a group for new hires and add the group instead of each person. Skip the default "Everyone" group for this, since it contains every user in the workspace. The Groups docs show how to create one.

Set Policy Pages to Read Mode

Docmost has a Read/Edit mode that lets you set a default page mode to prevent accidental edits. Use it on policy-style pages the hire should read and not change. But leave the questions log and the role guides in edit mode, since those are the pages you want the hire to write in.

The Onboarding Page Tree: First Day, First Week, First Month

This is the part to copy. Create the top-level pages first, then nest the rest underneath them. You can reorder everything by dragging pages in the sidebar.

Onboarding (space)
├── Start Here
│   ├── How This Space Works
│   ├── Who to Ask About What
│   └── Your Questions Log
├── Day 1
│   ├── Your First Day Schedule
│   ├── Accounts and Access
│   └── How We Communicate
├── Week 1
│   ├── How We Work
│   ├── Meet the Team
│   ├── Team Meetings
│   └── Your First Small Task
├── Month 1
│   ├── What Good Looks Like at Day 30
│   ├── Your First Project
│   └── Day 30 Review
├── Role Guides
│   └── [Role] First 30 Days (one per role)
└── For Managers and Buddies
    ├── Before the Start Date
    ├── Weekly Check-Ins
    └── Closing the Log at Day 30

Every page ends with a "done when" line, so the hire knows exactly when they can move on. The table below shows what is on each page and how it ends.

Section

Page

What's on it

Done when

Start Here

How This Space Works

How the tree is ordered, how to ask questions, what the log is for

You've read it and know where the log is

Start Here

Who to Ask About What

A short routing list: topic, person, channel

You've picked who you'd ask about access, pay questions, and your role

Start Here

Your Questions Log

One table for every question you have to ask

You've opened the log and added your first question

Day 1

Your First Day Schedule

What happens, in the hire's time zone, with reading time blocked

You've confirmed the schedule works for your time zone

Day 1

Accounts and Access

Each tool, how to sign in, who fixes problems

You've signed in to each tool and listed any that you couldn't sign in to

Day 1

How We Communicate

Which channel is for what, and how fast people reply

You've posted your intro in the right channel

Week 1

How We Work

How work moves from request to done, with one real example

You can describe the path from request to done in two sentences

Week 1

Meet the Team

Who does what, with a suggested order for intro calls

You've booked the first two intro calls

Week 1

Team Meetings

Which meetings exist, which are optional, how notes are shared

You know which meetings you attend this week

Week 1

Your First Small Task

One task with a clear scope and a person to review it

The task is finished and reviewed

Month 1

What Good Looks Like at Day 30

What the manager expects

You and your manager have read it together

Month 1

Your First Project

Scope, owner, and where the work is kept

You've shared a first draft

Month 1

Day 30 Review

A conversation guide, plus the log conversion described below

You've had the review and the log is closed

Every hire reads the same core pages. The Role Guides section is where the pages start to differ by job. Each role gets one page inside it that covers the tools that person will use, the people they'll work with, their first tasks, and the questions people in that role usually ask in their first month. Put your "Who to Ask About What" list in a synced block, so when you edit it once, every page that shows it updates.

"For Managers and Buddies" covers what the people around the hire need: a checklist of what has to be in place before the start date and a short agenda for weekly check-ins. The last page has the steps for closing the log at day 30.

If a role takes longer to get comfortable in, add Month 2 and Month 3 pages that follow the same pattern: what good looks like, one project, and a review.

The Accounts and Access page, written out in full, shows what each page looks like:

Accounts and Access
Owner: [name] · Last reviewed: [date]

Before you start: your laptop has arrived and you have your work email address.

Steps:
1. Sign in to email and set up your calendar.
2. Join the team chat and post a hello in the welcome channel.
3. Open the project tracker and find your name on the team list.

If something doesn't work: add it to Your Questions Log, then message your buddy.

Done when: you've signed in to all three and posted in the welcome channel. Add a comment to this page that starts with your manager's @mention and says "Access confirmed," or lists what didn't work.

The "Done When" Line: Check Progress Without a Call

Every page ends with a short "done when" line the hire can answer with evidence. In the sample above, the evidence is a comment that @mentions the manager, and mentioned users may receive a notification. You read it when you're online, and the hire never waits on a call to find out whether they're finished.

Resolving comments is a paid feature, but plain comments work on any edition, so this process doesn't depend on the paid edition.

The "done when" line tells the hire when they can move on. It isn't a test, and nobody grades it. For how to write the steps on each page, see how to write internal documentation. The difference here is that you can check the "done when" line without being online.

Keep a Questions Log: Turn Every Question Into a Page

A questions log is a table where the hire writes down every question they had to ask, so you can turn the answers into pages. It's the part that makes the space better with every hire.

Why a Written Question Is Useful

A question asked in the office disappears. But a question written in the log stays, and it can be counted, sorted, and fixed. For the wider habit, see setting up a corporate wiki.

How to Set Up the Log

Create a log page for each hire under "Start Here", with their name in the title. Your Questions Log in the tree above is the pattern. Add a table in the editor with these columns: Date, Question, Where I Looked First, Who Answered, Answer, and Page to Fix.

On the paid edition, you can start each log from a page template so every one has the same columns.

Three example rows:

Date

Question

Where I Looked First

Who Answered

Answer

Page to Fix

Example, day 2

Which channel do I use for access problems?

Start Here

Buddy

The IT channel

Who to Ask About What

Example, day 4

How do I request time off?

Searched "time off"

Manager

Ask your manager, then book it in the HR system

Time Off (page missing)

Example, day 9

Where does the first draft get reviewed?

How We Work

Teammate

In the project tracker, assigned to the lead

How We Work

On Docmost's paid edition, a Base can store the same rows and show them as a table or a Kanban board. Add a label to each page the log points at, such as the topic name, so you can find related pages later.

The Rule for Answering

When someone answers a hire's question in chat, the answer goes into the log, or the reply links to the page that already has it. Either way, the question gets a row.

Day 30: Turn Questions Into Pages

At the Day 30 Review, sit down with the hire for about 30 minutes and go through the log. The manager or the buddy can do this.

Each row falls into one of these groups:

What the row shows

What to do

Example

The answer existed, but the hire couldn't find it

Rename the page so its title matches what the hire searched for, add a link to it from the page they looked at first, and add a label

A page called "Tooling Notes" that should be "Accounts and Access"

No page covers it

Write a new page and add it to the tree

"Time Off"

The page was wrong or out of date

Edit it and note the change in page history

A tool name that changed

Several hires asked it

Several hires needed it, so it belongs in "Start Here"

A page on submitting expenses, buried under Month 1

Only this hire needs the answer

Leave it in the log

A question about a personal setup

Let the hire make the edits, because they know which wording confused them. When every row has a next step, the log is closed. Page history keeps every change and lets you restore an older version if an edit goes wrong.

What the Log Tells You Over Time

Watch three signals: how many questions come in each week, which ones repeat from hire to hire, and how many were "the answer existed but I couldn't find it." A falling count of repeat questions is a sign the space is working. Treat these as signals to watch and not targets, because there's no number you should be aiming for.

Remote Employee Onboarding Checklist: Before Day One to Day 30

Each row is one task. The Owner column says who is responsible for it, and the last column names the wiki page that helps with it.

When

Owner

Task

Docmost page

Before day one

IT

Ship hardware and create accounts

Accounts and Access

Before day one

Manager

Add the hire to the space with the Viewer role

Start Here

Before day one

Manager

Send the link to Start Here and the day one schedule

Your First Day Schedule

Before day one

HR

Collect contracts and personal documents

Not in the wiki

Day 1

Manager

Hold a welcome call

Your First Day Schedule

Day 1

Hire

Sign in to every tool

Accounts and Access

Day 1

Buddy

Confirm the hire knows where to ask

Who to Ask About What

Week 1

Hire

Read "How We Work" and "Team Meetings", with reading time blocked

How We Work

Week 1

Manager

Introduce the hire to important colleagues

Meet the Team

Week 1

Hire

Finish a first small task

Your First Small Task

Weeks 2 to 4

Hire

Read the role guide and start the first project

Role guide, Your First Project

Weekly

Manager or buddy

Check in and read new log entries

Weekly Check-Ins

Day 30

Manager and hire

Hold the review and convert the log

Day 30 Review

Onboarding Across Time Zones

Virtual employee onboarding only works across time zones if the hire can keep moving when nobody is online. Four habits make that possible.

Write "Day 1" Pages So Nobody Has to Be Online

Each page has the steps, the result the hire should see, and what to do if something doesn't go as intended. That way a hire who hits a problem at the end of their day can log it, move to the next step, and get the answer in the morning.

Set Expectations on One Page

Use "How We Communicate" for working hours, how fast people reply in each channel, and who covers when the manager is offline. A hire who knows a reply will take a day doesn't read the silence as a problem.

Add Recorded Walkthroughs Where Text Isn't Enough

Sometimes, steps are easier to show than describe. So, record a short screen walkthrough and put it on the page it explains, as a link or an embed.

Schedule the Reading

Block reading time in the "Day 1" schedule and name the first pages to read. Sending a hire off to read the whole space on their own is how they end up skimming the pages that matter most.

Who Sees What: Roles, Groups, and Page Permissions

Space roles are enough for most onboarding spaces, because everyone in the space can read the tree and the role guides. If a few pages should be for managers only, such as the pages in "For Managers and Buddies", use page-level permissions on the paid edition. You can also keep those pages in a separate space with its own members, which works on any edition.

Keep the Space Accurate

Put an owner and a last-reviewed date at the top of each page, as in the sample above. Review onboarding pages every three months, and put each review on someone's calendar. For the fields to use, see how to assign page owners and review dates.

The Day 30 Review also works as a check on your pages. By then the hire has used most of them, so they can tell you which ones are out of date or confusing. On the paid edition, page verification lets you pick one person to confirm that a page is still correct and set the date it needs checking again.

Docmost Features Used in This Setup

Feature

Used for

Edition

Spaces and nested pages

The onboarding tree, with drag and drop to reorder

All

Space roles and groups

Viewer before day one, Can Edit from day one

All

Comments and @mentions

"Done when" replies and questions on a page

All

Page history

Seeing and restoring changes the hire makes

All

Labels

Tagging pages the log points to

All

Synced blocks

One "Who to Ask About What" block shown on many pages

All

Search

Letting the hire find answers before asking

All

Page templates

Starting each role guide or log from the same layout

Paid edition

Page-level permissions

Restricting the manager pages

Paid edition

Bases

Optional table and Kanban view of the log

Paid edition

Page verification and approval

Naming who confirms a page and when

Paid edition

To see how Docmost fits next to other options, compare Docmost with other wiki platforms.

Frequently Asked Questions

  1. How Do You Onboard a Remote Employee With a Wiki?

Build a dedicated space with pages for the first day, week, and month. End each page with a "done when" line, and keep a questions log the hire updates from day one.

  1. Who Should Own the Onboarding Space?

One named person, usually the people ops lead or the hiring manager. Each page should also list its own owner at the top, so the space doesn't depend on one person remembering everything.

  1. How Long Does Remote Onboarding Take?

It depends on the role. The pages in this setup cover the first month, and a longer role can add Month 2 and Month 3 pages.

  1. Is Remote Onboarding Different From In-Office Onboarding?

The goals match, but nothing can be left to happen by chance when the hire works remotely. They can't learn by watching, so what they need has to be written down and easy to find.

  1. How Do You Onboard Employees Across Time Zones?

Write pages that need no live reply, set reply-time expectations on one page, and use the log so questions get answered in writing. The hire logs a problem, keeps going, and gets the answer when someone comes online.

  1. Can a Wiki Replace Onboarding Software?

No. A wiki covers how the company works. Contracts, payroll, and personal records stay in your HR system.

  1. When Should Remote Employee Onboarding Start?

Before day one. Ship hardware and create accounts early, and give the hire read access to Start Here so the first day isn't their first look at how things work.

Build Your Onboarding Space in Docmost

With Docmost, a remote hire can keep working while the team is offline, and every question they log can become a better page for the next hire. Get a free trial license and start with "Start Here".