Life Empowerment — Case Management

System

Checking…

Sign in

Session

File round-trip

Registry (Phase 1, Area 1)

Read-backs through the new registry actions — the lists show only what this account's roles and program grants allow (deny by default).

Incidents (Phase 1, Area 2)

Read-backs for the incident family — one person's records across the six report kinds, and the Coordinators cross-client queue. Both lists show only what this account may view.

Professional Collaboration (Phase 1, Area 3)

Read-backs for Professional Collaboration Forms — one person's records, showing only what this account may view; the office block appears only for Coordinators and up.

Daily Documentation + Goals (Phase 1, Area 4)

Read-backs for Daily Data Collection, Daily Record of Support, and the Goals registry — plus the Coordinators cross-client worklists. All lists show only what this account may view.

Person's Inventory (Phase 1, Area 5)

Read-backs for the per-person belongings inventory — the list shows only what this account may view.

Human Resources (Phase 2, Area 1)

Staff records under the two access tiers, enforced server-side: the full tier (Director, Site Administrator, owner accounts) sees everything including the restricted block; the limited tier (Coordinator, Admin Staff) gets the Details fields only — the restricted block never leaves the server — and documents/certificates refuse. Terminated staff sit in the inactive view.

Timecards (Phase 2, Area 2)

Timecard entries under the standing rules, enforced server-side: an entry is viewable only by the staff member who entered it, and editable only by the owner accounts — corrections are exercised from the Back Office Timecard Corrections list (owners, Site Administrators, and Directors may view it; every owner edit preserves the original in a corrections ledger). Match states are computed against the program shift calendars: matched (green), unmatched (red border), non-shift categories (amber). My Shift Schedule is view-only and shows only your own scheduled shifts.

Leave Requests (Phase 2, Area 3)

Leave under the standing rules, enforced server-side: a request submitted with Identified Coverage = None is auto-declined at submission with the exact standing reason. Decisions are manual, by Admin Staff, Coordinators, Directors, Site Administrators, and the owner accounts, with a decision reason; approval sends the coverage person an in-site notification (denial never does). Your own requests are editable only while Pending — decided requests are locked; the Coordinators Leave Requests List below can override status and coverage. The conflict flag shows when the coverage person is already scheduled or on approved leave in the window. Approval never moves your vacation bank — the balance shown on your own list is read-only.

Performance Evaluation (Phase 2, Area 4)

The paired evaluation, enforced server-side: your self-evaluation and the evaluator's form for the same Evaluation Type are ONE evaluation on one open cycle — the evaluator form attaches to your open cycle and cannot start a parallel one. Your self-evaluation is editable until you submit it; submitting locks it (display-only after). You never see the evaluator's half anywhere in this system, and the evaluator never sees yours here — the two halves meet only in the owners' combined review in the Back Office surface below, where an owner can tick Completed (which closes the cycle and locks both halves). The form renders from the server catalogue: 64 items, sections A–G, ratings 1–5 or N/A, a comment per section, and the workplan on the self form only.

Coordinator Checklist (Phase 2, Area 5)

One checklist store, three surfaces, enforced server-side. The person page is the working surface: only that person's ASSIGNED coordinator may mark it (assignment accepts only Coordinator-role staff; re-assignment replaces the assignee and is audit-logged) — Directors and up view it but do not mark. The At-A-Glance lists only the signed-in coordinator's own assigned persons with the day's counts. The Directors' Summary (Directors and up, view-only) rolls the week up per coordinator with the "No coordinator assigned" bucket. The standing template (five morning tasks, Mon–Fri, the Specific Expectations text) is stored data that Directors/owners can edit; coordinators cannot change it, but can add their own extra tasks. Every state change is kept in the mark history — never overwritten. Past weeks are locked.

Back Office (Phase 3, Area 1)

Back Office core, enforced server-side. The landing page is the LEI Admin Meeting Room Calendar: Admin Staff, Coordinators, Directors, Site Administrators and the owner accounts can see, add, edit and remove bookings (any of them may manage any booking — the shared room rule); below Admin Staff the calendar does not exist. Overlapping bookings are flagged at save, never silently double-booked and never blocked. The Archived registry is Directors-and-up, organized by person + document type with file-name search; every filing links a stored file whose SHA-256 is verified on read, and removal is owner-only. Company Inventory is the company-wide property list (distinct from a person's inventory); its delete is owner-only. Allegation of Abuse Reports can be created by anyone who can open the person's record — the creator then receives a reference only and cannot read it back — and can be read only by Directors and the owner accounts (not Coordinators, not Admin Staff, not a Site Administrator who is neither); every Director/Owner read is audit-logged, open reports sort by Final Report Due with Due/Overdue badges, and delete is owner-only.

LEI Admin Meeting Room Calendar

Archived (Directors and up; removal owners only)

Company Inventory

Allegation of Abuse Reports

Create from a person's record (reporter section only — office and funder fields are never in the creator's form and are server-stripped if sent). Directors and owners read completed reports in the registry below; everyone else is refused by the server.

