# License Mapping

License type defines the features and functionality available when using Whaly. It's important to successfully deploy your data project to assign the right licenses to the right stakeholders.

Whaly offers 3 main licenses:

1. **Builder**: Users who connect data sources, create models and define explorations
2. **Editor**: Users who create dashboards and questions
3. **Viewer**: Users who consume already existing dashboards, questions and exploration. However, everything is read-only for those.

<img src="/files/mjgkavRrN2se8KK1ysv5" alt="" class="gitbook-drawing">

A typical Whaly deployment is using the following License mapping with the organisation:

## **Builders**

### Required skills

* Understand the Data Stack architecture and how to operate its different parts
* Strong spreadsheet experience or SQL knowledge

### Typical audience

* Everyone from the **Data team** (Data engineers, Data analysts, Analytics engineers, ...)
* **Data driven individuals that are operating the data setup** of their team (SalesOps / Growth engineers / ...)

## Editors

### Required skills

* Understand how to build an effective dashboards
* Understand how to answer a question with the Metrics / Dimensions model or has experience with a spreadsheet pivot table

### Typical audience

* Any data driven individual (Engineer, Product Manager, Ops, ...)
* Team leaders that want to build dashboards to run their team

## Viewers

### Required skills

* Understand how to read a dashboard and use filters

### Typical audience

* Everyone in the company that isn't an Editor or a Builder already


---

# 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://help.whaly.io/core-concepts/getting-started/license-mapping.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.