> ## Documentation Index
> Fetch the complete documentation index at: https://afrizon-admin.tunzaa.co.tz/llms.txt
> Use this file to discover all available pages before exploring further.
# How to configure your Meneja tenant settings
> Learn how to configure your tenant's domain, currency, country, languages, modules, support details, and legal links through the Meneja settings UI.
Every tenant in Meneja has a settings area where you control how your marketplace operates. From here you set the domain your storefront runs on, the currency buyers transact in, the languages the platform supports, which optional feature modules are active, and the support contact details and legal links shown to your users. This page covers each setting available to admins through the UI.
This page covers settings available through the Meneja interface. Server-side environment variables and deployment configuration are outside the scope of this guide.
## Accessing tenant settings
Navigate to **Tenants** in the sidebar, find your tenant, and open its detail page. From there, click **Edit** to open the tenant form. All of the settings described below are on this form.
Super admins can also access tenant settings by selecting a tenant from the tenant switcher and then navigating to **Marketplace Settings** in the secondary navigation at the bottom of the sidebar.
## General settings
These fields define the core identity of your tenant.
| Field | What it controls |
| --------------- | ------------------------------------------------------------------------------------------------- |
| **Tenant name** | The display name for your marketplace. |
| **Domain** | The domain your storefront runs on (e.g. `mystore.example.com`). |
| **Admin email** | The primary contact email for this tenant. |
| **Admin phone** | The primary contact phone number for this tenant. |
| **Active** | Whether the tenant is live. Deactivating a tenant hides it from the platform without deleting it. |
## Localisation
Localisation settings tell Meneja how to display prices and which languages to make available.
| Field | What it controls |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Country** | The two-letter country code for this tenant (e.g. `TZ` for Tanzania, `KE` for Kenya). This drives localisation defaults. Supported countries include Tanzania, Kenya, Uganda, Rwanda, Burundi, DRC, South Sudan, Ethiopia, Somalia, South Africa, Nigeria, Ghana, Egypt, and Morocco. |
| **Currency** | The currency used for all transactions on this tenant. Options include TZS, KES, UGX, NGN, USD, EUR, GBP, and others. |
| **Languages** | The languages available on your tenant. Select one or more from the supported list, which includes English (US), Swahili, French, Arabic, Spanish, Portuguese, German, Italian, Japanese, Korean, Simplified Chinese, Traditional Chinese, Russian, Hindi, Bengali, and Urdu. At least one language is required. |
If your primary market is East Africa, set **Country** to `TZ` or `KE` and add **Swahili** alongside English to reach the broadest audience.
## Modules
Modules control which optional features are active on your tenant. Toggle each module on or off depending on the services your marketplace offers. Changes take effect immediately and update the sidebar navigation for all users on that tenant.
The following modules are available:
| Module | Key | What it enables |
| ------------------------ | ------------------ | --------------------------------------------------------------------------------- |
| **Payments** | `payments` | Payment processing and transaction management. |
| **Delivery** | `delivery` | Delivery functionality, delivery partners, and delivery sub-section under Orders. |
| **Vendor loans** | `vendor_loans` | The Loans section, including loan providers, loan products, and loan requests. |
| **Affiliates (Mawinga)** | `affiliates` | The Affiliates section and Winga entity configuration in tenant configurations. |
| **Rewards & referrals** | `rewards_referals` | The Rewards & Referrals section. |
Disabling a module hides its sidebar section for all users on that tenant, including admins. Make sure your team is aware before toggling a module off.
## Support contact details
These fields appear on the tenant's metadata and are used to surface support contact information to buyers.
| Field | What it controls |
| ----------------- | ------------------------------------------------------------ |
| **Support email** | The email address buyers can use to reach your support team. |
| **Support phone** | The phone number buyers can call for support. |
## Legal links
Provide URLs to your legal documents. These links are shown to users where required, such as on the sign-in page.
| Field | What it controls |
| ---------------------- | ------------------------------------------------- |
| **Terms & conditions** | A URL pointing to your terms of service document. |
| **Privacy policy** | A URL pointing to your privacy policy document. |
Both fields accept full URLs. Leave them blank if you do not yet have published documents, but provide them before going live.
## Branding
The branding section lets you customise the visual identity of your tenant.
| Field | What it controls |
| ---------------------- | ------------------------------------------------------------------------------------ |
| **Logo (primary)** | URL for the primary logo shown in the storefront header. |
| **Logo (secondary)** | URL for an alternate logo, used in contexts like the sidebar or email. |
| **Logo (icon)** | URL for a square icon version of your logo, typically used as a favicon or app icon. |
| **Primary colour** | The main brand colour, as a hex code (e.g. `#e43335`). |
| **Secondary colour** | A supporting brand colour, as a hex code. |
| **Accent colour** | A highlight colour used for interactive elements, as a hex code. |
| **Text colours** | Primary and secondary text colours, each as a hex code. |
| **Background colours** | Primary and secondary background colours, each as a hex code. |
| **Border colour** | The colour used for borders and dividers, as a hex code. |
All colour fields require a valid six-digit hex code starting with `#` (e.g. `#1a2b3c`). Invalid codes will be flagged by the form before you can save.
## Banners
You can add promotional banners that appear on your storefront. Each banner has:
* **Title** — A short label for the banner (required).
* **Image URL** — A publicly accessible URL for the banner image (required).
* **Alt text** — Descriptive text for accessibility (optional).
* **Display order** — A number that controls the order banners appear in. Lower numbers display first.
Add multiple banners by clicking **Add banner**. Remove an existing banner by clicking the delete icon next to it.
## Saving your changes
After updating any settings, click **Save** at the bottom of the form. Meneja validates all fields before saving — required fields that are missing or fields with invalid formats (such as a malformed hex code or a non-URL value in a URL field) will be highlighted with an error message. Fix the flagged fields and click **Save** again.
Learn how multi-tenancy works in Meneja, including how tenant context affects what each user sees.
Add users to your tenant and assign them roles and permissions.