The AI assistant and agent mode

Interactive tutorial

Follow the course step by step in the interactive player.

Lessons

1. 1Give the assistant something to read: three tax transactionsThis lesson is for the tax manager. The AI assistant and the agent answer from the records your company holds, so an empty company gets empty answers. You will add one sale and two purchases to Tax Intelligence by hand. Later lessons ask the assistant and the agent about exactly these three transactions, so that every answer can be checked against a record you know.6 min
2. 2Give the assistant something to read: a risk and a deadlineThis lesson is for the compliance officer. You will record one risk in the Risk Register and one deadline on the Compliance Calendar. Both are small, real records that later lessons ask the assistant about, so that you can see what it finds, what it does not find, and how to check its answer on the screen that holds the record.6 min
3. 3Give the assistant something to read: a processing activityThis lesson is for the Data Protection Officer. You will add one entry to the record of processing activities, or RoPA, which is the register of how the company uses personal data. Later lessons ask the assistant and the agent about data protection, and this entry is the record their answers should reflect.4 min
4. 4Open the assistant and ask a first questionThis lesson is for anyone whose role lets them use the Compliance Assistant; here it is the compliance officer. The assistant is a chat window that answers questions about compliance in the United Arab Emirates and about this company's own records. You will open it from the top of the page, see how it knows which module you are in, send a suggested question, wait for the answer, and move the conversation to the full page.5 min
5. 5Ask about the law and read the answer properlyThis lesson is for anyone who uses the Compliance Assistant. You will ask a question about a rule, in your own words, and then read everything that comes back with the answer: the Confidence figure, the Sources, and the follow-up questions. You will learn what each of them tells you, what it does not tell you, and how to check an answer against the law it names, including references the assistant itself marks as not verified against the knowledge base.6 min
6. 6Ask about your own company's recordsThis lesson is for anyone who uses the Compliance Assistant. The assistant can look in this company's records to answer a question. You will ask about the tax transactions, the deadlines and the data protection register that lessons 1 to 3 created, see what kind of answer each gives, and learn where the assistant stops: it reads and reports, and it changes nothing.7 min
7. 7Check before you rely on itThis lesson is for everyone who uses the Compliance Assistant, and it is the most important one in the course. An answer from a language model can be right, partly right or wrong, and it reads the same in all three cases. You will check a figure against the screen that holds the record, check an answer about the Risk Register against the register, and learn which part of an answer a Sources line or a not-verified mark speaks to.7 min
8. 8Follow up, clear a conversation, and find it in the audit logThis lesson is for anyone who uses the Compliance Assistant, and for the people who review how it is used. You will ask a follow-up question that only makes sense inside the conversation, leave the page and come back, clear the conversation, and then open the Audit log to see that every question was recorded with the name of the person who asked it.6 min
9. 9What a colleague without the assistant permission seesThis lesson is for colleagues whose role does not include the Compliance Assistant, and for the administrator who is asked why they cannot find it. Using the assistant needs a permission of its own, AI assistant, Use. The built-in roles that can open at least one module the assistant reads include it. An employee who may only see their own employee record does not, because there would be nothing the assistant could tell them. You will see what the employee's screen offers, and what happens if she opens the assistant's address directly.3 min
10. 10What the assistant can and cannot see for youThis lesson is for everyone who uses the Compliance Assistant. The assistant reads each module with the rights of the person asking. The Data Protection Officer's role includes the assistant and Data Protection, but not Tax. You will ask, as her, about her own module, about tax, and about the compliance scores, and read how the assistant answers when a module is closed to her.5 min
11. 11The administrator: who may use the assistantThis lesson is for the administrator who manages access. Lesson 9 showed an employee without the assistant, and lesson 10 a Data Protection Officer who has it but cannot see tax through it. Both follow from two kinds of permission: AI assistant, Use, which opens the assistant, and each module's own View permission, which decides what it may read for that person. You will find who holds AI assistant, Use on the company, and see the permission inside a built-in role.5 min
12. 12Agent mode: switch on the Tax Partner AgentThis lesson is for the tax manager. Agent mode is the second way of working with AI in ComplianceOS. The Compliance Assistant of the earlier lessons only answers questions. An agent does work: it classifies transactions, researches suppliers, prepares a draft VAT return, and stops to ask a person when it is unsure. Each entity has its own agent, and it does nothing until someone with the right role switches it on. You will read what the agent offers and switch it on.3 min
13. 13Read the agent's page before you ask it for anythingThis lesson is for the tax manager and for anyone who will work with the agent. The Agent Dashboard is one page with everything about the agent for this entity: its state, how much of its monthly AI budget it has used, the questions it has for you, the actions you can ask for, two specialist agents, a chat, and its recent activity. You will read each part without starting anything, so that the following lessons make sense.5 min
14. 14Decide what the agent may do on its ownThis lesson is for the tax manager, who is accountable for what the agent does to the tax records. Autonomy is the setting that decides, action by action, whether the agent acts on its own, asks a person first, or never does the action. A new agent is set to act on its own for everything. You will read the agent's settings and change three actions before the agent does any work.6 min
15. 15Ask the agent about your tax recordsThis lesson is for the tax manager. The chat on the Agent Dashboard is how you talk to the Tax Partner Agent. Unlike the Compliance Assistant, the agent is offered tools that match your own permissions on this entity: a person who may only view tax records gets an agent that can only look, and a person who may edit gets one that can also change. You will ask two questions that only read, mark a reply as helpful, and see that each exchange is counted as a run.6 min
16. 16Ask first: the agent asks for approval, and a person gives itThis lesson is for the tax manager. In lesson 14 you set Classify transactions to Ask first. Now you will tell the agent to classify the transactions, see it stop and raise an approval request instead, find that request in My Actions and in the agent's Inbox, approve it, and then repeat the instruction so that the agent does the work. Finally you will read the AI's suggestions in Tax Intelligence and approve them yourself in the Sign-off cockpit: the agent never approves a classification that only the AI has proposed.8 min
17. 17Run a full cycle and see what the agent asksThis lesson is for the tax manager. A full cycle is one complete round of the agent's work on this entity's tax records: it processes new documents, copies known supplier details across transactions, researches unknown suppliers, applies answers people have given, and raises questions about anything it needs a person for. You will start one, watch the steps appear, see which steps your autonomy settings skipped, and find the questions it raised.6 min
18. 18Answer one of the agent's questions and skip anotherThis lesson is for the tax manager. The full cycle of lesson 17 left two questions in the agent's Inbox, one for each supplier without a tax registration number. You will open the details of a question, answer one with the number from the supplier's invoice, skip the other, look at both in the All view, and then ask the agent which suppliers are still missing a number, to check that your answer was used.7 min
19. 19Read the agent log: what the agent really didThis lesson is for the tax manager, the compliance officer and the auditor. The agent log, on the page Agent History, records every run of the agent: each chat message and each cycle, who asked for it, the tools it used, what went in and what came out. It is where you settle what the agent actually did. You will read the runs of lessons 15 to 18, open two of them step by step, filter the list, and download the whole trail.6 min
20. 20Teach the agent a fact and manage what it remembersThis lesson is for the tax manager. The agent keeps a memory for each entity: facts about suppliers and preferences that it is given in the chat, and the feedback left with the thumbs. Memories it trusts are added to its instructions on every later message, so a wrong memory produces wrong work again and again. You will tell the agent a fact, find it under Agent Knowledge, search the list, and remove an entry.6 min
21. 21What the tax manager cannot change: the agent's AI budgetThis lesson is for the tax manager, and for the administrator who is asked to raise a budget. The tax manager decides how the agent behaves, but the amount of AI the agent may consume each month is money, and that decision belongs to an organisation administrator. You will try to change the Monthly AI Budget as the tax manager and read what the product answers.3 min
22. 22The administrator: AI credits, the agent's budget and its main switchThis lesson is for the organisation administrator. Every answer from the Compliance Assistant and every piece of agent work uses AI credits from the organisation's monthly allocation. You will set the monthly budget of one entity's agent, use the agent's main switch to turn it off and on again, and then read how many credits the organisation has used and which module used them.6 min
23. 23The agent works with your permissions: the auditor's viewThis lesson is for auditors and other colleagues with read-only access, and for the tax manager who wonders what they can do with the agent. The agent does not have rights of its own in the chat. For each message it is given only the tools that the person signed in may use on this entity. The auditor may view tax records and nothing more. You will ask the agent to read, then ask it to change a classification, and check the record afterwards.6 min
24. 24Ask the agent to record a data subject request, and trace itThis lesson is for the compliance officer, whose role covers both tax and data protection. The agent's chat also has tools for data protection, for people who hold those rights. You will ask it for a summary, then instruct it to log a data subject request, or DSR, which is a person asking what the company holds about them. Then you will trace the action: the new record in Data Protection, the run in the agent log, and the entry in the organisation's Audit log.7 min
25. 25Start a workflow and read its traceThis lesson is for the compliance officer. A workflow is a fixed, multi-step piece of AI work that you start by hand: the product runs several tools one after another in the background and keeps a trace of each step. The Workflows page is the last entry under Agent Mode. You will start one workflow without inputs, wait for it to end, open its trace, and learn from the result why a workflow needs to be told what to work on.6 min
26. 26Run the workflow with inputs and check what it createdThis lesson is for the compliance officer. In lesson 25 the workflow ended without doing anything, because it had no regulatory update to analyse. Now you will give it one, written in the Inputs box. The update is an example invented for training. A workflow, unlike the Compliance Assistant, may write records within your permissions, so you will read the trace step by step and compare what the summary says it did with the steps that ran.7 min
27. 27AI inside a module: have a contract draftedThis lesson is for legal counsel, and for anyone who wants to see how AI drafting is built into a module. Besides the assistant and the agent, several modules have their own AI buttons. Contracts has the clearest one: an agent writes a full draft from a short brief. The draft is only a draft. It cannot become a contract until a second person has approved it, which the next lesson shows. You will fill in the brief and start the drafting.6 min
28. 28Review the AI draft and have a clause revisedThis lesson is for legal counsel, the author of the draft. The agent has finished the draft of lesson 27. Before anyone is asked to approve it, the author reads it. You will open the draft, read the clauses and the agent's own checks, and tell the agent in plain words to change one clause. The agent rewrites that clause and keeps the result as a new version, so nothing is lost.6 min
29. 29Replace the placeholders the agent left in the draftThis lesson is for legal counsel. The agent did not know the two companies' addresses, so it left them as placeholders in square brackets, and the product will not let anyone approve the draft until they are filled in. You will give the agent the addresses through the same Revise this clause box and check that the placeholder warning has gone.4 min
30. 30A second person reads and approves the AI draftThis lesson is for the person who approves: here the compliance officer. The contract draft of lessons 27 to 28b was written by an AI agent at the request of legal counsel, who has reviewed it, had one clause revised and the placeholders filled in. It cannot become a contract on the author's word alone. You will find the request in your Approvals inbox, open the draft in Contracts, read it against the brief, approve it with a comment, and finalise it into a contract.7 min
31. 31AI inside a module: risk insights and their reasoningThis lesson is for the compliance officer. Some modules have an AI summary of their own. In the Risk Register it is called AI Insights: on request, the product looks across the entity's modules and writes findings, each with its reasoning. You will run the analysis, read one insight with the facts it relies on, and see that an insight is advice: it does not add a risk to the register by itself.6 min
32. 32Switch on the two specialist agentsThis lesson is for the person who manages the agents of an entity: here the tax manager. Beside the Tax Partner Agent, each entity can have two specialist agents. The Audit-Risk Agent runs the compliance checks and flags failing and overdue controls. The Regulatory Agent scores regulatory change and explains what each material update means. Like the Tax Partner Agent, each has to be switched on for the entity before it does anything. You will also use the action Classify documents, to see what an action reports when there is nothing for it to do.4 min
33. 33How this connects: the assistant, the agent and the recordsThis closing lesson is for everyone who took the course. It follows the records the course created through the product. You will ask the Compliance Assistant about three modules whose records were changed by other lessons: the contract that an AI drafted and a person approved, the transactions the agent classified, and the request the agent logged. Then you will open the notifications, My Actions and the Audit log, where that work lands and is recorded.8 min

