Rules

Resourcing → Agents & copilots → Rules is where you write down your organisation's AI usage policy — spend limits, data protection, which providers and models are approved. Each rule reads as one plain sentence, and every change is kept as a new version of the policy.

Once your organisation has rolled out the Cloud Proxy, Flowstate records each time an AI request matches one of your rules, so you can see how the policy is working in practice.

You need AI governance admin access to see this tab — ask your Flowstate admin.

Read the rules list

Rules are grouped by what they cover: Spend limits, Data protection, Access & keys and Model & usage.

Column	What it shows
Action	What the rule says should happen: Block, Warn or Info
Fired (30d)	How many times a request matched the rule in the last 30 days. — new means none yet.

To find a rule:

1. Search for words in the rule's sentence.
2. To narrow the list, filter by Effect or Concern.
3. To reorder it, sort by Effect or Times fired.

Tip

Fired (30d) only counts once the Cloud Proxy is rolled out. Before that, every rule shows — new.

Add a rule

1. Open Resourcing → Agents & copilots → Rules and select Add rule.
2. Pick a template, or select Start from scratch.
3. Fill in When, Who it applies to and Then.
4. Check the reason under Because, then select Add rule.
5. In the banner above the list, select Activate.
6. Write a Change summary and select Activate.

The rule is saved to a draft at step 4, and becomes part of your policy at step 6.

Read it before you add it

As you fill in the blanks, This rule will read shows the sentence the rule will become.

If the rule is for A team, A person or A service, the rule opens after you add it so you can choose exactly which one. Do this before you activate.

Change or remove a rule

1. Select the rule on the list.
2. Make your change and select Save changes — or select Remove rule and confirm.
3. In the banner, select Activate, write a Change summary, and select Activate.

To throw away a draft instead, select Discard in the banner.

See what a rule has matched

1. Select the rule on the list.
2. Select Activity.
3. Read the two lists:
   • Recent enforcement (last 30 days) — each time a request matched the rule, with the date and the reason.
   • Alerts raised by this rule — the detections the rule raised. Select one to open it.

If the rule hasn't matched anything, you'll see No enforcement events or alerts for this rule yet.

Go from a rule to its detections

1. On the list, select the … fired link next to the rule.
2. Insights → Agent insights → Alerts opens. If it shows an alert, select All signals at the top of the alert list.
3. Above the detections you'll see Showing alerts for: and the rule. Select a detection to deal with it.
4. To see every detection again, select the cross next to the rule's name.

Tip

View alerts, above the rules list, opens Alerts without narrowing it to one rule.

See earlier versions

Select History to see every version of the policy: its version number, whether it's Active, Draft, Superseded or Archived, the change summary written when it was activated, and when it was in force.

If something's not right

Activate stays greyed out — Write a Change summary. It's required.

"Couldn't match this rule in the draft — review the draft, or discard it and try again." — The draft changed while you were editing. Select Review to check it, or Discard it and start again.

Alerts shows fewer detections than the fired count — Fired (30d) counts every match in the last 30 days. Alerts lists the detections raised for the period chosen at the top of All signals, and not every match raises a detection. Change the period to see more.