> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useglimps.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setting up self-driving

> Say who goes about what in your own words, and decide what Glimps may do by itself.

Open **Self-driving > How it is set up**. Two things live here: what Glimps may do, and who gets which question.

## What Glimps may do by itself

Per kind of case you pick a rung: **Off**, **Watch**, **Ask**, or **Handle itself**. See [the four rungs](/self-driving/overview#the-four-rungs).

The risk is different per kind of case, which is why this is not one switch. Coding a line wrongly costs a correction. Paying a fraudster costs the money.

## Say it in your own words

There is one box for everything. Write the arrangement the way you would say it to a colleague:

> purchase order differences above 1000 euro go to Sam, and the ones due this week to the finance group

Glimps reads the sentence and shows you what it understood before anything is stored. You get:

* **This is how I read it**: the plain reading of your sentence.
* **These become the rules**: the rules that would be created, in priority order.
* **What this would have done to your own cases**: your sentence replayed against real routing decisions from your own administration.
* **What I still need to know**: anything ambiguous, such as two colleagues who both fit a first name.

Nothing is stored until you say so. If two names both fit, Glimps stores nothing and says which two.

## What you can say

* Who gets something: a person, a group, a department, or the supplier.
* From what amount, or in what range.
* What Glimps may do by itself for that kind of case.
* Conditions no field exists for, such as "due this week", or "from a supplier we do not know".

A rule with a condition in words is judged per invoice. If there is any doubt, that rule sits out and the other rules decide.

<Note>
  Your sentence is kept next to every rule and every setting that came out of it. Months later you can still see why a question reached somebody, in the words you used.
</Note>

## Priority

Rules are applied in order, and the lowest priority number wins. Existing rules are never rewritten or renumbered when you add a new sentence.

## Cases with no owner

On **What is happening**, the band **A rule is missing here** lists what came past recently with no rule to route it, such as "12x difference with the purchase order on the unit price". Each one has a **Write a rule** button that starts the sentence for you.

Some of those did have a rule, but its condition in words did not hold. That asks for different wording, not for another rule.

## Ledger account categories

A rule that routes on a kind of cost needs your ledger accounts grouped into categories. Without categories, "packaging differences go to the warehouse" has nothing to stand on.

## A sensible order

<Steps>
  <Step title="Put one kind of case on watching">
    Pick the one you deal with most.
  </Step>

  <Step title="Read what it would have done">
    Two weeks is enough to see whether the questions make sense.
  </Step>

  <Step title="Write the routing rules">
    Start with the gaps Glimps lists, because those are the cases you actually get.
  </Step>

  <Step title="Move to asking">
    Real questions to real people. The answers still come back to a person who carries them out.
  </Step>

  <Step title="Move to handling, one kind of case at a time">
    Only when the answers come back quickly and the outcomes were right.
  </Step>
</Steps>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.