Skip to content
GitHub

Feature overview

Everything below is on main. The table matches the Features table in the README row for row; areas with their own page link to it in the last column, the rest show ”—”.

AreaWhat you getPage
Access & orgRBAC (menus / buttons / data scopes) · row-level data permissions · department tree · users & rolesUsers, roles, departments and menus · Data permissions
Import & exportserver-side xlsx / csv export (current filter or selected rows · large exports run in the background and notify you when done · formula-injection safe) · generic import (templates with dropdowns · preview & validation · insert only / upsert / update only · error report · all-or-nothing) · build a whole department tree from one fileImport and export
Sign-in & securitycaptcha · lockout · password history & expiry · SMS code sign-in · two-factor auth (TOTP + recovery codes) · OAuth2 (GitHub / Google) · session management (idle timeout + absolute limit · per-client session caps · tells users why they were signed out · force sign-out)Sign-in and security
Workspacecustomizable dashboard (cards appear by permission · layout saved per user on the server) · multi-tab (pin / drag / reload) · command palette ⌘K · shortcuts · guided tour · column visibility and drag-to-reorder (kept in the URL) · theme / radius / tab style · per-user time zone · Chinese & EnglishDashboard and workspace · Multi-tab
Files & storagefile manager with previews (pdf / docx / xlsx / images / archives) · local + S3-compatible storage · pre-signed downloads · recycle bin · instant upload · chunked & resumable uploads · attachment panel for any pageFiles and storage
Approval workflowform designer · flow tree (approve / CC / conditional branches) · approve / reject / transfer / send back / take back / add approvers · timeout reminders and auto-actions · drafts · urgent · handover · AI pre-review / form filling / AI approval nodesApproval workflow
AI assistantfull-page chat + side drawer · tool calls bound by permissions and data scopes · preview + confirm for writes · audit log · MCP gatewayAI assistant
Open APIAK/SK-signed endpoints · scopes / IP allow-list / replay protection / rate limits · call logs · incremental sync · Python / Node / Java SDKs · webhook subscriptions (Standard Webhooks signatures · retries · delivery log · bulk resend)Open API
Messages & notificationsin-app notifications (real-time) · notices (rich text + attachments · audiences · scheduled publishing · pinned / level / expiry · pop-up after sign-in with required acknowledgement · top banner · sign-in page notices · read stats) · notification routing (email / SMS / Feishu · DingTalk · WeCom group bots · per-event policies · delivery log) · SMS (Alibaba Cloud / Tencent Cloud)Messages and notifications
Scheduled jobsonline scheduling · cron preview · run historyScheduled jobs
Operationssettings · dictionaries · sign-in / operation logs (redacted) · data change history (who changed which field from what to what, when and from where · linked to the operation log) · server & Redis monitoring · new-version prompt · a single health check URL for external monitoringLogs and audit · Monitoring and health checks · Config and data dictionary
ClientsElectron desktop (installers for three platforms · silent printing · local hardware · auto-update) · native Expo app (not a WebView wrapper)Desktop and mobile
Developerscomponent sandbox (every component tweakable and copy-pasteable) · color palette · type-safe API contract generated from OpenAPIDeveloper tools · Plugins
DatabasesPostgreSQL · SQL Server · MySQL, one codebase and one migration chainDatabases

Which menu is each feature in, and does it work on the phone?

Section titled “Which menu is each feature in, and does it work on the phone?”

The desktop app loads the web build directly, so everything on the web is on the desktop too; the table compares the web and the mobile app only. The Plugin column is the directory name under apps/api/backend/plugin/; empty means core. Menu names are from the seed data and each deployment can change them.

FeatureWeb menuPluginMobile app
Sign-in and securityProfile · Monitoring → Active sessions · System → ConfigSMS sign-in needs sms, third-party sign-in needs oauth2Password / SMS sign-in, can enter a two-factor code; users required to enrol must do so on the web first
Users · roles · departments · menusSystem → Users / Roles / Departments / MenusUser list → detail → delete (as a pattern to copy)
Data permissionsSystem → Data permissionsFiltering happens in the backend, so lists in the app are scoped the same way
Multi-tab · dashboard— (shell) · DashboardThe home tab is a fixed layout (notices, my approvals, shortcuts); no layout editing, no tabs
Import & exportToolbar of each list pageNone
Files and storageSystem → Files / StorageNotice attachments only
Approval workflowApprovals → Approval center / Workflow definitions / Instance monitorworkflowTo-dos, details, starting a request
In-app messages · noticesBell in the top bar · System → Noticesnotification · noticeReadable, not real-time (refreshes on open or pull-down)
Notification channels · SMSNotifications → Notification policy / Delivery records · SMS → SMS configurations / SMS logsnotification · sms · emailNone
AI assistantAI assistantaiNone
Open APIOpen platform → ApplicationsopenNone
Scheduled jobsScheduler → Tasks / Task historyNone
Config · dictionariesSystem → Config · Dictionariesconfig · dictNone
Logs and auditLogs → Sign-in log / Operation log / Data changesNone
MonitoringMonitoring → Active sessions / Server / RedisServer

The mobile app has only been checked by hand on Android; see Desktop and mobile for its scope and limits.

The repository keeps its rules and pitfalls next to the code: a root CLAUDE.md and 40+ module notes (AGENTS.md), each indexed by task (“adding a list page”, “changing the permission model”, “writing a migration”). Every entry follows the same shape — symptom, cause, fix, and the measurement or test that proves it — and pnpm ctx:check runs in CI to catch notes that point at files, scripts or test IDs that no longer exist.

Yes: sign in to the live demo as admin / 123456. It is shared by everyone, so data may change under you, and it may lag a release or two behind main.