> For the complete documentation index, see [llms.txt](https://kibu.gitbook.io/resource-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kibu.gitbook.io/resource-center/getting-started/getting-started-for-documentation-users.md). # Getting Started for Documentation Users This guide is here to help. Kibu provides a powerful platform that enables organizations to efficiently track service hours, documentation, medical information, and life plan goals—all from a phone or laptop. The video below walks you through a typical "day in the life" of an organization using Kibu's admin tools. Below that, you’ll find answers to common questions for key implementors to ensure a smooth onboarding experience. {% embed url="" %} A Brief Tour of Kibu for Admin Tooling (6:36) {% endembed %} ### **Will My Kibu Dashboard Look Exactly Like the One in the Video?** Likely not. Every organization has its own set of groups and customizations for attendance, time tracking, and note templates. The key Kibu implementors at your organization will work closely with Kibu's Head of Customer Success, [Ben Wallace](https://www.linkedin.com/in/benfwall/), to build a customized setup that works for your team. ### How Should I Prepare for Kibu Onboarding? * **Prepare your roster** of all your staff and members. Understand which roles each staff member requires in [our User Management article](/resource-center/reference/user-management.md). We can input data directly into Kibu or perform bulk uploads with an Excel spreadsheet. * **Think about how your people will be grouped** (by location? by program? by room?). A good group typically has 5-20 members. * **Think about your note template**. What questions should your staff answer about each member on each day? Note templates consist of short text, long text, dropdown, checkbox, and number selector options. A good note template has 1-4 questions. * **Will you be adding life plan goals of your members onto Kibu?** If so, do you expect staff to answer daily questions about them? For example, if Athena has a goal of improving social skills, you can ask a simple "Did Athena work on her social skills today" Yes/No question. Work with the Kibu team on what those might look like. * **Do you need time tracking in Kibu?** Some states only need "Present" or "Absent" for reporting, while others need the exact time they entered and left the facility. How are the rounding rules/units tracked for time? * **Develop a plan with Kibu for staff-wide training**. We can do a live video call, pre-recorded videos, and more. We're here to help! ### How Do I Report Ongoing Feedback, Questions, and Issues to Kibu? [Ben Wallace](https://www.linkedin.com/in/benfwall/) will be your designated support rep for all things Kibu! Any Kibu user can email at any time. You can also schedule a video call with him on [his booking calendar](https://cal.com/ben-wallace/30min). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kibu.gitbook.io/resource-center/getting-started/getting-started-for-documentation-users.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.