--- title: "How a Team Built a Living Onboarding and Knowledge System — Kylon Use Case" description: "Connect role processes, training material, current projects, internal apps, and everyday questions in a shared workspace that improves with use." url: "https://kylon.io/use-cases/living-onboarding-knowledge-system" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>[Talent operations](https://kylon.io/use-cases/topics/talent-operations)\>How a Team Built a Living Onboarding and Knowledge System Use Case7 min read # How a Team Built a Living Onboarding and Knowledge System Connect role processes, training material, current projects, internal apps, and everyday questions in a shared workspace that improves with use. [Start in Kylon](https://app.kylon.io/launch/living-onboarding-knowledge-system) [Book a call](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) What you'll connect - Google Drive - Gmail - Outlookoptional Your agent asks for each one in the Room. Nothing is sent or written until a person approves it. Kylon TeamProduct August 6, 2026 Step by step ## From a first day to real work. One card per step. The agent prepares, and a named person decides. 1. 01 ### Build the learning plan Today A new teammate gets a handbook and a folder of reference documents. In Kylon A role-specific plan is drafted from current process notes, projects and internal apps. Who decides The manager confirms the plan. 2. 02 ### Route the open question Today Questions go to whoever seems to know, and the answer stays buried. In Kylon An unanswered question goes to its knowledge owner with the relevant source attached. Who decides The knowledge owner answers and updates the record. 3. 03 ### Track progress without meetings Today Managers hold status meetings to learn where each new joiner stands. In Kylon Tasks, pending reviews and mentors appear per role, with a reviewer invited when a task is done. Who decides The reviewer checks each completed task. 4. 04 ### Send the welcome Today Welcome notes and access requests written from scratch for each person. In Kylon A welcome message or access request is drafted from the linked context. Who decides The manager reviews, edits and sends it. What it works with ## The tools you already use. - Connection Google Drive Keeps policies, process notes, training material and the core documents for each role. - Connection Gmail Carries welcome messages and access requests, drafted for a manager to send. - Optional Outlook Carries onboarding email if your team works from Outlook instead. Set it up ## Start with the next teammate who joins. 1. 1\. Start in Kylon A new Room opens in your workspace with this prompt. 2. 2\. Connect what it lists Google Drive, Gmail, from the card in the Room. 3. 3\. Give it your rules Your agent asks one at a time and writes them into the Room's guideline. Set-up prompt Set up our onboarding knowledge system in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Google Drive and Gmail first, since the first run needs them. Tell me which ones still need connecting. Outlook can wait until a step uses it. 2. Ask me which roles we onboard, who owns each area of knowledge, and who mentors and reviews new teammates. Help me invite them to this Room. 3. Build an Onboarding App with one record per new teammate: role, mentor, first-week checklist, core documents, knowledge owners, recurring workflows, current projects, open questions, progress and next review date. 4. For the next teammate who starts, draft a role-specific learning plan from the current documents in Drive, with each item linked to its source. Show me the plan before you save it. 5. Draft a welcome message and any request for missing access from the linked context, and hold each one in Gmail for the manager to review and send. 6. Copy our roles, knowledge owners and review rules into this Room's guideline, including how a question with no answer is routed to its owner. 7. After one clean onboarding, offer to turn milestone reminders and reviewer check-ins into an Automation. Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time. [Start in Kylon](https://app.kylon.io/launch/living-onboarding-knowledge-system) Rolling this out with a team? ## How it works in detail ## Start new teammates in real context A new teammate needs more than a handbook. Their onboarding record links the people, process notes, current projects, internal apps, and first working tasks that apply to their role. ## Keep knowledge connected to the work Policies, process notes, decisions, and email context remain attached to the work they explain. The agent can prepare a role-specific learning plan from the current source material rather than a static document. ## Create a usable onboarding app A database app can show the first-week checklist, knowledge owners, core documents, recurring workflows, open questions, and progress for each role. ## Use questions to improve the system When a new teammate cannot find an answer, the question can be routed to an owner with the relevant source. The answer improves the record for the next person. ## Keep external communication reviewed An agent can draft a welcome message or request for missing access from the linked context. A manager reviews and confirms any external message before it is sent. ## Turn onboarding knowledge into an active system New employees need more than a folder of reference documents. They need to understand which information applies to their role, where to ask questions, what good work looks like, and how their learning connects to real responsibilities. Kylon brings those elements together in a living onboarding knowledge system. Teams can organize guidance, policies, examples, checklists, role-specific tasks, and discussion in the same workspace where work is already taking place. Instead of treating onboarding as a one-time download of information, the organization can maintain a system that develops as processes, customers, and team practices change. New joiners receive a clearer path, while experienced colleagues have a more reliable way to share current knowledge. ### Connect guidance to the work it supports Static documents become difficult to use when they do not show the context behind a rule or a decision. In Kylon, a knowledge page can be linked to the conversation, workflow, database record, or project where it is applied. A new team member can see the approved process alongside a practical example and the person responsible for review. Subject specialists can update the source material without asking every employee to manage separate copies. This approach supports knowledge sharing without implying that one document has every answer. It gives people an orderly place to start, a route for asking questions, and a visible record when guidance has been clarified or changed. ## Make progress visible without turning it into paperwork A strong onboarding system gives managers enough visibility to support people without requiring constant status meetings. Kylon can provide a shared view of onboarding tasks, pending reviews, assigned mentors, and role-specific resources. A workflow can collect progress from the new joiner, invite a reviewer to check a completed task, and send a reminder when an agreed milestone has not yet been revisited. Database apps are usable internal systems for tracking the onboarding journey and linking it to the actual work the person is learning to do. The team can adjust the path for different roles or locations while retaining a common structure for the material that matters across the organization. Some onboarding work includes communications that must go outside the organization, such as a welcome message to a customer, a request to a partner, or a draft for a vendor. Kylon can prepare an email draft from the relevant linked context, but it does not remove the need for judgment. A person must review the content, make any necessary edits, and explicitly confirm before the email is sent externally. That distinction allows the system to reduce repeated preparation work while keeping accountability with the appropriate employee. As questions, examples, and feedback accumulate, the onboarding space becomes a maintained operational resource rather than an archive that is consulted only on a first day. ## What the team keeps in the internal system The exact fields differ by workflow, but the system keeps the source context, current status, accountable owner, decision history, related documents, relevant email thread, next internal action, and review date together. That structure gives people and agents a reliable starting point whenever work changes hands. ## Start with one repeated workflow Teams do not need to replace every tool at once. Start with the repeated work that currently requires people to copy information between conversations, inboxes, documents, and spreadsheets. Build a shared record, connect the people who own it, and use a workflow to support the review rhythm. The system becomes more useful as its context and decisions accumulate. See how Kylon can help your team turn recurring work into a shared operating system. [Talk to Kylon](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) ## More Use Cases [View all](https://kylon.io/use-cases) [ Before: 1,000 to email today, Re: group rates?, call notes: who?, hot lead, unread, OOO reply x40. With Kylon: 12 meetings booked from one send. Scored 214 replies by intent. Workflow tools: Gmail, Outlook, Fathom. ### How a US Hospitality Firm Built an AI Sales Pipeline with Kylon Agents run 1,000-contact outreach, score replies and route leads. - ![HubSpot](https://kylon.io/v2/integrations/small/hubspot-com.webp) - ![Apollo](https://kylon.io/v2/integrations/apollo.png) - ![Cloudbeds](https://kylon.io/v2/integrations/small/cloudbeds-com.webp) - ![Fathom](https://kylon.io/v2/integrations/small/fathom-video.webp) - ![Calendly](https://kylon.io/v2/integrations/small/calendly-com.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/ai-sales-pipeline)[ Before: resume\_final2.pdf, Re: still keen?, interview: TBD, 47 unread applicants, which role is this?. With Kylon: 12 interviews booked this week. Scored 47 resumes vs roles. Workflow tools: Gmail, Outlook, Google Calendar. ### How an AI Startup Automated Talent Sourcing with Kylon Resumes parsed, candidates scored and outreach managed from one room. - ![Greenhouse](https://kylon.io/v2/integrations/small/greenhouse-io.webp) - ![LinkedIn](https://kylon.io/v2/integrations/small/linkedin-com.webp) - ![Airtable](https://kylon.io/v2/integrations/small/airtable-com.webp) - ![Google Calendar](https://kylon.io/v2/integrations/small/google-calendar.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/talent-sourcing)