Governance · for IT and audit — The process you designed is the process that runs. No skipped steps, no exceptions outside the rule.

Control for the audit, protection for whoever executes. Two guardians make sure the flow is followed; every move and every AI run is recorded with its cost; and whoever executes learns at the step itself.

The two guardians

Two guardians protect the operation. The second one rules over the first.

At Olie, two guardians protect the operation. The first says what each person can do: create, edit, view. The second says how the work moves: it doesn't skip a step, doesn't move forward without the required answer, doesn't blow the deadline without warning. The second rules over the first: not even the super admin breaks the flow. To change it, you have to edit the rule, and the edit is recorded.

First guardian

What each person can do

Create, edit, view: each person's role, plus funnel access.

Second guardian

How the work moves

It doesn't skip a step, doesn't move forward without the required answer, doesn't blow the deadline without warning.

For the audit, it is control: whoever changes the rule is on record. For whoever executes, it is protection: nobody asks to skip a step, because nobody can.

Locks · Restrictions

The step locks. Without the required items, the project stays where it is.

If a document or a required field is missing, the project doesn't leave the step, for anyone. The lock comes from five places: entry and exit restrictions per step, hierarchy restriction, step lock, mandatory movement checklist and required field.

  • Entry and exit restrictionWhat needs to be ready to enter and to leave each step.
  • Mandatory movement checklistIf it isn't checked, it doesn't move.
  • Required field and required formEmpty, it doesn't move.
  • Hierarchy restriction and step lockOnly the right role moves it; a locked step takes no one.
In what order does the platform check each move?
  1. Active funnel
  2. Role permission
  3. Link to the project
  4. Exit and entry restrictions
  5. Mandatory checklist and form
  6. Tag and status locks

The first rule that refuses is the message the person sees. A cloned funnel takes its rules along: the new unit runs just like headquarters.

yourcompany.olie.aiIllustrative exampleALBRCS
Edit project funnel
← Back | Settings › Funnels › Sales
SearchCtrl K3
Edit restrictions for the "Proposal" stage
×
Decision restriction Active
EntryExit
Current projectDescendantsAncestors
Expected revenue ▾Greater than ▾0
And ▾Contact ▾Is not empty ▾
+ Add filter
Without revenue and a contact, the project can't leave Proposal
1 newClose
No revenue, no leaving the stage
Records · Traceability and cost

Nobody says “I didn't see it”. Every move has an author, a time and a reason.

