The security questionnaire
"Can admins review account activity?" is a standard question from enterprise buyers. "Not yet" stalls deals; a screenshot of an audit page closes the topic.
Use case
Give every workspace an account history page — role changes, billing actions, security events — with one API and none of the schema, retention, or pagination work.
The problem
"Can admins review account activity?" is a standard question from enterprise buyers. "Not yet" stalls deals; a screenshot of an audit page closes the topic.
Someone removed a teammate, changed a role, or deleted data — and nobody remembers doing it. Without an audit trail, support can only shrug.
Schema, ingest validation, cursor pagination, scoped reads, retention, export — the "quick events table" that eats a quarter.
How it works
One call at each choke point: invites, role changes, billing, API keys, exports, deletions. Under ten calls covers most B2B SaaS.
Append-only storage with actor snapshots — history stays intact even after users are deleted or renamed. Retention is enforced automatically by plan.
Drop the feed component into account settings for a per-workspace audit page, or query the REST API for custom admin views. Export CSV/JSON any time.
import { log } from '@/lib/softechlog';
log.track({
actor: { id: user.id, name: user.name, email: user.email },
action: 'member.role.changed',
target: { type: 'workspace', id: target.id, name: target.name },
metadata: { from: 'member', to: 'admin' },
});FAQ
No. There is no update or per-event delete path — corrections are recorded as new events, and deletion only happens via plan-based retention. That append-only property is what makes the trail usable as evidence.
Yes. Your server mints a short-lived feed token scoped to one actor; the browser never holds a credential that can read anyone else’s events.
Yes — CSV or JSON export with full filtering is available on every plan, including Free.
Keep reading
Ready to try it? Beta partners get hands-on onboarding and a schema review.
Request Beta Access