How this connects to the rest of ComplianceOS

• Tax Intelligence

  The Compliance Assistant reads the tax transactions, with totals of sales and purchases, for a person who may view tax transactions. The Tax Partner Agent changes them: after an approval, the classification it starts appears in Tax Intelligence as an AI suggestion awaiting review, and a person with the approve permission approves it, for example in the Sign-off cockpit. The agent never approves a classification that only the AI has proposed.

• Compliance Calendar

  The assistant reads the calendar's deadlines for a person who may view compliance tasks. It cannot add one: it answers that nothing was changed and points to the calendar.

• Vendor Directory

  An answer given in the agent's Inbox to a question about a missing supplier tax registration number is checked as a 15-digit UAE number and saved on all of that supplier's tax transactions and on its Vendor Directory record. A skipped question changes nothing.

• Risk Register

  The assistant reads the Risk Register. AI Insights on the register, and the Regulatory Impact Analysis workflow, write risk insights with their reasoning; an insight is not added to the register until a person records it.

• Data Protection

  The assistant reads the data protection register, with each processing activity by name, for a person who may view Data Protection, and refuses other modules by naming the missing permission. Instructed by a person who may create records, the agent logs a data subject request, which appears under DSRs with its due date and raises a notification.

• Contracts and the Approvals inbox

  An AI agent drafts a contract from a brief; each revision is a new version, placeholders block approval, the draft appears in the Approvals inbox of a second person, and only after that person approves is it finalised into a contract that the assistant can report.

• My Actions and the agent's Inbox

  An approval the agent asks for under Ask first appears in the agent's Inbox and in My Actions. The agent's other questions, such as missing supplier tax registration numbers, appear in its Inbox only.

• Agent History and the Audit log

  Every agent run is kept in Agent History with its steps and the person who requested it, and can be exported. Each question to the assistant, and each record created or approved, is an entry in the Audit log; a record made through the agent names the person with the words via agent.

• Access control and Billing

  Using the assistant needs the permission AI assistant, Use, which the built-in roles hold when they can view a module the assistant reads; Who can lists everyone who holds it. AI usage is shown by module under Organisation settings, Billing, and each agent's monthly budget is set by an organisation administrator.