Back Office Files (Phase 3, Area 2)

Drop boxes with named-person visibility, Policies in Word, and the two meeting-minutes drop points.

Drop boxes

Policies in Word

Meeting minutes

Program Tools (Phase 3, Area 3)

Master File (the 12 Policy A-5 folders), Programming Tools (six plan areas), Residence Documents, Emergency Response Drills, the Key Registry, and the Communication Log. Document files are capped at 25 MB per file.

Master File

Programming Tools

Residence Documents

Emergency Response Drills

Key Registry

Communication Log

Report Launcher (Phase 3, Area 4)

Coordinator and up. The report only ever includes people and programs you can access. Allegation of Abuse reports are never included.

Announcements + Pictures (Phase 3, Area 5)

Four locations, each its own entity. Posting — Home / Employee Services / OHS Bulletin Board: Admin Staff and up; Coordinators Portal: Coordinator and up. Deleting an announcement: owners only. Pictures (JPG/PNG/WebP/GIF, up to 25 MB each) run the location's posting gate; click a picture to enlarge it in-page.

Pictures

Picture viewer

Close viewer

Announcements + Home (Phase 3, Area 5)

The portal compositions: Home (announcements, the shared links column, birthday entries, the Casual Calendar), the Employee Services landing (Employee Announcements + the SAME shared links, composed with your timecards and leave), and the OHS portal (Bulletin Board announcements, OHS links, and the meeting minutes from the existing minutes store). Saving links and birthdays: Admin Staff and up. Casual availability: your own entries, or anyone's for Admin Staff and up. Deleting any of these entries: owners only.

Links

Home birthdays

Casual availability (Home Casual Calendar)

OHS Portal (Phase 3, Area 6)

The OHS portal landing (Bulletin Board announcements 2/3 + the links column 1/3) is composed above; this panel works the portal's sidebar surface — the OHS Meeting Minutes drop point, its own list on the shared minutes store. Everyone signed in can view and download minutes; adding, editing and removing them is Admin Staff and up (plus the owner accounts).

OHS Meeting Minutes

Employee Services — Policy Manual + Documents (Phase 3, Area 7)

The Policy Manual is ONE page: the Forward and Handbooks first, then Sections A–G as groupings, each section's document list in its own scroll box (refinement §21); a title search spans the whole manual and its matches display uncapped. Everyone signed in can view and download; uploading, editing, replacing and removing documents is Director + Site Administrator + owner accounts only (§18). Any file type files (§17 addendum — the PDF-only check was removed). The Documents group holds two links: Performance Evaluation (the self-evaluation entry — Phase 2, Area 4 panel above) and the Employee Satisfaction Survey (§26 — built in Phase 4; its panel follows this one).

Employee Services — Employee Satisfaction Survey (Phase 4)

The ShareVision survey ported whole (§26): a flat form of 13 questions, all required — Current Position, Position Location, tenure, then ten 1–5 ratings (1 – Strongly Agree … 5 – Strongly Disagree). Any signed-in account can submit; a submitted response is not shown to its submitter again. Results (responses + aggregates) are owners + Site Administrator + Director only, and deleting a response is owner-identity only. ANONYMITY: the submission stores a hidden submitter link in the data layer that is NEVER displayed — no read on this page (or anywhere) returns it. Attachments ride the file store: choose a file and it uploads first, then links to the submission.

Site Admin (Phase 3, Area 8)

Site Admin tooling over the Phase 1 substrate: user accounts (provision, update, lifecycle, owner/admin password reset — passwords are one-way hashes, reset is the only recovery; deletion is owner-identity only and soft), the permission matrices (portal rows, per-role and per-staff link overrides, program grants), permission preview, the audit reads, and the Recycle Bin. The bin reads every soft-deleted store directly: restore runs each feature's own delete gate, permanent delete is owner-only everywhere, and the stored file behind a filing is never touched by either act. Below-gate actors are refused by the server on every verb; the refusals show on the message line.

Accounts

Permissions

Permission preview

Audit

Recycle Bin

Edit Mode + Menu Arrange (Phase 3, Area 9)

The owners' presentation layer. Edit mode edits a form's layout — rename labels, hide and restore items (fields, sections, headings, buttons, help text, picklist options), reorder items, add picklist options, add custom fields, reset a form — and menu arrange mode saves one order per menu that every user's rendering follows. Both are gated by owner identity (never role): a Site Administrator who is not an owner is refused by the server on every write, and writes fail closed while a permission preview is active. The layer is presentation only: it never changes validation, calculations, permissions, workflow or stored data — a hidden item's field still validates and its record still reads back in full. Workflow-status picklists (Trip Request, Allegation of Abuse) are locked against adding options. Menu visibility is untouched by ordering: an item a role cannot see keeps its slot in the saved order and simply does not render for them.

Form layout

Menu arrange