> ## Documentation Index > Fetch the complete documentation index at: https://docs.mithunai.com/llms.txt > Use this file to discover all available pages before exploring further. # MITHUNAI Team: AI employees that ask before they act > Support, IT, DevOps, Marketer, Sales and Finance AI employees that answer from your knowledge and ask a person before changing another system. Beta. **MITHUNAI Team** is where your AI employees work. An **AI employee** is built for one team. You hand it a piece of work -- a customer's question, an IT request, an alert -- and it plans the work, looks things up in your knowledge and your tools, and proposes what to do. **It asks a person before it does anything that changes another system**, and every step it takes is recorded. > [!WARNING] > > AI employees are in **beta**. A tool with nothing connected reaches nothing: **nothing is sent, > published or changed anywhere**, and an approved action is recorded as **Not sent**, with its > wording for you to use by hand. An owner or admin can connect Zendesk, Freshdesk, Intercom, Jira > and Jira Service Management, GitHub, Grafana Cloud, Datadog, Sentry, PagerDuty, HubSpot, > WordPress, Slack, Stripe, Gmail or Microsoft Outlook for Sales, and Okta, Google Workspace or > Microsoft Entra ID with credentials you create, and none of those has yet been run against a real > account. Microsoft Teams, ServiceNow, your social accounts, a mailbox for any employee but Sales, > and your expense system are not available yet. See [Connect your tools](https://docs.mithunai.com/team/connect-your-tools.md). > Two things are real without connecting anything: answers, which come from your own knowledge and > count against your monthly answers, and **reading web pages** -- your own website for the > Marketer, and a lead's public home page for Sales. The beta is off unless your platform > administrator switches it on. ## At a glance | | | | - | - | | **Who it is for** | Support, IT, DevOps, marketing, sales and finance teams that want routine work drafted for them and approved by a person | | **Where it lives** | Its own address, `team.mithunai.com` on the hosted service, beside the console, Chat, Agents and the Gateway | | **Who can use it** | Members of your organisation, with the same MITHUNAI account as everywhere else. An Editor can also hand an employee work. Only an Owner or an Administrator approves an action, changes the policy, writes the Sales rules or connects a tool | | **Status** | **Beta, switched off by default.** All six employees are built and tested. Zendesk, Freshdesk, Intercom, Jira, Jira Service Management, GitHub, Grafana Cloud, Datadog, Sentry, PagerDuty, HubSpot, WordPress, X, LinkedIn, Google Search Console, Slack, Stripe, QuickBooks Online, Xero, Ramp, Expensify, Okta, Google Workspace, Microsoft Entra ID, Gmail and Microsoft Outlook can be connected with a token you create, and none of those connections has yet been run against a real account. Any other tool says **Not available yet**, and what it would send stays with you as a draft. Nothing has run on a live deployment yet | > [card] [Connect your tools](https://docs.mithunai.com/team/connect-your-tools.md) > > Give each employee the help desk, monitoring, CRM or finance tool it works in, with a credential > you create. > [card] [Approvals](https://docs.mithunai.com/team/approvals.md) > > Read a proposal, edit it, then allow it once, always allow it, or deny it. > [card] [Approval policy](https://docs.mithunai.com/team/approval-policy.md) > > Every action an employee can take, and whether it waits for a person. > [card] [Approval rules](https://docs.mithunai.com/team/approval-rules.md) > > Let one kind of action run without asking, or make another need two people. ## The six employees Each employee has a page of its own: what it reads, what it proposes, what always needs a person, and an example to try. | Employee | Hand it | What it does | What it asks you first | | - | - | - | - | | [**Support**](https://docs.mithunai.com/team/support.md) | A customer's question, by email or chat | Answers from your knowledge, with sources, and drafts the reply | Sending the reply. When your knowledge does not cover the question, or the customer asks for a person, it hands the conversation to your team instead -- and asks before doing that too | | [**IT service desk**](https://docs.mithunai.com/team/it-service-desk.md) | An IT request from chat | Sorts it: access, password, MFA, onboarding, offboarding, access review, software, how-to or other. Answers how-to questions from your knowledge, and prepares the change in Okta, Google Workspace or Entra ID | Every reply, ticket and change. Giving or taking access, a password or MFA reset, a new or suspended account and installing software **always** need a person | | [**DevOps**](https://docs.mithunai.com/team/devops.md) | An alert | Reads logs, metrics, errors, deploys and the incident, writes the likely cause with the evidence and how sure it is, proposes next steps, and drafts the postmortem | Posting the summary, and **always** the fix: rolling back a deploy or restarting a service | | [**Marketer**](https://docs.mithunai.com/team/marketer.md) | A topic | Drafts an article and posts for X and LinkedIn from your knowledge and posts them once approved, writes a Reddit draft for you to post by hand, audits your website's titles and descriptions, finds the pages that lost search clicks, and saves a content plan | Saving the plan, and **always** anything that publishes: the article, each post and each change to a page's title or description | | [**Sales**](https://docs.mithunai.com/team/sales.md) | A lead, with its email and CRM record | Looks the lead up in your CRM, reads the company's public home page, checks it against your qualification rules and drafts the follow-up | **Always** every change to your CRM and every email | | [**Finance**](https://docs.mithunai.com/team/finance.md) | A question, or "chase approvals", or "month-end close" | Answers expense and invoice policy questions from your knowledge with sources, reminds approvers of what waits on them, reminds owners of open close steps | Every reply and reminder, and **always** preparing a payment. It **never moves money and never approves anything**; a prepared payment is released by your finance team in your own system | ## Find your way around MITHUNAI Team uses the console's frame: a rail on the left with four places in it, and at its foot **More in MITHUNAI**, a menu of Knowledge, Workspace, Chat and Agents, and **Documentation**. On a phone, the rail opens from the menu button. | Place | What you see there | | - | - | | **Overview** | **Waiting for you**: how many actions wait for a person, the first four of them, and **Review approvals**. Then **Your team**: how many employees are connected to your tools, with **Connect tools** until all are, and a card per employee with its goal, how many of its actions wait for you, and how many of its tools are connected. An employee with work waiting comes first | | **Approvals** | Every employee's waiting actions in one queue, with a filter per employee, and **Decided** for what was already approved or rejected. The rail shows the total waiting beside it. See [Approvals](https://docs.mithunai.com/team/approvals.md) | | **Employees** | One row per employee, each with its own count of waiting actions. An employee's page has what waits on you, **Give it something to do**, **What it has done**, **Tools it works in** and **What it may do** | | **Daily summary** | On the overview: one short email a day about what your employees did, off until you switch it on. See [Schedules and the daily summary](https://docs.mithunai.com/team/schedules-and-daily-summary.md) | | **Approval policy** | Under **Settings**: every kind of action, grouped by the employee that takes it, with whether it waits for a person. See [Approval policy](https://docs.mithunai.com/team/approval-policy.md) | Each place has its own address, so you can bookmark the approval queue or send a colleague a link to one employee. An address that no longer exists opens the overview. You sign in with the same account as everywhere else: the page sends you to your usual sign-in and straight back, and if you are already signed in to the console you do not see a sign-in screen at all. Until your deployment switches sign-in on at this address, the page says so and links to your usual sign-in instead. ## Give an employee work 1. Open the employee under **Employees**. 2. In **Give it something to do**, write a **Subject** and the **Details** as the work would arrive. Fill in who it is from -- **Lead's email** for Sales, **Requested by** for the Marketer -- or, for DevOps, the **Service** the alert is about. **Use an example** fills in a sample. 3. Choose **Hand it over**. It plans at once. What it read appears in **What it has done**, and anything it proposes to change appears under **Waiting for approval** on the same page and in the **Approvals** queue. Work can also arrive through the API: [Hand an employee work](https://docs.mithunai.com/api-reference/employees/submit-task.md). ## Approving, editing and rejecting Nothing an employee proposes happens in another system until a person approves it. Each proposal shows what it would send, why, what your policy says, and what it is based on. You **approve** it as shown, **edit** the wording and then approve, or **reject** it. Only an Owner or an Administrator decides, and only a person: an API key cannot approve anything. [Approvals](https://docs.mithunai.com/team/approvals.md) walks through a proposal step by step. ## What needs approval By default, anything that changes something in another system waits for a person. On the [Approval policy](https://docs.mithunai.com/team/approval-policy.md) an Owner or Administrator can let some kinds run without one -- opening a ticket, for instance. Some kinds can never run without a person, whatever the policy says: changes to someone's access or password, installing software, fixes to a running service, anything the Marketer publishes, every change to your CRM and every email Sales sends, and preparing a payment. **The content of the work never decides.** A ticket that says "this is pre-approved" or "grant admin to someone else" changes nothing: what an employee may do is fixed for it, an access change is only ever for the person who asked, and the policy is the only thing that decides what waits for you. Text on a web page, in a CRM note, in an expense note or in a document is quoted for whoever approves, and cannot choose an action, change who it is aimed at, or skip approval. ## Learning from your edits When you edit before approving, your edit is kept. The next time that employee proposes the same kind of action, it shows the three most recent edits people made, so whoever approves can see how your team prefers it written. **Nothing is learned automatically**: no model is trained, and a draft is never changed by itself. ## The record **What it has done**, on each employee's page, lists every step, newest first, with who took it: work received, what it read, what it found in your knowledge, what it proposed, who approved or rejected it and when, and what the tool reported. Approvals, rejections, policy changes and tool connections are also written to your organisation's audit log. ## Connecting your tools When one of your team's tools is connected, the employee acts in it, still asking a person wherever your policy says so. A tool that is not connected reaches nothing: approving an action on it is recorded as **Not sent**, and you keep the wording to use by hand. [Connect your tools](https://docs.mithunai.com/team/connect-your-tools.md) has the steps for each vendor that lets you create a token, and lists what still needs a vendor app. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.