Service line — client & SLA operations
Client management + multi-location facility structures + recurring task tracking + SLA compliance + partner portal — for service businesses where the client wants visibility on what's getting done, when, and where it stands.
Workspace-scoped client accounts. Linked profiles for the people responsible on each side. Deletion checks for dependencies (a client with active facilities or running SLAs can't be deleted accidentally). Foundation for Basic; everything else builds on top.
One client can have multiple facilities — locations, branches, venues, sites. Each facility carries its own recurring tasks, SLA scope, and notification routing. Useful for horeca chains, multi-office legal firms, education operators with multiple campuses, real-estate portfolio managers.
Per-facility recurring tasks (cleaning logs, equipment checks, monthly compliance reviews, supplier orders). Each task has a status — compliant, pending, issue. Dashboards roll up to facility-level percentages and client-level summaries. Operations leads see across the portfolio; venue managers see only their facility via role-gated access.
A live SLA compliance percentage rolls up from individual recurring tasks. Drill in to see which locations are pulling the number down, which tasks are overdue, who owns the next action. Useful for operations directors who need to see status without tapping their venue managers on the shoulder weekly.
Authenticated portal at /portal where the client sees their own facility data — recurring tasks, SLA status, recent activity. Membership lives in client_portal_users, gated by getPartnerPortalAccess. The client cannot see other clients' data. Provisioning happens on consent during reservation flow or by manual admin invite. EN/NL/AR locale-aware.
Every write checks role (admin / manager / contributor / portal-client) before mutating. Cross-workspace and cross-client data access is blocked at the database via Supabase Row Level Security — not at the application layer where a bug could leak. The client portal is structurally isolated from the admin workspace.
Replaces: spreadsheet-tracking of recurring tasks across locations · ad-hoc client status emails · a separate portal vendor for client visibility · the manager's manual Monday-morning compliance walk through every venue. Note: this is not a full CRM (HubSpot, Pipedrive remain that category) and not project management (Asana, Linear, Monday remain that category).
Client and SLA operations are available across both tiers — Basic from €499 setup + €50/month for foundational client records and single-location facility tracking; Pro from €899 setup + €699/month for multi-location SLA compliance, partner portal access, recurring task automations, and the rest of the workspace stack.
Basic vs Pro →Legibility Hub
Structured counts run through allowlisted database cards. Narrative context uses semantic retrieval only when needed. Hybrid answers separate deterministic facts from retrieved snippets and show provenance.
“What is overdue this week?”
structuredCounts overdue SLA tasks from scoped workspace tables.
“Which clients need attention and why?”
hybridCombines unresolved flags with recent semantic notes.
“What content exists for booking and legal workflows?”
semanticRetrieves relevant workspace semantic nodes with citations.
Query cards
Allowlisted
No generated text-to-SQL surface is exposed.
Metering
Only on synthesis
Structured-only answers avoid Gemini and do not burn credits.
Scope
Workspace RLS
No cross-workspace data access is claimed or allowed.
Booking lifecycle
The booking is not the end of the form. It can become a client record, confirmation trail, Legal Vault draft, and follow-up path.
Public availability and active/gated/unavailable states guide the intake.
Reservation changes create an operational trail instead of a lost inbox thread.
Portal-client provisioning can attach the booking to a future client workspace relationship.
Confirmed reservations can draft a service agreement into Legal Vault where enabled.
Public submissions run through honeypot and form-start timing checks before they become operational data.
Reservations
Lifecycle
Status history
Logged
Anti-abuse
Checked
