Use cases
Onboarding new team members
Everything a new hire needs in one searchable space. Processes, docs, contacts, and context.

The first weeks at a new job are mostly spent looking for things. Where's the brand guide? How do I request access to the staging environment? Who do I talk to about invoicing? What's the process for submitting work? The answers exist somewhere, scattered across a wiki nobody maintains, a shared drive with a hundred folders, Slack messages from before the new hire existed, and the heads of people who are too busy to walk them through everything. Onboarding fails not because nobody prepared for the new person, but because the preparation is spread across so many places that finding it is a job in itself.
This page is for managers, HR teams, and operations people who want to give new hires one place where everything they need is searchable from day one, without having to rebuild the onboarding experience for each person.
The problem
The information exists but isn't findable. Processes are documented in a wiki. Guides are in a shared drive. Contacts are in a spreadsheet. Templates are in email threads. The new hire's job is to assemble all of this into a working understanding of how the team operates, and nobody has made that easy because the information was never consolidated.
Onboarding depends on specific people's availability. The real onboarding happens when someone experienced sits down and walks the new hire through things. But that person has their own work, so the new hire waits, asks in Slack, gets a partial answer, and pieces things together over weeks. The dependency on individual availability slows everything down.
Every new hire gets a different experience. Without a consistent onboarding resource, what a new person learns depends on who happens to help them, what links they're sent, and what they stumble across. One hire gets a thorough walkthrough. The next gets a folder link and "let me know if you have questions." The inconsistency means some people ramp in two weeks and others take two months.
What Fabric changes
Everything a new hire needs is in one searchable space. Processes, guides, templates, contacts, tools access instructions, team norms, and reference materials all live in a dedicated onboarding space. The new hire has one place to go, and everything in it is searchable by meaning.
The new hire can find answers without asking. Instead of messaging a teammate for every question, the new hire searches the onboarding space or asks the AI assistant. "How do I submit an expense report" returns the relevant process document. Self-service replaces waiting for someone to be available.
The onboarding experience is consistent and reusable. Build the space once and use it for every new hire. Update it as processes change. Every person who joins gets the same comprehensive, current resource rather than a variable experience that depends on who's around to help.
How it works
A dedicated onboarding space. Create a Fabric space for onboarding with everything a new hire needs. Organise by category if it helps (processes, tools, people, templates), but don't over-structure. Search handles discovery.
Search for any question. Fabric's AI search reads inside every document and note in the space and searches by meaning. A new hire searching "how to set up my development environment" finds the relevant guide whether it's titled "Dev Setup" or buried in a broader engineering onboarding document.
An AI onboarding assistant. The AI assistant works from the content in the onboarding space. New hires ask questions in plain language and get answers drawn from the actual documentation, with references. This is faster than searching and doesn't require a teammate's time.
Write and maintain guides collaboratively. Use notes and docs to write onboarding guides, checklists, and process documents. Anyone on the team can update them as things change.
Pull in existing documentation. Connect Google Drive, Notion, or Dropbox to bring in existing onboarding materials, process docs, and guides without rewriting them. Forward useful emails to your email-to-note address.
Track the onboarding checklist. Use tasks and reminders to give the new hire a structured checklist: accounts to set up, documents to read, people to meet, training to complete. The checklist lives in the same space as the guides it references.
Annotate documents with tips. Annotate onboarding materials with practical tips, common mistakes, and clarifications. These notes add the kind of context a mentor would provide, attached directly to the relevant document.
An onboarding workflow in Fabric
Build the space before the hire starts. Assemble processes, guides, checklists, contacts, tool setup instructions, and templates. Import from existing tools. The space should answer every question a new hire is likely to ask in their first month.
On day one, share the space. Give the new hire access and walk them through how to search and ask questions. This is the one walkthrough that replaces dozens of ad hoc explanations.
Let them self-serve. When the new hire has a question, they search the space or ask the assistant first. If the answer isn't there, that's a signal to add it. Each gap filled makes the space better for the next hire.
Use the checklist to structure the first weeks. The onboarding tasks give the new hire a clear path through their first weeks: what to read, who to meet, what to set up. Progress is visible to both the hire and their manager.
Collect feedback from the new hire. New hires see the gaps that experienced people don't. Ask them to note what was missing, confusing, or outdated. Use that feedback to improve the space for next time.
Update as processes change. When a process changes, update it in the onboarding space. The next hire gets the current version automatically. No separate maintenance cycle.
What compounds over time
An onboarding space in Fabric improves with every hire. Each person who joins and finds a gap contributes to filling it, so the space gets more complete and more useful over time. After onboarding ten people, the resource covers questions you wouldn't have anticipated when you built it.
The time savings compound too. The first hire you onboard with the space takes marginally less time than a manual onboarding. The tenth hire takes dramatically less, because the space is thorough, the AI answers most questions, and the experienced team members are barely interrupted. At scale, a good onboarding space is worth weeks of recovered productivity per year.
For guidance on onboarding in Fabric, see the guides to onboarding collaborators and setting up a collaborative workspace.
Related use cases
For the standing team knowledge base that the onboarding space draws from, see team wiki. For per-project knowledge that a new hire might need to access, see project documentation. For managing a team's brand and file library, see digital asset management. Fabric supports teams of all sizes.
Get started
Give every new hire one searchable space with everything they need, and stop onboarding through Slack messages and shoulder taps. Try Fabric free.
Comparing tools? See why teams choose Fabric as the best team knowledge base and the best internal wiki software.
FAQs
Can a new hire ask the AI questions about our processes?
Yes. The AI assistant works from the content in the onboarding space. New hires ask questions in plain language and get answers drawn from the actual documentation, with references to the source documents.
Can I create a checklist for new hires?
Yes. Use tasks and reminders to build an onboarding checklist: accounts to set up, guides to read, people to meet, training to complete. Progress is visible to both the hire and their manager.
Can I reuse the same onboarding space for every new hire?
Yes. Build the space once and share it with each new hire as they join. Update it as processes change and it stays current for the next person.
Can I import existing onboarding docs from Google Drive or Notion?
Yes. Fabric connects to Google Drive, Notion, and Dropbox. Bring in existing guides, process docs, and templates without rewriting them.
Does the onboarding space have to be perfectly structured?
No. Search works by meaning, so a document is findable by what it says, not by where it sits in the page hierarchy. Good structure helps browsability, but search ensures nothing is unfindable just because it's in the wrong folder.
Can I include video or audio walkthroughs?
Yes. Add video files or record voice notes with process explanations. Fabric transcribes audio so the content is searchable as text alongside your written guides.
Can I annotate onboarding documents with tips and context?
Yes. Annotate any document with practical tips, common mistakes, or clarifications. These notes add mentor-like context attached directly to the relevant material.
Can the new hire's manager see their progress on the checklist?
Yes. Tasks in the shared onboarding space are visible to everyone with access. The manager can see which checklist items are complete and which are outstanding.
How is this different from using Notion or Confluence for onboarding?
Notion and Confluence are page-based systems that require deliberate structure and navigation. Fabric adds AI search by meaning, an AI assistant that answers questions directly from the documentation, and support for every content type (documents, audio, images, files) in the same searchable space. The difference matters most for new hires who don't know what to navigate to, because they can search or ask instead of browsing.
Can I give different roles different onboarding experiences?
Yes. Create separate spaces or sub-sections for role-specific onboarding (engineering, design, sales, operations) alongside a shared general space. New hires get access to the general space plus their role-specific one.
Can I control what the new hire sees?
Yes. Access is controlled per space. The new hire sees only the spaces you've shared with them. Sensitive material in other spaces remains invisible.
What happens after the onboarding period?
The space stays as a reference. New hires can return to it whenever they need to look something up. Over time, they transition to using the broader team wiki for ongoing questions while the onboarding space remains available as a starting-point resource.
