Skip to content

Domain deep dive — Platform & admin

Single D1 narrative for engineers working on portal identity, Singpass, website/tenant admin, or AI integration settings stored as DocTypes. It ties together:

In scopeOut of scope (link instead)
Singpass Token, UserLKA, Applicant, verification codesFull Singpass legal/compliance sign-off — vendor docs
OpenAI Settings, Google reCAPTCHAModel selection product strategy
Tenants Table, Features Group ListMulti-tenant billingFinance & AR
Log Data / prompt logsApplication business PDFs — Incorporation
Sub-themeExamples
Identity / portaluserlka, applicant, singpass_token, verifycodelka, resetkeylka
AI / safetyopenai_settings, google_recaptcha, prompt_log
Website / tenancytenants_table, features_group_list, addons_list
Ops logslog_data, log_data_list

Confirm exact membership in platform-admin — categorization rules live in generate-doctype-reference.mjs.

LayerPrimary locations
APIsleekimerp/api/user.py, api/website_faqs.py, api/company_search.py, Singpass-related packages — API inventory
DocType controllerslee_kim_alliance_erp/doctype/<name>/ per generated page
HooksGrep hooks.py for portal DocTypes when adding doc_events
PriorityDocType keysRationale
P1 — Overlays presentsingpass_token, userlka, openai_settings (see overlays.json)Auth/session, extended user, AI keys
P2google_recaptcha, applicant, verifycodelkaBot defense and onboarding
P3tenants_table, log_data, prompt_logMulti-tenant metadata and observability
SymptomFirst checks
Singpass login failsSingpass Token freshness, redirect URIs, Singpass
AI features downOpenAI Settings keys, rate limits, provider status
Spam signupsGoogle reCAPTCHA keys, server-side verification

Logs: Error Log, Log Data DocTypes if used for app-level tracing; never log raw tokens.