> 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/initial-setup.md).

# Initial Setup

Follow this order. Each step depends on the one before it — for example, a service can't be scheduled before a branch has opening hours.

```mermaid
flowchart LR
  A["1. Business<br/>Profile"] --> B["2. Branch &<br/>Opening Hours"]
  B --> C["3. Services &<br/>Pricing"]
  C --> D["4. Staff &<br/>Resources"]
  D --> E["5. Schedule"]
  E --> F["6. Payment &<br/>Bank Account"]
  F --> G["7. Storefront<br/>Appearance"]
  G --> H["8. Trial<br/>Booking"]
```

## 1. Complete your business profile

**Settings → Setting → Business tab.** Business name, logo, description, contact, and subdomain. The subdomain determines your storefront address (`business-name.diro.app`), so choose something short and easy to remember.

## 2. Create branches and opening hours

**Settings → Branches.** At least one branch is required. Fill in the address, map location, contact, and operating hours per day.

A branch's operating hours are shown to customers as information, but they **do not restrict booking slots**. Slot availability is determined entirely by the service schedule (step 5) and resource availability (step 4).

## 3. Create services and pricing

**Master Data → Services.** For each service, fill in the name, category, photo, duration, price, and the branches where it's available.

If your business sells packages or recurring classes, read Services, Packages & Add-ons before creating them — package structure differs from a regular service.

## 4. Add staff and resources

**Master Data → Staff & Roles** for people who need to log in to the portal. Set their role, since the role determines which menus they see.

**Master Data → Resources → Resource Items** for providers (people who carry out bookings) and rooms/equipment. This is what determines capacity — if you have 3 chairs, create 3 resources, not one.

## 5. Set up your schedule

This is the part most often done wrong. Read Setting Up Service Schedules — it includes examples for daily schedules, weekly classes, and monthly sessions.

## 6. Activate payments and your bank account

**Settings → Setting → Payment tab.** Choose which payment methods to accept, set cancellation and reschedule rules, and decide who bears the transaction fees.

**Settings → Balance.** Register a bank account for withdrawals. Without a registered account, your balance can't be withdrawn.

## 7. Set up your storefront appearance

**Settings → Setting → Appearance tab** for colours, logo, and template. **Sites → Website** for the homepage, sections, and blog. See Your Storefront.

## 8. Try booking yourself

Open your storefront in a different browser (or incognito mode) and go through one booking from start to payment. This catches 90% of configuration issues before your first customer finds them.

{% hint style="info" %}
If a slot doesn't show up during your trial, don't change many things at once. See Frequently Asked Questions — there's a specific order of checks to follow.
{% endhint %}


---

# 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/initial-setup.md?ask=<question>&goal=<endgoal>
```

`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.