> ## Documentation Index > Fetch the complete documentation index at: https://docs.quintai.dev/llms.txt > Use this file to discover all available pages before exploring further. # Baseline policies > Build the rules your customers inherit, check them against every customer, save revisions, and have a second admin apply one. A **baseline** is a set of rules you write once for all the customers you manage. Each customer's policy is your baseline plus the customer's own rules on top. **Baselines**, under **Operations** in the console, is where you draft a change, check it against every customer and save it as a revision; another admin applies it. Who can do what: **Viewer** reads, **Analyst** drafts changes and checks them, **Admin** saves revisions, and a second **Admin** applies them. ## The page Three figures, **Customers**, **On this revision** and **Mode**, sit above the current revision's progress: "Saved — waiting for another admin", "Applied by another admin" and "Reaching customers". | Card | What it holds | | - | - | | **Rules** | Every rule in the current revision, with **What it watches** and its outcome: **Record**, **Ask for approval** or **Refuse**. | | **Customers** | For analysts and admins, one row per customer: **Revision they have**, **Mode**, **Their own rules** and **Status**, such as **Up to date** or **Waiting to apply**. | | **Revision history** | "Every revision saved, newest first, and who applied it." | A baseline is **Recording only**, where customers' machines record what each rule would have done, or **Set to enforce**, where the machines that act on it ask and refuse as each rule says. A customer's own enforcement switch doesn't reach your rules: in **Set to enforce** they can refuse actions even where that switch is off. ## Draft a change **1. Start a rule** **New rule** › **From scratch** builds one rule. **New rule** › **From a template** opens sets of rules Quint ships: untick the ones you don't want, then **Add *n* rules to the draft**. To change a saved rule, click its name or open its menu. **2. Build it** **What to watch** is what the agent does that the rule notices. **What happens** is the outcome, a **Name** and a **Category**. **Check** tries the draft against every customer: "Nothing is saved or applied." **Done** returns you to the list; the rule is already in your draft. **3. Read the draft bar** The bar counts your changes and says which revision customers keep meanwhile. "This draft lives in this tab until you save a revision: a reload starts again from revision *n*." **Discard** throws the draft away after you confirm. ## Save a revision Press **Review and save** (an **Analyst** gets **Review changes**, without the save). Anything that "Needs fixing first" is listed at the top with **Fix**. Then come the **Changes** against the current revision, the **Mode** to save with, and **Customers**: each one's result is "Fits · changes their rules", "Fits · no change" or "Doesn’t fit". The check shows counts, never a customer's own rules. Add an optional **Note**, then press **Save revision *n***. Saving changes no customer. A revision that doesn't fit every customer can still be saved, but it can't be applied. ## Apply a revision Applying needs a second admin. The admin who saved the revision sees "You saved this. Another admin applies it." Any other admin sees **Waiting to apply** and **Review and apply**. **Apply revision *n*?** lists the changes against the revision your customers have now, and runs a fresh check when it opens. The apply carries a digest of that check: if the result has changed by the time you press **Apply revision *n***, nothing is applied and you see the fresh check. If the revision doesn't fit every customer, the apply button is disabled. Only the newest revision can be applied. Once applied, "Quint sends it to each customer on its next pass". > [!NOTE] > > Where applying is switched off, the console says "Applying is switched off for partner baselines right now, so no customer receives this revision." and the apply button is disabled. Ask your Quint contact. ## Start from an older revision In **Revision history**, open a revision and press **Restore these rules into the draft…** (Admin). The draft takes that revision's rules and mode; if it already has changes, choose **Keep my draft** or **Replace the draft**. Save it as a new revision. ## If this fails | What you see | What it means | What to do | | - | - | - | | "Someone saved revision *n* while you were working. Your draft is kept — review it against revision *n*, then save again." | Another admin saved after your draft started. Nothing was saved. | Review the draft, then save again. | | "You are this partner's only admin. Saving a revision works, but another admin has to apply it: add a second admin under Operators first." | Nobody else can apply | Add a second admin. | | "The plan changed since you reviewed it. Review the fresh plan below and apply again." | The check changed after the dialog ran it | Read the fresh check, then apply. | | "Only the newest revision can be applied. Reload the revision list." | A newer revision was saved | Reload. | | "This revision doesn’t fit with every customer’s own rules, so it can’t be applied. Save a revision that fits every customer, then apply that one." | A customer's own rules conflict with the baseline | Change the draft until it fits, then save and apply. | ## Next * [How policies work](https://docs.quintai.dev/policies/how-policies-work.md), the customer side * [Audit and sessions](https://docs.quintai.dev/partners/audit-and-sessions.md), where saves and applies are recorded This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.