-
Notifications
You must be signed in to change notification settings - Fork 15
Multi Tenancy Progress
Part of the Multi-tenancy section. Planned / in active development. Tracks the build against the plan. Last updated: 2026-06-21.
Legend: β done Β Β·Β π§ in progress / next Β Β·Β β¬ not started
Where things stand: the foundation is complete and tickets are starting to scope by company β you can create companies, switch between them in the header, and the ticket list filters to the selected company. Email routing (per-company mailboxes) and the other modules are still ahead.
The invisible plumbing. None of this changes anything on a single-company install.
- β
tenantstable + a silent Default company that owns all existing data - β
tenant_domainstable (for future email-domain routing) - β Analyst β company access model (which staff can see which companies, + an "all companies" flag)
- β
tenant_idon tickets (every existing ticket assigned to the Default company) - β Shared tenancy helper β the single choke-point all tenant logic routes through
- β Active-company session context
- β Company switcher in the header (appears only once a 2nd company exists)
- β System β Companies admin page (list / create / rename companies)
Making the tickets module company-aware.
- β Ticket list scopes to the active company
- β New tickets are stamped with the active company
- π§ Folder count badges scope to the active company (next up)
- β¬ Ticket detail / remaining ticket endpoints scoped (defence-in-depth)
So an MSP can receive each client's email and have it land under the right company.
- β¬ Link mailboxes to companies (pinned = one mailbox per company, shared intake = one inbox sorted by sender)
- β¬ Register each company's email domains
- β¬ Route incoming email to the right company by sender domain
- β¬ Triage queue for unmatched / unknown senders
- β¬ Replies sent from the company's own mailbox (outbound identity)
(Today, all incoming email lands under the Default company β a fine interim state.)
- β¬ Assets, CMDB, Change Management, Calendar, Forms, Network Mapper
- β¬ Knowledge β per-company and global articles (two-axis visibility)
- β¬ Per-module Settings: split into global vs per-company
- β¬ Global requester identity β one login, tickets across companies, each badged
- β¬ Portal scoping + the "only your own tickets" guardrails
- β¬ Per-company branded portals / per-company SSO (optional, later)
- β¬ README documentation (deferred until the feature nears release)
- β¬ Companies: delete / archive management (today you can only deactivate)
- β¬ Automated isolation tests (guarding against one company seeing another's data)
This page is maintained by hand as work lands β see the GitHub roadmap issue (#24) for live discussion.
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
- Architecture
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- Theming & Dark Mode
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
- MobileβFriendly
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ Basic IMAP mailboxes
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- Problem Management
- Tasks
- Assets
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
- Forms
- Contracts
- Service Status
- π Notifications
- π¨ War Room
- Self-Service Portal
- LMS
- Process Mapper
- CMDB
- Network Mapper
- Workflows
- Issue trackers (Jira, Azure DevOps)
- System
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)