[{"data":1,"prerenderedAt":1123},["ShallowReactive",2],{"help:\u002Fhelp\u002Fteam\u002Flog-an-employee-incident":3,"help-all-categories":175,"help-cat-articles:\u002Fhelp\u002Fteam\u002Flog-an-employee-incident":295,"help-related:\u002Fhelp\u002Fteam\u002Flog-an-employee-incident":296},{"id":4,"title":5,"audience":6,"body":7,"category":154,"description":155,"draft":156,"extension":157,"icon":158,"keywords":159,"meta":165,"navigation":166,"order":167,"path":168,"related":169,"seo":171,"stem":172,"updatedAt":173,"__hash__":174},"help\u002Fhelp\u002Fteam\u002Flog-an-employee-incident.md","Log an employee incident","clinic",{"type":8,"value":9,"toc":137},"minimark",[10,14,23,28,88,91,97,101,108,112,116,119,123,126,130],[11,12,13],"p",{},"The incident log is a confidential HR record on each team member's panel: what happened, how serious it was, and what you did about it. Only admins and owners can see or write it — the person it concerns never sees the tab.",[11,15,16,17,22],{},"For an event involving a client, visitor, or the venue itself, use ",[18,19,21],"a",{"href":20},"\u002Fhelp\u002Foperations\u002Frecord-and-follow-up-on-incidents","Record and follow up on venue incidents",".",[24,25,27],"h2",{"id":26},"how-do-i-record-an-incident","How do I record an incident?",[29,30,31,36,47,51,62,66,81,85],"steps",{},[32,33,35],"h3",{"id":34},"open-the-incidents-tab","Open the Incidents tab",[11,37,38,42,43,46],{},[39,40,41],"strong",{},"Team"," → click the member → ",[39,44,45],{},"Incidents",". The tab is only visible to admins and owners.",[32,48,50],{"id":49},"add-the-incident","Add the incident",[11,52,53,54,57,58,61],{},"Pick a ",[39,55,56],{},"category"," — attendance, conduct, performance, safety, client complaint, policy, or other — and a ",[39,59,60],{},"severity",": minor, serious, or gross.",[32,63,65],{"id":64},"describe-it","Describe it",[11,67,68,69,72,73,76,77,80],{},"Set the date and time it occurred and write what happened. Optional fields capture the ",[39,70,71],{},"business impact",", the ",[39,74,75],{},"action taken",", and any ",[39,78,79],{},"follow-up"," planned.",[32,82,84],{"id":83},"save","Save",[11,86,87],{},"The incident joins the member's log, timestamped and attributed to you.",[11,89,90],{},"Backdating is expected — you're documenting something that already happened — but an incident can't be dated in the future.",[92,93,94],"warning",{},[11,95,96],{},"Incidents are confidential HR records. Write them as you'd want them read in a dispute: factual, dated, specific, and free of speculation. The log can be exported when you need the full record.",[24,98,100],{"id":99},"marking-an-incident-as-protected","Marking an incident as protected",[11,102,103,104,107],{},"An incident can be flagged ",[39,105,106],{},"protected"," for particularly sensitive records. ",[24,109,111],{"id":110},"common-questions","Common questions",[32,113,115],{"id":114},"can-the-employee-see-their-incident-log","Can the employee see their incident log?",[11,117,118],{},"No. Incidents are admin\u002Fowner-only and are never shown to the subject inside Owneli. Whether and how you share them is your HR process, not the software's.",[32,120,122],{"id":121},"should-every-complaint-become-an-incident","Should every complaint become an incident?",[11,124,125],{},"Use the log for things you'd want a dated record of — patterns of lateness, a client complaint, a safety event. One-off coaching conversations usually don't need one.",[32,127,129],{"id":128},"how-does-this-relate-to-offboarding","How does this relate to offboarding?",[11,131,132,133,22],{},"They're independent, but a well-kept incident log is what makes a termination defensible. See ",[18,134,136],{"href":135},"\u002Fhelp\u002Fteam\u002Fsuspend-archive-or-offboard-a-team-member","Suspend, archive, or offboard a team member",{"title":138,"searchDepth":139,"depth":139,"links":140},"",2,[141,148,149],{"id":26,"depth":139,"text":27,"children":142},[143,145,146,147],{"id":34,"depth":144,"text":35},3,{"id":49,"depth":144,"text":50},{"id":64,"depth":144,"text":65},{"id":83,"depth":144,"text":84},{"id":99,"depth":139,"text":100},{"id":110,"depth":139,"text":111,"children":150},[151,152,153],{"id":114,"depth":144,"text":115},{"id":121,"depth":144,"text":122},{"id":128,"depth":144,"text":129},"team","Record a confidential HR incident on a team member's profile — category, severity, what happened, and the action taken.",false,"md","i-lucide-flag",[160,161,162,163,164],"employee incident log","hr record staff","document staff conduct","staff disciplinary record","incident report team member",{},true,70,"\u002Fhelp\u002Fteam\u002Flog-an-employee-incident",[20,135,170],"\u002Fhelp\u002Foperations\u002Fpolicies",{"title":5,"description":155},"help\u002Fteam\u002Flog-an-employee-incident","2026-08-14","vvEBRGunRWymWWp6wcek1jIn3OWb5uXgqAWLeaYpwZ8",[176,187,196,205,215,225,235,244,254,264,274,285],{"id":177,"title":178,"audience":6,"description":179,"extension":180,"icon":181,"meta":182,"order":183,"slug":184,"stem":185,"__hash__":186},"helpCategories\u002Fhelp\u002Fcategories\u002Fgetting-started.yml","Getting started","Set up your workspace, learn the layout, and run your first day.","yml","i-lucide-compass",{},1,"getting-started","help\u002Fcategories\u002Fgetting-started","lTnfg_2tKvxQ9QanJ9XY3shoBHrJNWNfnxhcYaaKKPI",{"id":188,"title":189,"audience":6,"description":190,"extension":180,"icon":191,"meta":192,"order":139,"slug":193,"stem":194,"__hash__":195},"helpCategories\u002Fhelp\u002Fcategories\u002Fcalendar.yml","Calendar & booking","Book, move, and cancel appointments. Block time, work the waitlist, and read the grid at a glance.","i-lucide-calendar",{},"calendar","help\u002Fcategories\u002Fcalendar","s5UMHzRIeTUFi7mdsOyuSluzJBp79U9WTsTpOtbaW-E",{"id":197,"title":198,"audience":6,"description":199,"extension":180,"icon":200,"meta":201,"order":144,"slug":202,"stem":203,"__hash__":204},"helpCategories\u002Fhelp\u002Fcategories\u002Fcheckout.yml","Checkout & payments","Ring up a sale, take tips, handle deposits and fees, issue refunds, and close the drawer.","i-lucide-credit-card",{},"checkout","help\u002Fcategories\u002Fcheckout","4PQPgJd7Z25g0SvtoqqdMlnzk3DlcJpaZhNAiNiYVW0",{"id":206,"title":207,"audience":6,"description":208,"extension":180,"icon":209,"meta":210,"order":211,"slug":212,"stem":213,"__hash__":214},"helpCategories\u002Fhelp\u002Fcategories\u002Fclients.yml","Clients & forms","Add and find clients, read a client profile, and send forms and consents.","i-lucide-users",{},4,"clients","help\u002Fcategories\u002Fclients","u-tqzEJo2gR_wJ7x7y-EMIF3L4TP9EuBWlamwgwCC0I",{"id":216,"title":217,"audience":6,"description":218,"extension":180,"icon":219,"meta":220,"order":221,"slug":222,"stem":223,"__hash__":224},"helpCategories\u002Fhelp\u002Fcategories\u002Fretail.yml","Memberships, packages & gift cards","The things clients buy once and spend down over time, and how each one behaves at checkout.","i-lucide-gift",{},5,"retail","help\u002Fcategories\u002Fretail","wVVr_rc_P9p2RZWwy0XKsNB9fQ7XtQxxIz4qnixkGkg",{"id":226,"title":227,"audience":6,"description":228,"extension":180,"icon":229,"meta":230,"order":231,"slug":232,"stem":233,"__hash__":234},"helpCategories\u002Fhelp\u002Fcategories\u002Foperations.yml","Operations","The internal side of the business, covering your written playbook, task boards, venue incidents, and the policies everyone signs.","i-lucide-briefcase",{},6,"operations","help\u002Fcategories\u002Foperations","kSPRTYYbOW5LBNuaYXGv0C4IE7BqS2n-OkCSI97f-cM",{"id":236,"title":237,"audience":6,"description":238,"extension":180,"icon":239,"meta":240,"order":241,"slug":154,"stem":242,"__hash__":243},"helpCategories\u002Fhelp\u002Fcategories\u002Fteam.yml","Team & scheduling","Working hours, the weekly roster, clock-in, timesheets, and time off.","i-lucide-id-card",{},7,"help\u002Fcategories\u002Fteam","1cMbCRwUmewb4t_DwUJ7jJUjntx-odU8jRDgBredsPs",{"id":245,"title":246,"audience":6,"description":247,"extension":180,"icon":248,"meta":249,"order":250,"slug":251,"stem":252,"__hash__":253},"helpCategories\u002Fhelp\u002Fcategories\u002Fgrowth.yml","Reports & growth","Read the numbers, export them, and find the report you actually need.","i-lucide-trending-up",{},8,"growth","help\u002Fcategories\u002Fgrowth","3XyCU-DkoYi7xSPz0tDRohlYkNBUS0YsLo-insknI8o",{"id":255,"title":256,"audience":6,"description":257,"extension":180,"icon":258,"meta":259,"order":260,"slug":261,"stem":262,"__hash__":263},"helpCategories\u002Fhelp\u002Fcategories\u002Fsettings.yml","Settings & admin","Services and pricing, who can see what, and moving your data in from another system.","i-lucide-settings",{},9,"settings","help\u002Fcategories\u002Fsettings","rdLQHp7tfAu5iySbsypfXu1kOuujDAuLVk6yGidNvtQ",{"id":265,"title":266,"audience":6,"description":267,"extension":180,"icon":268,"meta":269,"order":270,"slug":271,"stem":272,"__hash__":273},"helpCategories\u002Fhelp\u002Fcategories\u002Faccount.yml","Your login and profile","Your own login, password, two-factor security, profile, and language.","i-lucide-user-circle",{},10,"account","help\u002Fcategories\u002Faccount","8JZPH_8Q-lnEEFgysE9gCwyd1pzUe2hfAebATuQ5Pog",{"id":275,"title":276,"audience":277,"description":278,"extension":180,"icon":279,"meta":280,"order":281,"slug":282,"stem":283,"__hash__":284},"helpCategories\u002Fhelp\u002Fcategories\u002Fbook-online.yml","Book online","client","Booking, paying, and managing your visit from your venue's booking page and the private links they send you.","i-lucide-globe",{},20,"book-online","help\u002Fcategories\u002Fbook-online","dUBIoELt-ci1vqbw_VX1VA6PGJV8V-9x4ZmpAk1aXXE",{"id":286,"title":287,"audience":277,"description":288,"extension":180,"icon":289,"meta":290,"order":291,"slug":292,"stem":293,"__hash__":294},"helpCategories\u002Fhelp\u002Fcategories\u002Fportal.yml","Your account and visits","Booking from your account, managing your visits, and using your wallet, memberships and rewards.","i-lucide-user-round",{},21,"portal","help\u002Fcategories\u002Fportal","D8_zQhv9hO2b9PYDADw-ebh1yZUuC0UcBt3DDZbMAH4",[],[297,591,821],{"id":298,"title":21,"audience":6,"body":299,"category":232,"description":576,"draft":156,"extension":157,"icon":577,"keywords":578,"meta":584,"navigation":166,"order":585,"path":20,"related":586,"seo":587,"stem":588,"updatedAt":589,"__hash__":590},"help\u002Fhelp\u002Foperations\u002Frecord-and-follow-up-on-incidents.md",{"type":8,"value":300,"toc":560},[301,306,309,314,318,324,360,368,371,375,457,460,464,471,484,487,490,494,505,508,512,519,526,533,537,547,550,553,557],[11,302,303],{},[39,304,305],{},"Operations → Incidents",[11,307,308],{},"Use Incidents to keep a record of something that happened at your venue: what occurred, who was involved, what your team did, and what still needs attention. An incident can concern a client, a visitor without a client record, or an event with no identifiable person.",[11,310,311,312,22],{},"This is separate from the confidential HR log on a team member's profile. For attendance, performance, or employee conduct records, see ",[18,313,5],{"href":168},[24,315,317],{"id":316},"who-can-use-incidents","Who can use Incidents?",[11,319,320,321,323],{},"Access follows your role's ",[39,322,45],{}," permissions:",[325,326,327,340],"table",{},[328,329,330],"thead",{},[331,332,333,337],"tr",{},[334,335,336],"th",{},"Permission",[334,338,339],{},"What you can do",[341,342,343,352],"tbody",{},[331,344,345,349],{},[346,347,348],"td",{},"View",[346,350,351],{},"Read the incident list and individual records.",[331,353,354,357],{},[346,355,356],{},"Manage",[346,358,359],{},"View records, file incidents, update the response, close or reopen a matter, and download reports.",[11,361,362,363,367],{},"Client access and blocking have separate permissions. Being able to file an incident does not give you access to every client's profile or contact details. Ask an administrator to review ",[18,364,366],{"href":365},"\u002Fhelp\u002Fsettings\u002Froles-and-permissions","Roles and permissions"," if an action is missing.",[11,369,370],{},"Incident records are internal. They are not displayed to the person named in the client portal.",[24,372,374],{"id":373},"file-an-incident","File an incident",[29,376,377,381,391,395,398,402,416,420,434,437,441,444,447,451],{},[32,378,380],{"id":379},"open-the-form","Open the form",[11,382,383,384,386,387,390],{},"Go to ",[39,385,305],{}," and choose ",[39,388,389],{},"File incident",". On mobile, use the add button in the page header.",[32,392,394],{"id":393},"record-when-and-where-it-happened","Record when and where it happened",[11,396,397],{},"Enter the date and time the event occurred. You can record a past event, but not a future one. Check the location, especially if your business has several venues. The form may select your active location or your only location automatically.",[32,399,401],{"id":400},"identify-the-subject","Identify the subject",[11,403,404,405,407,408,411,412,415],{},"Choose an existing ",[39,406,277],{},", a ",[39,409,410],{},"visitor",", or ",[39,413,414],{},"no identifiable person",". For a visitor, provide a name or a factual description. You do not need to create a client account just to document an event.",[32,417,419],{"id":418},"describe-the-event","Describe the event",[11,421,422,423,426,427,411,430,433],{},"Choose a category and a severity of ",[39,424,425],{},"minor",", ",[39,428,429],{},"serious",[39,431,432],{},"critical",". Add a short summary and a detailed description of what happened.",[11,435,436],{},"Categories cover solicitation of sexual services, harassment, threats or violence, theft, payment issues, intoxication, property damage, trespass, safety, privacy, and other events.",[32,438,440],{"id":439},"record-the-response-and-people-involved","Record the response and people involved",[11,442,443],{},"Add any action already taken and any planned follow-up. If police were notified, record that and add the police reference if available. This records a notification you have already made; it does not contact the police.",[11,445,446],{},"You can add witnesses, affected people, and responders. Select a staff member or enter another person's name, with relevant contact information and notes. A record supports up to 20 people in this section.",[32,448,450],{"id":449},"review-and-file","Review and file",[11,452,453,454,22],{},"Check the subject, time, category, severity, description, and people before saving. The record receives an incident reference, identifies who filed it, and starts as ",[39,455,456],{},"Open",[11,458,459],{},"Write observable facts and distinguish what you witnessed from what someone told you. For example, “At 14:10, the visitor knocked a display onto the floor; Alex witnessed it” is more useful than a judgement about the visitor's character. Include only information needed to document the event and the response.",[24,461,463],{"id":462},"update-the-response","Update the response",[11,465,466,467,470],{},"Open the incident and select ",[39,468,469],{},"Edit response",". You can update:",[472,473,474,478,481],"ul",{},[475,476,477],"li",{},"Action taken.",[475,479,480],{},"Planned follow-up.",[475,482,483],{},"Whether police were notified and the police reference.",[11,485,486],{},"Save your changes when finished. Follow-up is a written record; it does not automatically schedule a task or send a reminder.",[11,488,489],{},"The original narrative, subject, category, severity, date, location, and people involved cannot be edited after filing. If you need to correct or clarify the original account, explain the correction in the follow-up, with a date and context, so readers can understand what changed.",[24,491,493],{"id":492},"close-or-reopen-the-matter","Close or reopen the matter",[11,495,496,497,500,501,504],{},"Choose ",[39,498,499],{},"Close incident"," when the required response is complete. Closing keeps the record available; it does not delete it. Choose ",[39,502,503],{},"Reopen incident"," if further attention is needed.",[11,506,507],{},"Use the incident list's status and category filters to find open matters or review similar events.",[24,509,511],{"id":510},"block-a-client-when-appropriate","Block a client when appropriate",[11,513,514,515,518],{},"Filing an incident does ",[39,516,517],{},"not"," automatically block the client.",[11,520,521,522,525],{},"For a linked client, users with the required client-management permission can choose ",[39,523,524],{},"Block client",". The block form suggests a reason and includes the incident reference. Review and confirm it separately. Some reasons, including the safety designation, require additional authority.",[11,527,528,529,22],{},"The incident shows the client's current blocked status. Closing the incident does not unblock the client. Manage that separately using ",[18,530,532],{"href":531},"\u002Fhelp\u002Fclients\u002Fblocked-and-flagged-clients","Blocked and flagged clients",[24,534,536],{"id":535},"download-a-report","Download a report",[11,538,539,540,542,543,546],{},"Users with ",[39,541,356],{}," permission can choose ",[39,544,545],{},"Download report"," to save a PDF. The report includes the incident record and your business branding, where configured. Its timestamps use the incident location's time zone, falling back to the business time zone and then UTC.",[11,548,549],{},"The download is recorded in the audit log. Client contact and sensitive details follow the exporting user's permissions, so a report may omit information the user cannot access. Review the PDF before sharing it through your business's chosen process. Downloading does not send it to police, insurers, or the client.",[11,551,552],{},"Repeated exports are limited. If you see a message about too many reports, wait before trying again.",[24,554,556],{"id":555},"why-can-i-no-longer-open-a-record","Why can I no longer open a record?",[11,558,559],{},"Your role may no longer have access, you may be in a different organization, or the linked client's record may have been restricted following an erasure request. A restricted record cannot be opened or exported through the ordinary incident screens. Ask your administrator to review the restriction rather than creating a duplicate record to bypass it.",{"title":138,"searchDepth":139,"depth":139,"links":561},[562,563,571,572,573,574,575],{"id":316,"depth":139,"text":317},{"id":373,"depth":139,"text":374,"children":564},[565,566,567,568,569,570],{"id":379,"depth":144,"text":380},{"id":393,"depth":144,"text":394},{"id":400,"depth":144,"text":401},{"id":418,"depth":144,"text":419},{"id":439,"depth":144,"text":440},{"id":449,"depth":144,"text":450},{"id":462,"depth":139,"text":463},{"id":492,"depth":139,"text":493},{"id":510,"depth":139,"text":511},{"id":535,"depth":139,"text":536},{"id":555,"depth":139,"text":556},"File a factual record of a venue incident, document your response, close or reopen the matter, and download a report.","i-lucide-siren",[579,580,581,582,583],"venue incident report","client incident","visitor safety harassment theft","police insurance report pdf","incident follow up",{},40,[531,168,365,170],{"title":21,"description":576},"help\u002Foperations\u002Frecord-and-follow-up-on-incidents","2026-09-19","6GIwILJ6dpgkEdmPZDgQVBq7Qffa4rqC-KPs7z3TCWY",{"id":592,"title":136,"audience":6,"body":593,"category":154,"description":804,"draft":156,"extension":157,"icon":805,"keywords":806,"meta":813,"navigation":166,"order":814,"path":135,"related":815,"seo":818,"stem":819,"updatedAt":173,"__hash__":820},"help\u002Fhelp\u002Fteam\u002Fsuspend-archive-or-offboard-a-team-member.md",{"type":8,"value":594,"toc":790},[595,610,613,617,685,689,748,762,767,769,773,776,780,783,787],[11,596,597,598,601,602,605,606,609],{},"When someone leaves — or you need to lock them out fast — use the ",[39,599,600],{},"Offboarding"," tab on their team panel. ",[39,603,604],{},"No access"," (suspend) locks the login but keeps everything else intact; ",[39,607,608],{},"Archive"," runs a wizard that resolves their future appointments first, then records the departure. Both are reversible.",[11,611,612],{},"Admin access is required. The owner and the last active admin are protected — they can't be suspended or archived.",[24,614,616],{"id":615},"suspend-vs-archive-which-one","Suspend vs archive: which one?",[325,618,619,632],{},[328,620,621],{},[331,622,623,626,629],{},[334,624,625],{},"Action",[334,627,628],{},"What it does",[334,630,631],{},"When to use it",[341,633,634,647,660,672],{},[331,635,636,641,644],{},[346,637,638,640],{},[39,639,604],{}," (suspend)",[346,642,643],{},"Locks the login immediately. Their data, appointments, and history stay untouched.",[346,645,646],{},"Urgent lockout, investigation, extended leave",[331,648,649,654,657],{},[346,650,651],{},[39,652,653],{},"Restore access",[346,655,656],{},"Unlocks a suspended account",[346,658,659],{},"The situation is resolved",[331,661,662,666,669],{},[346,663,664],{},[39,665,608],{},[346,667,668],{},"Full offboarding: future appointments reassigned, last day and reason recorded, member removed from active rosters",[346,670,671],{},"The person has actually left",[331,673,674,679,682],{},[346,675,676],{},[39,677,678],{},"Reinstate",[346,680,681],{},"Reverses an archive, with an optional note",[346,683,684],{},"A rehire or a mistake",[24,686,688],{"id":687},"archive-someone-the-wizard","Archive someone: the wizard",[29,690,691,695,704,708,723,727,737,741],{},[32,692,694],{"id":693},"open-offboarding","Open Offboarding",[11,696,697,42,699,701,702,22],{},[39,698,41],{},[39,700,600],{}," tab → ",[39,703,608],{},[32,705,707],{"id":706},"resolve-the-blockers","Resolve the blockers",[11,709,710,711,714,715,718,719,722],{},"The wizard won't continue while the member has ",[39,712,713],{},"future appointments",", an ",[39,716,717],{},"active clock-in",", or an ",[39,720,721],{},"open cash drawer",". Recent paid hours show as a warning (make sure payroll is settled) but don't block.",[32,724,726],{"id":725},"reassign-their-future-appointments","Reassign their future appointments",[11,728,729,730,733,734,22],{},"Every upcoming appointment and add-on is listed. Assign each to a specific provider or leave it on ",[39,731,732],{},"Any available",", then choose what clients are told: notify where the provider is client-visible, notify everyone, or notify no one. Click ",[39,735,736],{},"Apply",[32,738,740],{"id":739},"confirm-the-offboarding","Confirm the offboarding",[11,742,743,744,747],{},"Record the ",[39,745,746],{},"last working day"," (required), a reason category, optional context, vacation payout days, and knowledge-transfer notes. Confirm to archive.",[11,749,750,751,754,755,758,759,761],{},"After archiving, the member's row shows ",[39,752,753],{},"Offboarded",". Tick ",[39,756,757],{},"Include offboarded"," in the team directory to see them; their panel shows the offboarding record — who archived them, when, why — with a ",[39,760,678],{}," action.",[92,763,764],{},[11,765,766],{},"Reassignment moves real client bookings. Pick the notify option deliberately — \"notify no one\" leaves clients expecting a provider who won't be there.",[24,768,111],{"id":110},[32,770,772],{"id":771},"does-suspending-someone-cancel-their-appointments","Does suspending someone cancel their appointments?",[11,774,775],{},"No. Suspension only locks their login. Their appointments stay on the calendar — if they'll actually be gone, reassign or reschedule those separately, or archive instead.",[32,777,779],{"id":778},"why-cant-i-archive-the-owner","Why can't I archive the owner?",[11,781,782],{},"The owner and the last remaining active admin are protected so a workspace can never lock itself out. Transfer ownership or promote another admin first.",[32,784,786],{"id":785},"what-happens-to-their-historical-sales-and-timesheets","What happens to their historical sales and timesheets?",[11,788,789],{},"Nothing — history is preserved. Archiving affects access and future scheduling, not past records, so reports and payroll stay accurate.",{"title":138,"searchDepth":139,"depth":139,"links":791},[792,793,799],{"id":615,"depth":139,"text":616},{"id":687,"depth":139,"text":688,"children":794},[795,796,797,798],{"id":693,"depth":144,"text":694},{"id":706,"depth":144,"text":707},{"id":725,"depth":144,"text":726},{"id":739,"depth":144,"text":740},{"id":110,"depth":139,"text":111,"children":800},[801,802,803],{"id":771,"depth":144,"text":772},{"id":778,"depth":144,"text":779},{"id":785,"depth":144,"text":786},"Lock a team member's access, or archive them for good with the offboarding wizard that reassigns their future appointments first.","i-lucide-log-out",[807,808,809,810,811,812],"remove staff member","suspend staff access","offboard employee","archive team member","reassign appointments leaving staff","reinstate employee",{},60,[816,168,817],"\u002Fhelp\u002Fteam\u002Finvite-a-team-member","\u002Fhelp\u002Fcalendar\u002Freschedule-cancel-and-no-shows",{"title":136,"description":804},"help\u002Fteam\u002Fsuspend-archive-or-offboard-a-team-member","RPCPXlkirWkQ9JwxC9Dp0o18tvJvfK7p54AvhbWGCtY",{"id":822,"title":823,"audience":6,"body":824,"category":232,"description":1113,"draft":156,"extension":157,"icon":1114,"keywords":1115,"meta":1116,"navigation":166,"order":1117,"path":170,"related":1118,"seo":1119,"stem":1120,"updatedAt":1121,"__hash__":1122},"help\u002Fhelp\u002Foperations\u002Fpolicies.md","Policies — reading, signing, and authoring",{"type":8,"value":825,"toc":1103},[826,831,834,840,844,847,850,856,862,867,871,878,947,957,961,983,987,990,994,1003,1010,1013,1017,1023,1026,1033,1037,1097],[11,827,828],{},[39,829,830],{},"Operations → Policies",[11,832,833],{},"Policies are the HR and compliance layer — code of conduct, health and safety, privacy, harassment, attendance, social media, confidentiality, the employee handbook.",[11,835,836,837,839],{},"They sit in ",[39,838,227],{},", not in Settings, because every employee has to read and sign them. Only authoring is restricted.",[24,841,843],{"id":842},"if-youre-an-employee","If you're an employee",[11,845,846],{},"You need to do two things: read the policy, and acknowledge it.",[11,848,849],{},"When a policy that requires acknowledgment is published — or its version is bumped — you're prompted to sign at your next sign-in. Read it, then acknowledge.",[851,852,853],"note",{},[11,854,855],{},"Your signature and its timestamp are permanently logged against the exact version you signed. That record is the point of the feature: it's what proves the business told you, and what proves you read it.",[11,857,858,859,861],{},"You can revisit any policy at any time from ",[39,860,830],{},". If you can read but not author, the sidebar shows a small eye icon next to the link — that's expected, not a fault.",[92,863,864],{},[11,865,866],{},"Acknowledgment prompts are skipped on read-only reporting pages, so a manager reviewing numbers isn't blocked by an HR overlay on every report. The prompt still reaches you everywhere else, and the notification bell keeps the item visible.",[24,868,870],{"id":869},"if-you-author-policies","If you author policies",[11,872,873,874,877],{},"Authoring needs the policy-management permission. ",[39,875,876],{},"New policy"," offers five ways in:",[325,879,880,890],{},[328,881,882],{},[331,883,884,887],{},[334,885,886],{},"Route",[334,888,889],{},"Use it when",[341,891,892,902,912,927,937],{},[331,893,894,899],{},[346,895,896],{},[39,897,898],{},"Start from a template",[346,900,901],{},"You want a solid starting draft. Templates prefill your business name, HR contact and jurisdiction.",[331,903,904,909],{},[346,905,906],{},[39,907,908],{},"AI Policy Studio",[346,910,911],{},"You want a draft generated from a description. Only available when the AI assistant is enabled for your business.",[331,913,914,919],{},[346,915,916],{},[39,917,918],{},"Upload a document",[346,920,921,922,926],{},"You already have the policy as a PDF, ",[923,924,925],"code",{},".docx",", or HTML file.",[331,928,929,934],{},[346,930,931],{},[39,932,933],{},"Paste HTML",[346,935,936],{},"You're bringing it from another system. The pasted markup is sanitised before it's stored.",[331,938,939,944],{},[346,940,941],{},[39,942,943],{},"Blank",[346,945,946],{},"You'd rather write it yourself.",[11,948,949,950,952,953,956],{},"Uploads accept PDF, ",[923,951,925],{}," and ",[923,954,955],{},".html"," only, and are size-limited — the editor tells you the maximum.",[32,958,960],{"id":959},"fields","Fields",[472,962,963,971,977],{},[475,964,965,968,969],{},[39,966,967],{},"Title"," and optional ",[39,970,56],{},[475,972,973,976],{},[39,974,975],{},"Summary"," — a one-liner shown in lists and on the acknowledgment overlay. Worth writing well; for many staff it's the only part they read carefully.",[475,978,979,982],{},[39,980,981],{},"Require acknowledgment"," — when on, every employee must sign it at next login",[32,984,986],{"id":985},"draft-then-publish","Draft, then publish",[11,988,989],{},"A new policy is created as a draft. Review it — particularly the extracted text from an upload or the sanitised output of a paste — and publish when you're satisfied.",[32,991,993],{"id":992},"versions-and-re-acknowledgment","Versions and re-acknowledgment",[92,995,996],{},[11,997,998,999,1002],{},"Bumping a policy's version ",[39,1000,1001],{},"resets everyone's acknowledgment"," and asks the whole team to sign again. That's correct for a substantive change and wasteful for a typo. Save the version bump for changes that alter what someone is agreeing to.",[11,1004,1005,1006],{},"When you edit and re-publish with a version bump, the app confirms it: ",[1007,1008,1009],"em",{},"\"Version bumped. Team must re-acknowledge.\"",[11,1011,1012],{},"You can also replace the attached file on an uploaded policy — the signature record then attaches to the file you uploaded.",[24,1014,1016],{"id":1015},"compliance-tracking","Compliance tracking",[11,1018,1019,1022],{},[39,1020,1021],{},"Compliance"," (admin only) shows, per employee: how many policies they've acknowledged, out of how many, as a percentage — plus exactly which ones are missing.",[11,1024,1025],{},"A policy someone signed at an older version is flagged separately from one they've never signed, so you can tell \"hasn't read it at all\" from \"read the previous edition\".",[11,1027,1028,1029,1032],{},"Filter to ",[39,1030,1031],{},"only missing"," to get your chase list.",[24,1034,1036],{"id":1035},"policies-versus-notes","Policies versus notes",[325,1038,1039,1051],{},[328,1040,1041],{},[331,1042,1043,1045,1048],{},[334,1044],{},[334,1046,1047],{},"Policies",[334,1049,1050],{},"Notes",[341,1052,1053,1064,1075,1086],{},[331,1054,1055,1058,1061],{},[346,1056,1057],{},"Subject",[346,1059,1060],{},"Conduct, safety obligations, privacy, employment",[346,1062,1063],{},"How to do the work",[331,1065,1066,1069,1072],{},[346,1067,1068],{},"Who can author",[346,1070,1071],{},"Policy-management permission only",[346,1073,1074],{},"Anyone who can create notes",[331,1076,1077,1080,1083],{},[346,1078,1079],{},"Who can read",[346,1081,1082],{},"Everyone with policy view",[346,1084,1085],{},"Depends on the note's visibility",[331,1087,1088,1091,1094],{},[346,1089,1090],{},"Signature",[346,1092,1093],{},"Permanently logged against the version",[346,1095,1096],{},"Acknowledgment logged, optional per note",[11,1098,1099,1100,22],{},"If it would go in an employee handbook, it's a policy. If it would go on a laminated card by the machine, it's a ",[18,1101,851],{"href":1102},"\u002Fhelp\u002Foperations\u002Fnotes-your-team-playbook",{"title":138,"searchDepth":139,"depth":139,"links":1104},[1105,1106,1111,1112],{"id":842,"depth":139,"text":843},{"id":869,"depth":139,"text":870,"children":1107},[1108,1109,1110],{"id":959,"depth":144,"text":960},{"id":985,"depth":144,"text":986},{"id":992,"depth":144,"text":993},{"id":1015,"depth":139,"text":1016},{"id":1035,"depth":139,"text":1036},"What every employee has to do with a policy, how authors create one from a template, upload or paste, and how compliance is tracked.","i-lucide-shield-check",[],{},30,[1102,365],{"title":823,"description":1113},"help\u002Foperations\u002Fpolicies","2026-07-26","Olc7gRagEd7UYBUv2Ug9gJ9Km9IBKV4mIQ6NWjhd-7w",1790210905552]