Skip to main content
A flag marks an account as being in a state worth acting on: a risk like usage falling away before a renewal, or an opportunity like a trial that’s outgrown its plan. Flags open on their own when an account matches a rule, and close on their own when it stops. Flags turn up on the Flags page, the one list of everything needing attention, and on the account they’re about. The rules that raise them live under Settings → Flag rules.
A flag is not the same thing as an indicator. An indicator is a number or a yes/no computed from product events — it’s an input. A flag is something a person is meant to do something about.

What a flag carries

Addressed is not the same as closed

This is the distinction worth knowing, because it’s what stops a long-running risk nagging a team that has already dealt with it.
  • A flag closes by itself, when the account no longer matches the rule. Nobody closes a flag by hand.
  • A flag is addressed by a person, meaning “we’ve seen this and it’s handled”. The condition may well still be true.
So a flag can sit addressed for weeks while the underlying situation persists — that’s correct and intended. It drops off the Needs attention list and stays visible under Addressed. If you addressed something too early, Reopen puts it back. When the condition finally does clear, the flag closes whether or not it was addressed. If the same condition comes back later, that’s a new flag rather than the old one reopening, so the history reads as two separate episodes instead of one that flickered.

Where flags turn up

There is no separate flags screen to check. A flag reaches the places work already happens: An addressed flag drops out of the digest and the inbox’s working list, because the decision has been made. It stays on the account page until the condition clears.

Filtering the list

Filter them on the Flags page: Narrow to flags alone with the Type filter: Risk or Opportunity.

Where flags come from

Flags come from rules, and a rule is a segment plus a kind. Any account in that segment gets a flag of that kind; when it leaves the segment, the flag closes. Open Settings → Flag rules to write one. A rule needs: Until there is at least one rule, no flag can open, however your accounts are doing.
Settings → Flag rules: the Add a rule form above the list of rules, each with its kind, segment and an on/off switch
Each rule has a switch. Pausing one stops it raising anything new and leaves the flags it already raised open, because they describe something that happened. Edit changes its name, kind, segment or assignment without rebuilding it. Using segments means flag rules inherit everything segments already do, including change-over-time conditions and the customers/accounts level — so a rule on a customer-level segment raises one flag per customer rather than one per account. Rules are checked every hour, so a new rule takes up to an hour to raise its first flags. Deleting a rule stops it raising anything new. Flags it already raised are kept, since removing them would rewrite what your team saw and acted on.

Reading flags elsewhere

Flags are readable over the API and from MCP with list_flags and get_flag, filtered by status, kind or account. The same needsAttention filter is available, so an assistant can be asked what needs attention today and get back the list you’d see on the page. They’re read-only there. Opening and closing belongs to the rules, and marking one addressed is a statement about your team that should carry a real person’s name rather than an API key’s.

Parent accounts

A flag on a child account also shows on its parent, labelled with the account it came from. The parent doesn’t get its own copy — one flag stays one flag, so a customer-level count never doubles it. A parent shows as needing attention when any of its accounts has an open, unaddressed flag.