Each project keeps its edit and movement history (log). Each AI agent run generates a statement: model, tokens (the AI's unit of usage), cost, input and output. Each automation has a record per run. The WhatsApp conversation stays in the project, in the company's account, not on the phone of whoever answers.

  • Edit and movement logWho moved it, who edited the field, when.
  • Statement and cost of each AI runModel, tokens, cost, what went in and what came out.
  • Record per automation runFor debugging: what triggered, what ran, what failed.
  • WhatsApp recorded in the companyThe history stays with the company; the approval answered on WhatsApp goes to the log.
yourcompany.olie.aiIllustrative exampleALBRCS
PD‑1086 · Grupo Vértice
← Back | Funnel
SearchCtrl K3
Main# WhatsApp+Logs ▾
Yesterday
Project

Linked to the funnel Leads · Marketing. Action by: System

Moved to the stage Lead intake of the funnel Leads · Marketing. Action by: System

Moved to the stage Qualification. Action by: System. Automation: #3947 · Lead intake

Linked to the funnel WhatsApp · Quick replies. Action by: System. Automation: #3983 · Awaiting reply

Moved to the stage Pain points of the funnel Leads · Marketing. Action by: System. Automation: #3924 · Move by the lead's answer

Moved to the stage Replied of the funnel WhatsApp · Quick replies. Action by: System. Automation: #3982 · Set as replied

Field Order amount changed from empty to R$ 38,000. Action by: Ana Lima

Press Enter to send, "/" for commands and "@" to mention
Author and automation of every move
Teaches · Training at the step

Knowledge, skills and attitude delivered at each step.

Today, training is a welcome PDF and newcomers learn by asking in the hallway, each in their own way. At Olie, each step delivers what the person needs to execute it right: the instruction video, the checklist so nothing is forgotten and the right questions to move forward. And each answer in each field can lead to a different action.

  • Knowledge: mandatory videoThe person watches the step's instructions before moving the card.
  • Skills: the step checklistThe step-by-step checked item by item; if it isn't checked, it doesn't move.
  • Attitude: the right questionsThe step form asks for what needs to be answered to move forward.
  • Each answer, an actionA field's answer can alert someone, open another request or change the path.
Example: a refund request

Júlia gets the refund request through the step's rule and finds the video "How to review a refund", the checklist (check the purchase date, look at the photo, record the assessment) and an AI assistant for questions. She asks whether she can approve a 35-day-old purchase; the answer comes from the policy: refunds only up to 30 days; after that, offer the repair under warranty. A new hire follows the policy from day one. Illustrative names and values.

yourcompany.olie.aiIllustrative exampleALBRCS
Funnel
← Back | Support · Refunds
SearchCtrl K3
No business areaRefundsSearch30 daysList
RequestedR$ 0.00 • 32 projects
Ana
CS‑212Refund · order 8812
StatusIn Progress
4 D
Bruno
CS‑215Refund · order 8840
StatusIn Progress
5 D
+ Options
DoingR$ 0.00 • 71 projects
Carla
CS‑209Refund · order 8791
StatusIn Progress
5 D
+ Options
DoneR$ 0.00 • 180 projects
Diego
CS‑198Refund · order 8755
StatusComplete
5 D
+ Options
Stage trainingHow to review a refund
  1. Check the photo of the defect
  2. Review the customer's history
  3. Record the decision and the reason
0:00 / 2:14
Watching the video is required *Note: double-click to watch the video
Instructions before moving the card
What the audit asks for

A control that depends on someone remembering is not a control.

In the ACFE global study (2024, more than 1,900 cases in 138 countries), more than half of occupational frauds were linked to a lack of internal controls or to management overriding the controls, and the typical case took 12 months to be discovered. The auditor doesn't ask for good intentions: they ask for proof that the control ran. See where each requirement lives in Olie.

  • Audit trailWho did what, when, with the before and after: edit and movement log in each project.
  • Proof that the control ranThe restriction locks the step and each automation has a record per run.
  • Access management with historyRole per system function, funnel access and a record of who linked whom.
  • Segregation of dutiesHierarchy restriction: only the right role moves the approval step.
  • Time and cost of whoever executedRun history per person: start, end, duration and cost by hourly rate.
  • Retention and exportSpreadsheet of the projects and of the answers to any form, at any time, exported by the super admin. If the account is canceled, it stays in read-only mode for about 30 days for export.
yourcompany.olie.aiIllustrative exampleALBRCS
User details
← Back | Users › User details
SearchCtrl K3
SummaryProject executionsNotificationsNotebook
Detailed execution history
CodeProjectStageStartEndDurationCost
PD‑1041Proposal · Construtora Alfa ↗Drafting the proposal09/16 14:4909/16 16:421h 52mR$ 224.00
PD‑1043Proposal · Hotel Mirante ↗Review09/16 16:4209/16 17:3148mR$ 96.00
CS‑212Refund · order 8812 ↗Analysis09/18 13:5909/18 14:1011mR$ 22.00
PD‑1050Contract · Transportes Rio ↗Signature09/23 14:3009/23 14:3141sR$ 1.37
OP‑330Onboarding · Júlia M. ↗Documents09/24 15:1109/24 15:1248sR$ 1.60
PD‑1055Proposal · Ótica Central ↗Kick‑off09/25 14:2209/25 14:3210mR$ 20.00
Total of this data3h 02mR$ 364.97
Time and cost of every run
Who sees what

Each person sees the funnel and the number they need. And who granted each access is recorded.

The role defines what the person can do; funnel access defines where. To see cost or revenue, the person needs both permissions. The salesperson sees their funnel; finance sees invoicing; only those the company allowed see the margin. Each role link and each change is recorded, with author and date.

  • The role says whatMove, edit, approve, see amounts. You build the role.
  • Funnel access says whereWhoever doesn't have the funnel assigned doesn't see the project.
  • Cost and revenue only for roles that allow itThe role decides who sees the project's cost and revenue fields.
yourcompany.olie.aiIllustrative exampleALBRCS
Roles
← Back | Settings › Roles
SearchCtrl K3
Roles Create roles to organize permissions
NamePermissionsTypeUsers
Leadership147PartnerALBR
Sales manager38ManagerialALBR
Salesperson14OperationalALBR
Finance22OperationalALBR
Who granted each access, and when
For IT

What your IT team will ask. And what already exists today.

Where the data lives, how people sign in, what is recorded and who sees what.

  • Data on AWS in São PauloPlatform in the São Paulo region, with Cloudflare protection. AI is processed in the United States, by the model providers; the managed WhatsApp connection is in Europe.
  • Daily backupDaily copy, kept for 30 days.
  • Second factorSign-in with second-factor authentication.
  • LogsEdits, moves, each automation and each AI run, with author and time.
  • Permissions by role and by funnelThe role says what the person can do; the funnel says where.
  • Data protection agreement (LGPD)An agreement for your company to sign with Olie. Security and data

More information for IT: talk to Olie.

How does Olie ensure the process is followed?

With two guardians. The first says what each person can do (create, edit, view); the second says how the work moves: it doesn't skip a step, doesn't move forward without the required answer, doesn't blow the deadline without warning. The second rules over the first, and whoever edits the rule is on record. Entry and exit restrictions, checklists and required fields lock the step; edit and movement logs, the statement with the cost of each AI run and the record of each automation keep what happened; each step delivers a video, a checklist and the questions to move forward; and the check in a fixed order (active funnel, permission, link, restrictions, checklist and form, locks) shows the person the first rule that refused the move.

Governance questions

Can the super admin skip a step?

No. The super admin, included in the Subscription, configures the funnels and administers the platform, but also operates, so the same rule applies. The second guardian (the flow) rules over the first (the role). To change it, you have to edit the rule in the funnel's edit mode, and the edit is recorded.

Can the AI do something I didn't authorize?

No. The agent acts with the permissions you give it, at the step where you place it. Each run goes into the statement, with its cost, and there is a route for when it fails.

Can I prove, in an audit, that the process was followed?

The history of each project, the forms with versions and counters and the AI statement make up the record. The super admin exports the data.

Who sees revenue and cost?

Only those whose role allows it. For everyone else, the cost and revenue fields stay hidden.

Updated on · Source: Olie technical base · Security and data

Bring a critical process. Olie shows where it locks and what gets recorded.

The rule the company designs is the rule that runs, for everyone. In the next tab, see how your team builds all of this without coding.

Next step: 30 minutes to see your process on screen; then, a diagnosis with your leadership.

yourcompany.olie.aiIllustrative exampleALBRCS
Sales funnel
← Back | Funnels › Edit funnel
SearchCtrl K3
Edit restrictions of the "Proposal" stage
×
Restrictions

They limit entry to and exit from the stage: the project only enters or leaves when it meets every criterion.

Stage restrictionThe project only enters or leaves if it is in the chosen stage.
Tag restrictionPasses only with the right tag on the project.
Funnel status restrictionPasses only with the chosen funnel status.
Decision restrictionA filter on any project field, with And and Or.
Close