Skip to main content

Key Terms

Type: ReferenceCreated: Team: Platform
draft

Skapp and its editions​

  • Skapp — Rootcode's people- and work-management platform. The core covers HR and people operations; separate modules add project management and more.
  • Core — the main Skapp application (the skapp repo): the HR/people modules and the shared platform they run on. Next.js frontend, Spring Boot backend.
  • Community edition — the open-source Skapp core, on its own.
  • Enterprise edition — the same core plus paid features, layered in through git submodules. See Getting Set Up.
  • Submodule — the git mechanism that pulls enterprise-only code into the core repo. A plain clone of skapp is incomplete until submodules are initialized.
  • Tenant (organization) — one customer organization. The enterprise edition is multi-tenant: each tenant gets its own database, isolated from the others. The community edition runs a single organization.

The core modules​

A module is a self-contained capability area — its own frontend feature folder and backend package. The ones you'll hear about:

  • People — employee records and the directory.
  • Attendance / Time — clock-in/out and timesheets.
  • Leave — leave requests and balances.
  • OKR — objectives and key results.
  • CRM — customer-relationship features.

Enterprise adds more on top, including eSignature, Invoice.

One naming gotcha: the backend package for a module often carries a planner suffix while the user-facing name is shorter — Attendance is timeplanner, People is peopleplanner. Same module, two names.

Project management terms​

The PM module (skapp-pm) is project management — a separate repo and stack (Next.js + NestJS + GraphQL), not part of the core. Its vocabulary:

  • Project — the top-level container for a team's work.
  • Board — where a project's work is tracked and moved through stages.
  • Sprint — a time-boxed iteration of work.
  • Item — the unit of work: a Story, Bug, or Task. PM's word for a "ticket."

The supporting services​

  • UI library (skapp-ui) — shared React components used by both the core and PM front ends; published to GitHub's npm registry as @rootcodelabs/skapp-ui.
  • AI service (skapp-ai) — a Python service that powers the chatbot and insights, answering questions over the PM module's data.
  • Migration service (skapp-migrations) — runs database migrations across tenants, for both MySQL and Postgres.

Handbook words​

  • The handbook — this site. Engineering docs only; everything else lives in other tools.
  • The editor — the custom app where docs are written.
  • The reader — the Docusaurus site where docs are browsed.
  • The validator — checks every doc's frontmatter, headings, and Markdown against the rules before it's saved.

The authoring vocabulary — frontmatter, doc_type, owner_team, status — is defined in How Our Docs Work. New to navigating the handbook? Our Reading Guide shows you how to find anything.