> For the complete documentation index, see [llms.txt](https://guide.mymodone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mymodone.com/readme.md). # Introduction ## Mission Control for Your Safety Program
modONE is a digital safety platform that keeps frontline workers engaged with short, regular safety lessons — delivered to the device they already carry, with no app and no login. It automates content delivery, gives you actionable engagement metrics, and adapts as your program requirements change. ### What modONE is not modONE is a safety platform. It is not a payroll, HR, or benefits system. It does not hold paystubs, W-2s, pay rates, hours worked, direct deposit details, or benefits enrollment. Team members with questions about any of those should contact their employer's HR or payroll department. See [Paystubs, W-2s, and Pay Questions](https://guide.mymodone.com/common-features/team-member-portal/pay-and-hr-questions). ### Start where you are {% hint style="info" %} **I'm a team member** — I get safety lessons by text or email. Start at [Start Here — Team Members](https://guide.mymodone.com/common-features/team-member-portal/start-here). **I'm an administrator** — I run the safety program for my organization. Start at the [Quick Start Guide](https://guide.mymodone.com/overview/quick-start-guide). **Something isn't working** — go to [Troubleshooting and Common Questions](https://guide.mymodone.com/troubleshooting). {% endhint %} You're reading the modONE User Guide, which covers everything you need to use the modONE platform — from basic concepts to advanced features, with step-by-step tutorials. We're constantly updating and improving this documentation. If you have a question it doesn't cover, or a suggestion for improvement, contact modONE Support at . --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://guide.mymodone.com/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.