> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.basement.chat/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.basement.chat/_mcp/server. # MultiDados [MultiDados](https://multidadosti.com.br) (MultidadosTI) is a service desk: the requests are **tickets** (ocorrências), the people who serve them are **operators**, and the tickets are in **groups** (divisions). The Gateway speaks with the MultiDados of your company through its API 3.0. MultiDados does not know which person uses the assistant, because the Gateway signs in with the credentials of the company. So Basement does the control: each member is linked to a MultiDados operator, and the agents of that member see and act on only the tickets of that operator. An admin can share more. ## What the assistant does | With read only | With read and write | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Searches tickets by text, status, group, request type or period. Reads a ticket with the history and the attachments. Lists the groups, the request types and the statuses. Searches clients and operators. Shows which tickets you can see. | All of the read part. Opens tickets. Replies (adds a follow-up). Changes the status, forwards to another operator and adds a note. Schedules a reply or a status change for a date. Lists and cancels what is scheduled. | A scheduled action becomes a task on the **Tasks** board of the member. See [Tasks](/daily/tasks). ## Step 1: the admin configures MultiDados (one time) In **Connections**, on the **MultiDados** card, click **Configure**. 1. **MultiDados address**: for example `https://yourcompany.multidadosti.com.br`. 2. **API token**: ask MultiDados, or the admin of your MultiDados, for an **API 3.0 token** (the `Authorization-Token` used at `/api`), with the API enabled for the account. 3. **API user** (optional): the token already has a MultiDados login, and Basement writes with that login. Fill in the web-service user and password (`usuario_ws` / `senha_ws`) only if the writes must go out with a different login. Click **Save**. The Gateway tests the token and tells the result: * **Configured**: reads and writes with the login of the token. * **Configured as read-only**: MultiDados did not accept the login of the token for writes. Add an API user to enable writes. ## Step 2: each person connects their operator In **Connections**, on the **MultiDados** card, click **Connect my account**. Basement looks for an active operator with your e-mail. * It found one: the card shows **Connected to MultiDados as (your name)**. * It found none, or more than one: click **Ask an admin to link me**. The admin links your account to the correct operator in **MultiDados access**, and Basement tells you by e-mail. The MultiDados account is always personal. It cannot be shared with the organization. ## What each person sees By default, the agents of a member reach only the tickets of **that member**: the ones they serve, the ones they are responsible for, the ones forwarded to them and the ones they opened. An admin extends this for each member, in **Connections**, on the **MultiDados** card, in **MultiDados access**: | Option | What it gives | | -------------------------------- | ---------------------------------------------------------------------------------------------- | | **Also access tickets of** | The tickets of the selected operators. The agents of the member read and act on these tickets. | | **And tickets in groups** | All the tickets of the selected groups (divisions). | | **Read every ticket** | Reads everything. Acts only on the own tickets and the shared ones. | | **Read and act on every ticket** | Reads and acts on everything. | ## Example questions * "Which of my tickets have been open for more than 3 days?" * "Summarize ticket 10452 with the last contact of the client." * "Reply to ticket 10452: 'Update applied, please validate.'" (needs read and write) * "Schedule for tomorrow at 9:00 a reply on 10452 that asks the client for feedback." (needs read and write) ## If it does not work | Message | What to do | | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | "An admin must configure MultiDados first" | Ask an admin for step 1. | | "No active MultiDados operator uses (your e-mail)" | Click **Ask an admin to link me**. The admin links your account in **MultiDados access**. | | "Several MultiDados operators use (your e-mail)" | The admin selects the correct operator in **MultiDados access**. | | The assistant does not see a ticket | The ticket is not yours. Ask an admin to share the operator or the group. | | A write answers "not permitted" | Your access level has read only in MultiDados, or MultiDados is configured as read-only. Speak with the admin. |