> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/getting-started/portal-menu-map.md). # Portal Menu Map Complete reference for the `portal.diro.app` sidebar. The menus that appear follow your role's access rights — if a menu isn't visible, that role hasn't been given access to that module. See Staff, Roles & Access Rights. ```mermaid flowchart LR R["Portal"] --> D["Dashboard"] R --> P["Booking"] R --> M["Master Data"] R --> C["Customer"] R --> S["Sites"] R --> A["Analytics"] R --> G["Settings"] R --> H["Help"] ``` ## Dashboard The first screen after login. A summary of bookings, revenue, peak hours, and service/provider rankings for the date range you choose. Details: Dashboard & Analytics. ## Booking Everything related to bookings in progress. | Menu | What it holds | When to open it | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | **Booking** | The full list of bookings, with status and date filters. From here you create, edit, reschedule, cancel, and charge payment. | Every day. This is the operations team's main work screen. | | **Schedule Report** | A daily schedule view per branch — who's coming at what time, handled by whom. | In the morning before opening, to see the day's plan. | | **Attendances** | Records of customer attendance at bookings. | When a customer arrives, to mark them present. | Guides: Customer Booking Flow · Creating a Booking from the Portal ## Master Data Your business configuration. This menu's content rarely changes after initial setup, but it determines everything else. | Menu | What it holds | When to open it | | ------------------------------ | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | | **Categories** | Service groupings in the storefront catalog. | When adding a new type of service. | | **Services** | Everything you sell and that can be booked, complete with price, duration, schedule, resources, and attributes. | When adding a service, changing a price, or fixing a schedule. | | **Events** | Events with their own date and quota, with a separate share page. | When running a special class, workshop, or one-off event. | | **Resources → Resources** | Resource groups — for example "Therapists", "Studio Rooms". | When setting up your capacity structure. | | **Resources → Resource Items** | The actual items within a group: each therapist, each room, with its own availability schedule. | When adding a person or room, or changing their working schedule. | | **Additional Items** | Paid add-ons offered at checkout. | When adding a product or add-on service. | | **Vouchers** | Discount vouchers and memberships. | When creating a promo or package. | | **Commission** | Commission rules per provider and per service. | When agreeing on a new commission scheme. | | **Reviews** | Reviews from customers, and settings for which ones show on the storefront. | Periodically, to respond and choose which to display. | | **Staff & Roles** | The list of staff who can log in, along with their roles and access rights. | When hiring, changing responsibilities, or revoking access. | Guides: Services, Packages & Add-ons · Setting Up Service Schedules · Resources · Service Attributes · Vouchers & Membership · Commission · Staff, Roles & Access Rights ## Customer | Menu | What it holds | When to open it | | ------------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------------- | | **Customer List** | All customers with their booking history, total spend, and contact details. | When looking up customer data, or preparing a campaign. | | **Customer Memberships** | Who holds which membership, remaining quota, and validity period. | When a customer asks about remaining quota, or when renewing. | Guides: Branches & Customers ## Sites Everything the public sees. | Menu | What it holds | When to open it | | --------------- | ------------------------------------------------------------------------- | ---------------------------------------------------- | | **Website** | The storefront front page: sections, content, order, and which ones show. | When updating the look or content of the front page. | | **Link in Bio** | A compact link page to put in your Instagram or TikTok bio. | When changing your promotional links. | | **Blogs** | Articles to attract visitors from search. | When publishing a new post. | Guides: Your Storefront ## Analytics | Menu | What it holds | When to open it | | -------------------------- | ---------------------------------------------------------------------- | ---------------------------------------------- | | **Booking Analytics** | Booking and revenue trends, peak hours, service and provider rankings. | Weekly or monthly, when evaluating. | | **Commission Report** | Commission earnings per provider for a given period, ready to export. | Every pay period. | | **Payment Reconciliation** | Matching paid bookings against incoming transactions. | Periodically, and whenever a number looks off. | Guides: Dashboard & Analytics · Payment Reconciliation ## Settings | Menu | What it holds | When to open it | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | | **Setting** | One page with several tabs: **Business** (profile, subdomain), **Payment** (methods, fees, cancel/reschedule rules), **Appearance** (logo, color, template), **Form** (custom checkout fields). | During initial setup, and occasionally when a policy changes. | | **Assets** | Your photo and file library, organized into folders. | When uploading service photos or promotional material. | | **Balance** | Active and held balance, transaction history, bank accounts, and withdrawal requests. | When checking incoming funds or withdrawing money. | | **Integrations** | Connections to other services, such as Google Calendar. | Once, when connecting, then rarely. | | **Branches** | All locations, their addresses, contacts, and operating hours. | When opening a new branch or changing an address. | | **Import History** | A record of bulk data uploads and their results. | After an import, to check which rows failed. | Guides: Payment Methods & Invoices · Wallet & Withdrawals · Custom Booking Form {% hint style="warning" %} **Branches lives under the Settings menu, not Master Data.** This is often looked for in the wrong place. {% endhint %} {% hint style="info" %} The **Balance** menu is the only way to withdraw funds. A role without access to this module can't request a withdrawal. {% endhint %} ## Help | Menu | What it holds | | ------------------ | ----------------------------------------------------- | | **Tutorial** | Video guides for using the portal. | | **Template Files** | Sample files for importing customer and service data. | ## If a menu doesn't appear Three possibilities, in order of how often they happen: 1. **Your role hasn't been given access** to that module. Check under **Master Data → Staff & Roles**. 2. **You were just given access** but haven't reloaded the portal. Refresh the page. 3. **The business subscription is inactive**, so some menus are restricted. See Subscription & Plans. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.diro.app/en/getting-started/portal-menu-map.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.