Organizations
MuninX uses the word organization in two different ways:
- Tenant organization: your MuninX workspace. It represents the business using MuninX to provide support.
- Customer organization: an optional record inside your tenant organization. It represents a company, account, client, or group that receives support from you.
Tenant organization
Section titled “Tenant organization”When you create an account on muninx.com, MuninX creates a tenant organization for your business.
For example, if a small software company called Northstar Apps signs up for MuninX, Northstar Apps becomes the tenant organization. Its admins and support agents log in to that tenant organization to answer tickets, manage settings, invite team members, and review reports.
Support agents are part of the tenant organization. They are not part of customer organizations.
Tenant organization settings include the organization ID, display name, logo, customer access settings, reply identity, auto-solve and auto-close, billing, and team management.
Customer organizations
Section titled “Customer organizations”Customer organizations exist inside a tenant organization. They are useful when you support other businesses, clients, accounts, or groups and want to keep their customers, domains, and tickets grouped together.

A customer organization can include:
- Display name.
- Domains.
- External reference URL.
- Notes.
- Status.
- Avatar or logo.
Customer organizations are optional. If you support individual customers, consumers, or a small number of accounts that do not need grouping, you can create customer records without assigning them to a customer organization.
Domains and restricted email access
Section titled “Domains and restricted email access”When email ticket creation is set to Restricted, emails sent from any domain associated with a customer organization are allowed.
Deleting a customer organization
Section titled “Deleting a customer organization”Deleting a customer organization also deletes all customers that belong to that organization.
Ticket organization history
Section titled “Ticket organization history”When a customer creates a ticket, MuninX records the customer’s organization on that ticket at creation time.
If the customer is later moved to a different customer organization, existing tickets stay linked to the original organization. New tickets use the customer’s current organization.
This preserves the historical context of each support request. For example, a customer using a personal email address could change companies later; MuninX should not move tickets created for the first company into the second company’s history.
Customer organization statuses
Section titled “Customer organization statuses”Customer organization statuses include active, pending, suspended, and inactive.
If a customer organization is set to Suspended, customers belonging to that organization cannot log in, new customers cannot be added to that organization, and new tickets cannot be created by email for that organization’s domains unless Customer Access Settings is set to Open.