Tenant setup

Admins configure tenant settings from Settings > Tenant.

This page configures your tenant: the Muninx workspace that represents your business. It does not configure customer organizations, which are optional records for companies, clients, accounts, or groups that receive support from you.

Tenant ID and slug

The tenant ID is a server-generated, stable identifier for the tenant. The tenant slug is the editable, unique routing name used to build the support portal URL and inbound support email address.

Your inbound support email uses support@$TENANT_SLUG.muninx.com, where $TENANT_SLUG is the tenant’s current slug. Admins can find it in Settings > Tenant under Tenant Details.

To use an address on your own domain, complete both the external forwarding and Muninx sender-verification steps in Custom support email. The default address for the current slug continues to work after a custom sender is activated.

Treat the tenant ID as operational infrastructure. Use the display name for customer-facing naming, and update the slug carefully because it changes routing URLs and email addresses.

Before changing the tenant slug

Changing the slug immediately changes the default inbound support address. Muninx does not retain or redirect addresses that contain a historical slug. For example, changing acme to acme-support replaces [email protected] with [email protected]; the old address stops routing to the tenant.

The change can also affect replies to ticket notifications sent before the change. Their ticket-specific Reply-To addresses contain the old slug and can no longer route to the tenant. A verified custom sending address is independent of the slug and remains active, but any inbound forwarding rule for that custom mailbox must point to the new default address.

Use this checklist when changing a slug:

Record the new default support address shown in the confirmation dialog.
Immediately after changing the slug, update every external forwarding rule to the new address.
Update websites, contact pages, saved replies, and other published references to the default address.
Send a test email to the intended customer-facing address and confirm that Muninx creates a ticket.

Display name

The display name appears in customer-facing places such as notifications and the customer portal.

Use a recognizable company, product, or support team name. Avoid internal abbreviations that customers would not understand.

Tenant logo

Admins can upload and crop a tenant logo. The logo is used where Muninx shows tenant identity.

If reply identity is set to tenant identity, customers see tenant branding instead of individual agent names and avatars.

Reply identity only changes what customers see on responses they receive from agents. Admins and agents continue to see the real reply author, whether or not they are assigned to the ticket.

Platform support vs customer support

Muninx platform support is separate from your tenant inbound support email. Use Muninx support for account, billing, or platform help. Your customers use your tenant portal or inbound support email for their own tickets.