# Understanding Custom Role in DoubleTick and How Do You Create One?

The four default roles in DoubleTick cover most team setups really well. But sometimes, your business has a unique need that doesn't quite fit into any of them.

That's where custom roles come in.

***

#### <mark style="color:$primary;">**What is a Custom Role?**</mark>

A custom role is a role that you build yourself. Instead of picking from the default options, you hand-pick exactly which permissions to include — giving a team member access to only what they need, and nothing else.

For example, imagine you have a developer who needs to integrate DoubleTick with your CRM. They need access to API keys and webhooks — but they have no reason to read customer conversations or touch your billing details. A custom role lets you create something that fits that exact situation perfectly.

***

#### <mark style="color:$primary;">**Two Types of Custom Roles**</mark>

Just like default roles, custom roles come in two types:

**Custom Organization Role** — for account-level permissions. Use this when you want to control access to things like team management, billing, integrations, API keys, analytics, and audit logs.

**Custom Channel Role** — for WhatsApp-specific permissions. Use this when you want to control access to things like conversations, message templates, bots, and calls — within a specific WhatsApp number.

You'll choose which type you're creating as part of the setup process.

***

<figure><img src="/files/GddnPdSAEFioUaBVWSCz" alt=""><figcaption></figcaption></figure>

#### <mark style="color:$primary;">**How to Create a Custom Role**</mark>

The steps are the same whether you're creating a custom Organization Role or a custom Channel Role — the only difference is which section you start from.

1. Log in to your DoubleTick account.
2. Click on **Settings** in the left-hand panel.
3. In the Settings search bar, type **Roles** and open the **Roles** section.
4. Under **Manage Roles**, you'll see two sections — **Organization Level Roles** and **Channel Level Roles**.
5. Click into whichever section matches the type of custom role you want to create.
6. Click **Create New Role**.
7. Give your role a clear, recognisable name — something that tells you exactly what it's for (for example, *Developer Access* or *Support Agent - Read Only*).
8. Optionally, add a description to remind yourself and your team what this role includes.
9. Select the permissions you want to include from the list.
10. Click **Save**.

Your custom role is now ready to use. You'll be able to assign it to team members when you invite someone new or when you update an existing team member's profile.

***

#### <mark style="color:$primary;">**A Few Things Worth Knowing**</mark>

**You can create as many custom roles as you need.** There's no limit — so if different teams or individuals need different levels of access, you can build a role for each situation.

**Custom roles don't affect default roles.** Creating a custom role doesn't change or remove any of the four default roles. They'll always be there.

**You can go back and edit a custom role anytime.** If your team's needs change, you can update the permissions in a custom role without having to create a new one from scratch.

***

In the next two articles, we'll go through all the permissions available when creating a custom Organization Role and a custom Channel Role — so you know exactly what you're working with when you build your own.


---

# Agent Instructions: 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:

```
GET https://learn.doubletick.io/settings/manage-roles/understanding-custom-role-in-doubletick-and-how-do-you-create-one.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
