REST API: Knowledge module guide + how-it-works updates
REST API: Changes module guide incl. CAB workflow + how-it-works updates
REST API: Problems module guide (company-scoped) + how-it-works updates
REST API: Assets module guide + how-it-works updates (assets shipped, scope note)
REST API v1: how-it-works deep dive + Tickets endpoint guide (per-module pattern); link from Home/sidebar/API-Reference
Add Theming & Dark Mode wiki page Documents the token model (var(--token, #light-fallback) → light pixel- identical + non-themed pages safe), server-rendered data-theme/-mode, the token vocabulary, registry + per-module → global resolution, the account-menu picker, TinyMCE skin-swap + Chart.js handling, gotchas, and two checklists (theme a page / add a palette). Includes a "Scaling to many palettes" section on how the same token contract supports any number of named palettes as drop-ins. Linked from the sidebar.
Mailbox Authentication: fix User.Read contradiction; add opt-out note The "least privilege" line wrongly still said FreeITSM doesn't request User.Read. Corrected, and added a "Prefer not to grant User.Read?" section: it's optional (lowest-privilege, self-consent), only used for alias resolution, with two zero-permission alternatives (use the primary address, or app-only). Framed honestly as a trade-off, not unavoidable.
Mailbox Authentication: alias-awareness + corrected User.Read story Delegated safeguards now capture the mailbox's full address set (primary + UPN + proxyAddresses aliases), so a target that's an alias is accepted. Updated the scopes 101 to reflect that User.Read is now requested (low-privilege, user-consentable) to resolve aliases, with graceful degradation when absent. Added an alias troubleshooting row.
Add Mailbox Authentication page (delegated vs app-only, scopes 101) New page covering the two Microsoft auth modes, when to use each, the "reading from the right inbox" safeguards (issue #26), a plain-English OAuth scopes/permissions primer (incl. why User.Read is NOT needed), Azure app-registration setup, Google note, and troubleshooting. Linked from Tickets.md and the sidebar.
i18n: note pt-BR (Brazilian Portuguese) now 100% complete across all modules
Problem Management wiki: picker modals, notes journal, tables, phase-2 ideas Update incident/change linking to describe the searchable multi-select pickers and right-click "Link to problem", add the Notes journal + History sections, note the ?change_id= deep-link standardisation, and list phase-2 ideas.
Add Problem Management module page + sidebar link
Multi-tenancy: document moving a ticket to the right company
WhatsApp: inbound media + 15s live refresh
WhatsApp: document message templates (reply after the 24h window)
WhatsApp: Test button now covers reachability + inbound simulation
WhatsApp: note the per-channel Test connection button
WhatsApp: Graph API version is now a form field, not a DB edit
WhatsApp: Cloudflare Tunnel for firewalled installs + Meta Cloud API setup
WhatsApp: note the Public base URL setting
Add WhatsApp channel page + sidebar link
Document 2026-06-27 work: portal SSO, multi-tenant SSO, System tools, Trash - Single-Sign-On: self-service portal SSO (portal-aware callback, user_sso_identities, auto-claim), multi-company company-owned providers + email-domain routing, providers Company column. - Self-Service-Portal: SSO sign-in for requesters. - System: Help, Topology, Orphaned tickets, Debug Tools restructure + D003/D004. - Tickets: manual-ticket send-from mailbox, Trash with restore (+ drag/right-click/empty). - API-Reference: new endpoints. - Multi-Tenancy-Progress: per-company SSO done; admin visibility tools.
Wiki end-of-session refresh: index status, progress (isolation/settings/analyst access done + deferred cross-module reads)
Staff-access wiki: document the per-analyst company-access control (now built)
Add Multi-Tenancy-Isolation page: isolation model + the three-sweep hardening audit
Multi-tenancy settings: per-company add/hide (types+origins) + rationale for global-only settings
Multi-tenancy wiki: per-sender-address routing, freemail list, routing diagnostics (#563-567)
Multi-tenancy wiki: mark Phase 1 tickets + Phase 2 email routing as built Progress tracker: count badges done; Phase 2 (pinned/shared mailboxes, domain routing, triage queue, freemail handling) now complete bar outbound reply identity. Email-routing + landing pages updated from 'planned' to 'built on the multi-tenancy branch'. Parked ideas (routing visualiser, customisable freemail list) noted.
Add Multi-tenancy progress tracker page
Link multi-tenancy pages to roadmap issue #24