> For the complete documentation index, see [llms.txt](https://ajuda.pdvlegal.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajuda.pdvlegal.com.br/retaguarda/dashboard/pessoas.md).

# Pessoas

Use a visão **Pessoas** do Dashboard para analisar a operação por colaborador.

Essa leitura ajuda a acompanhar caixa, atendimento, comissão e entregas.

### Filtros disponíveis

Você pode filtrar por:

* período
* filial
* usuário
* tipo de venda

### Indicadores exibidos

Depois de aplicar os filtros, o painel mostra:

* **Vendas por operador (caixa)** — total encerrado por quem finalizou e recebeu a venda
* **Comissão por atendente** — comissões calculadas com base nos acréscimos
* **Venda por atendente** — valor lançado pelo atendente nas mesas
* **Venda por entregador** — total das entregas concluídas

{% hint style="info" %}
Na comissão por atendente, o cálculo considera quem lançou o item. Se a taxa de serviço não for paga, ela não entra no total.
{% endhint %}

<figure><img src="https://1320237751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLaIVEmahy7qwD0rmQzED%2Fuploads%2Fdkcv44gHOc6ws7MI3aAf%2Fdash_pessoas.gif?alt=media&amp;token=5e016f22-9601-44c1-bfae-f9e554d59be8" alt=""><figcaption></figcaption></figure>


---

# 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://ajuda.pdvlegal.com.br/retaguarda/dashboard/pessoas.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.
