Qmarkets provides different ways to separate users, content, and processes within the platform. Two of the main options are Tenants and Subsystems.
While both help organizations manage multiple activities in the same environment, they serve different purposes.
- Tenants are mainly used to separate audiences and experiences while keeping the same process.
- Subsystems are used when different activities require separate workflows, configurations, and management.
This article explains the differences between them and provides guidance on when each option should be used.
What is a Tenant?
A Tenant creates separation between audiences while keeping the same core process.
Each tenant can have its own:
- Homepage experience
- Campaigns
- Ideas
- News
- Branding
- Reports and KPIs
Users may automatically be routed to their relevant tenant based on their profile or assignment.
Common use cases for Tenants:
- Different countries
- Business units
- Internal vs. external users
- Different branding
- Separate content visibility
- Different sender email addresses
What is a Subsystem?
A Subsystem is designed for organizations that manage different processes.
Each subsystem may contain independent:
- Workflows
- Submission forms
- Roles
- Categories
- Business rules
- Dashboards
- Reports
- Automation logic
Subsystems are often used for completely different business activities.
Common use cases for Subsystems:
- Idea management
- Startup scouting
- Project portfolios
- Patent processes
Key Differences
| Capability | Tenant | Subsystem |
|---|---|---|
| Purpose | Separate audiences | Separate processes |
| Workflow | Shared workflow baseline | Independent workflows |
| Submission Form | Shared baseline | Independent forms |
| Branding | Separate branding | Independent branding |
| Reports | Tenant-level reports | Fully configurable reports |
| Roles | Tenant managers | Subsystem managers |
| Business Rules | Shared logic | Independent logic |
| Categories | Tenant values | Independent structures |
| Homepage | Tenant content | Independent layouts |
Administration Differences
Tenant Administration
Tenant administrators manage settings that affect their own tenant only.
Examples include:
- Homepage configuration
- Branding
- Tenant categories
- User assignments
- Limited workflow adjustments
Tenant admins cannot create independent workflows or subsystem configurations.
Subsystem Administration
Subsystem administrators have broader configuration capabilities.
They can manage:
- Workflow design
- Roles
- Categories
- Reports
- Business rules
- Dashboard settings
- Automation logic
Subsystem settings apply to the entire process managed within that subsystem.
How to Decide
| Requirement | Recommended Option |
|---|---|
| Same process, different audiences | Tenant |
| Different regions or departments | Tenant |
| Internal and external communities | Tenant |
| Different workflows | Subsystem |
| Different forms | Subsystem |
| Different stakeholders | Subsystem |
| Different entity types | Subsystem |
| Full process separation | Subsystem |
Summary
Choose a Tenant when you need different experiences for different users while keeping the same process.
Choose a Subsystem when different teams require separate workflows, configurations, and business logic.
For many organizations, combining both options provides the best balance between flexibility and governance.