> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/account.md).

# Settings and members

Find every dCal setting in one place. See what each Settings tab holds (General, Booking Page, Notifications, Members and Integrations), who can open it, where API keys, webhooks and AI agents live no

**Settings** holds your own profile and, if you are an admin or owner, the settings of the whole workspace: who is in it, which emails go out and what dCal connects to. Open it from **Settings** in the left menu, or go to [app.dcal.ai/admin/settings](https://app.dcal.ai/admin/settings). It opens on the **General** tab.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-da90ec4ed3b56717c94dd59dde4af04d1a91fc37%2Fdcal-account-01-settings-tabs.png?alt=media" alt="The Settings title of dCal with its five tabs boxed: General (selected), Booking Page, Notifications, Members and Integrations"><figcaption><p>Admins and owners see five tabs. Members see the first two.</p></figcaption></figure>

***

## The Settings tabs

| Tab               | What it holds                                                                                                                                 | Who sees it                                              |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| **General**       | Your **Display name**, **Public handle** and **Timezone**, the workspace's **Dapta branding** switch, and the **Language** of your dashboard. | Everyone                                                 |
| **Booking Page**  | The studio for your public page (profile, brand, appearance and the events it lists) and the workspace **Brand kit**.                         | Everyone. Only admins and owners can save the brand kit. |
| **Notifications** | Which booking emails go out to guests and to hosts, and the wording of each one. One set for the whole workspace.                             | Admins and owners                                        |
| **Members**       | Everyone in the workspace, their role and status, invitations and ownership.                                                                  | Admins and owners                                        |
| **Integrations**  | The HubSpot connection for the whole workspace.                                                                                               | Admins and owners                                        |

A member who opens an admin tab from a saved link sees **You don’t have access** and the note that the section is for workspace admins and owners. Ask an admin or an owner to make the change, or to give you the **Admin** role in [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md).

API keys, webhooks and the setup for connecting an AI agent are not in **Settings**. They live in the left menu, for admins and owners only: **Connect your agent**, **Tools**, and **API and webhooks**, which holds **API keys**, **Webhooks** and **API docs**. A saved link to the old **MCP & API** tab (`app.dcal.ai/admin/settings/developer`) now opens **Connect your agent**. See [Connect an AI assistant (MCP)](https://docs.dapta.ai/dcal/developers/mcp-server.md).

> **💡 Tip:** **Calendars** is not a Settings tab. You connect your Google or Outlook calendar from **Calendars** in the left menu. See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

***

## In this section

{% content-ref url="/pages/wlc4G831uFWG8GIyNChK" %}
[Your name and time zone](https://docs.dapta.ai/dcal/account/general-settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/sbdAecFArpTbeDcE49IL" %}
[Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md)
{% endcontent-ref %}

{% content-ref url="/pages/VFaqbnaSyn1ajrC3P6kZ" %}
[Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md)
{% endcontent-ref %}

{% content-ref url="/pages/IkYZh3mzZ7Wh8FiZbX2R" %}
[Workspaces](https://docs.dapta.ai/dcal/account/workspaces.md)
{% endcontent-ref %}

{% content-ref url="/pages/0f7YIYqLdA4FU9BASPxK" %}
[Language and appearance](https://docs.dapta.ai/dcal/account/language-and-appearance.md)
{% endcontent-ref %}

## Related

* [Profile and layout](https://docs.dapta.ai/dcal/design/booking-page-studio.md): what the **Booking Page** tab does.
* [Customize your emails](https://docs.dapta.ai/dcal/emails/customize-emails.md): the **Notifications** tab.
* [Integrations](https://docs.dapta.ai/dcal/integrations.md): HubSpot, webhooks and your Dapta agents.
* [API keys](https://docs.dapta.ai/dcal/developers/api-keys.md): the **API keys** page, under **API and webhooks**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
