Set up your workspace

A fresh Muninnbase tenant comes with safe defaults for everything. You can technically invite your whole team in the next five minutes and they would have a working knowledge base. But spending fifteen minutes on the basics first pays for itself. The first time your team logs in, they should see your company's name and logo. Not ours.

Why this matters

Most of the settings on this page are set-and-forget. You touch them once, during the first week. Everything you do here happens at /admin/settings. Open that page in another tab while you read.

The order below is the order we recommend setting things up: branding first because it changes what your team sees, then password policy if you have a specific compliance requirement, then a quick pass over data retention and retrieval tuning. The rest can wait until you have a reason to revisit them.

Branding

Three fields in the Branding section make your tenant feel like your business.

App name. The text shown in the chat header where your employees ask questions. The default is "Muninnbase." Change it to your company name if you want the chat surface to read like an internal tool ("Acme Helpdesk") rather than a third-party product.

Logo. Upload your company logo. We accept PNG, JPG, JPEG, and SVG. The image is auto-resized to fit 120 by 40 pixels. A horizontal lockup with the company name beside the mark reads best at that aspect ratio.

Chat avatar. This is the small circular image that sits next to every answer from the assistant. Same accepted file types, auto-resized to 40 by 40 pixels. A simple icon or mark works better than a full logo at that size.

Password policy

Four toggles control how strict employee passwords have to be. Minimum length (default 8), require an uppercase letter, require a number, require a special character. Default is on for everything except special character.

The honest answer for most small businesses is: leave it alone. The defaults are reasonable and your team will thank you for not requiring "Tr0ub4dor&3" passwords. Only tighten this if you have a specific compliance requirement (HIPAA, SOC 2, a client contract) that mandates it. Loosening it is almost never worth doing.

Email is automatic

Muninnbase sends invites, password reset links, billing receipts, and trial-ending warnings through Resend. There is nothing to configure on your end. No SMTP server to set up, no API key to paste, no fallback URLs to copy and forward by hand. As soon as you invite someone or trigger a password reset, the email goes out.

If a user reports an invite or reset email that did not arrive, the first thing to check is their spam folder. New senders sometimes get filtered the first time.

Data retention

Q&A logs and their source citations are kept for 30 days by default. The dropdown gives you 7 days, 30 days, 90 days, 1 year, and Keep all. Lower retention is friendlier to privacy-conscious teams; longer retention is friendlier to admins who want to look back across the quarter and see what their team was asking.

Two things to know. First, shortening the window does not just affect future logs. It triggers an immediate purge of older entries the next time the retention job runs. The settings page warns you before applying the change. Second, the unanswered events queue (the list of questions your team thumbed-down or that the system could not answer) is never purged automatically. Those stick around until you mark them resolved or wipe the tenant.

Retrieval tuning (brief)

Two retrieval tuning knobs are visible on the settings page. The similarity threshold (a slider) controls how confident retrieval needs to be before the system attempts an answer. Below the threshold, Muninnbase tells the user it does not have an answer rather than guessing. The cross-encoder reranker (a toggle) rescores retrieved chunks for a better ordering. Default is on.

These defaults are well-tuned. If you want to understand what each one does and when to adjust, see Retrieval tuning.

What to skip for now

The Danger Zone at the bottom of the settings page has two buttons: "Remove my data" and "Delete and close account." Neither is part of setup. The first wipes all your documents and Q&A history while keeping the tenant alive. The second deletes the tenant entirely. Both require typing a confirmation phrase. Stay away from them unless you actually mean it.

Advanced retrieval tuning beyond the two knobs above is also worth skipping until your team has been using the product long enough to give you a reason to change something. Default settings work for the vast majority of small-business knowledge bases.

What to do next

With branding set and the basics confirmed, the next useful step is putting documents in. Five to ten of your most-asked-about files turn an empty workspace into a useful one. See upload your first documents.

Once documents are indexed, invite and manage your team walks through bringing employees in.