Every privileged change leaves a fingerprint.
Custom roles built permission-by-permission. An append-only audit log behind every billing, role, and approval change. Two-factor sign-in that admins can require for their whole team. Plan-level feature gating so the wrong people can never see the wrong screen.
Four primitives, all shipped today.
No fine print, no “coming in Q3.” These are the four governance surfaces every Fruitful organisation has from day one.
Custom roles, built permission-by-permission
Name the role. Tick the boxes. Ship it. Pre-built roles for HR, Finance, Manager, Team Lead are ready — or build your own from a flat permission list.
Append-only audit log
Every role grant, permission change, billing transition, 2FA reset, and attendance edit lands in audit_logs. Filterable by actor, action, subject, date.
Two-factor — opt in, or require for admins
TOTP-based two-factor lives in every user’s profile. Org admins can flip one switch to require it for everyone with admin access — including themselves.
Plan-level feature gating
Each plan switches modules on or off. If a feature isn’t part of your plan, the screen still appears with a clear upgrade prompt — never a 404, never a leaked permission.
Seventeen minutes, one fingerprint.
A manager corrects a clock-out by seventeen minutes. Here is everywhere that change shows up — without anyone writing a single line of compliance code.
AuditService::log() in the same request. Append only, no edit endpoint.
From signup to a live audit trail, in four steps.
The path most enterprise organisations take. Each step uses features that ship today — no professional services package, no implementation engineer required.
Stand up the admin team
Sign in, build the four roles you actually need (HR, Finance, Manager, Team Lead, or your own), and require two-factor sign-in for everyone with admin access.
- Custom roles + permission picker
- Require 2FA across the org
- First audit entries land
Invite your employees
Bulk-invite by CSV or department. Every employee acknowledges the consent screen on first agent run. Transparent monitoring starts capturing immediately.
- Bulk invitations + departments
- Consent flow before any capture
- Live status grid populates
Define what productive means
Set productivity rules for the apps and URLs your team uses. Assign shifts and timezones. The desktop agent classifies in real time from there.
- App + URL classification
- Shift scheduler with timezones
- Idle + activity thresholds
Review the receipts
Filter the audit log by actor for your first security review. Pull productivity reports as PDF or CSV. Set data-retention windows for screenshots.
- Audit log filter + export
- Reports · CSV + PDF
- Retention configured by plan
The toggle that makes admins sign their name.
Stealth mode hides the monitoring indicator from employees. It is the most regulator-sensitive setting in the product, so we wrote a one-screen legal acknowledgement an admin has to read and tick before enabling it. The acknowledgement is captured in the audit log with the admin’s name and timestamp.
We default to transparent mode because most jurisdictions require employees to be told. This page is not legal advice.
Asked by every security review.
Where is our data stored?
Do you support SSO?
How are screenshots protected?
Can a manager edit attendance silently?
Can we use the platform for in-house staff?
Does the AI see screenshots or passwords?
Can our finance team get a real audit trail of billing?
audit_logs via AuditService::logBilling().
Bring the procurement checklist. We’ll work down it together.
Trial the full product for 14 days, no card, audit log capturing from minute one. Or book a 30-minute walkthrough with our team — bring any procurement questions your security team flagged.