HR relationship access
Managers and HR partners see only the employees—and compensation—they are entitled to, mirroring real org structure instead of one big employee export for every user.
Playbooks are ready-made business packages you install in the dashboard. Each one brings a clear picture of your world—customers, employees, invoices, or clinical teams—so people and AI work from the same governed context. Build your own with the playbook generator and export a zip to install in OSS.
These are starter packs contributed for the open-source project—install any of them from the dashboard to explore a real domain with sample data. You can fork, adapt, or publish your own playbook for others to use.
Managers and HR partners see only the employees—and compensation—they are entitled to, mirroring real org structure instead of one big employee export for every user.
Reps see accounts they own; territory leaders see their region; deal values appear only when the user already has a legitimate path to the account—so pipeline data stays in the right hands.
Clinicians and coordinators see patients in their clinic panel; sensitive clinical notes follow the same rules—nurses may see the panel without seeing every note—so clinical AI stays within care boundaries.
A living org chart: people, companies, and employment—so “who works where?” is a shared fact for HR, leadership, and assistants.
A lightweight customer view linking contacts to accounts—ideal when you need a connected CRM picture without a full product rollout first.
Trusted invoice facts in the graph for reporting and AI Q&A—amounts and vendors agents can cite instead of guessing from document snippets.
Follow spend from invoice to purchase order, vendor, and cost center—one place to answer “what did we commit to and who billed us?”
Tickets tied to the right customer and contact—so support leads see workload by account and agents answer from customer context, not ticket text alone.
Upstream systems keep their column names while the business shares one clean Customer model—fewer conflicting definitions in reports and bots.
One golden profile per customer or vendor across ERP, billing, and support—so duplicates stop polluting answers and analytics.
Bad rows wait for human review instead of silently entering the graph—stewards get a queue, not surprises weeks later.
A catalog of contracts and documents linked to parties—agents know what exists and what it relates to before opening full file stores.
Products, parts, and suppliers in one BOM-style view—see which finished goods are affected when a part or vendor changes.