Tracker

Purpose

Generic data tracking for any entity shape. Trackers, typed fields, permissions, views, and widgets without knowing projects, products, or customers. Industry meaning stays in application packs — Keystone owns the configurable store.

In a product

We model jobs, inventory, or customer notes as trackers in your app — same engine, your field names, layouts, and permissions.

How it works

1. You define a tracker (a board / entity type) scoped to an organization.
2. You add typed fields — text, status, people, dates, currency, and more.
3. Users create records (and optional subitems); the engine validates and coerces values.
4. Views and widgets present the same data as tables, boards, timelines, or KPI shells.
5. Creates, updates, and deletes can publish tracker.record.* events for Automation.

Capabilities

• Org-scoped tracker CRUD with archive and settings
• Thirteen field types, pin limits, record vs subitem scopes
• Views: table, kanban, analytics, dashboard, timeline
• Widget shells for KPIs, charts, tables, and schedules
• Role-based tracker permissions
• Record validation, duplication, and optional event publish
• API routes under /v1/trackers (fields, views, widgets, permissions, records)

Related

Event · Workflow · Automation