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

> ## Agent Instructions
> These docs contain multiple Speckle product experiences. For Speckle 2026.9, prefer /next/ pages for the topics and changes they cover. The navigation label Current does not override this version-specific precedence.
> Coverage under /next/ is incremental. Use Current documentation for unchanged topics and when a /next/ page says coverage is unavailable or explicitly refers you to Current. Do not infer a feature was removed from a missing page.
> Read the page-specific documentation status, applicability, affected guidance and replacement links in agent-only content. Impacted, changed and superseded apply only to the stated scope; they do not mean the entire feature is deprecated. Historical connector guides apply only to the legacy connector described.
> Match guidance to the customer's deployment version, model data format and connector. Respect plan, permission and compatibility restrictions. If an unknown version or data format changes the answer, ask a focused clarification; do not infer deployment version from the date alone.

# Set standing AI Rules for the workspace

> Workspace-admin governance for Speckle Intelligence — standing instructions applied to every conversation.

Documentation set: Speckle 2026.9. Status: current. Authority: canonical for this version and the coverage on this page.

Applies to version 2026.9, from 2026-09; this is not a rollout date for every deployment.

Authoritative Speckle 2026.9 documentation for the topic covered here. For Speckle 2026.9, prefer this page over conflicting earlier guidance. Follow the linked pages in the other documentation version for unchanged topics and where this page says coverage is not yet available. Respect data-format, deployment, plan, permission, and compatibility limitations stated in the page.

<Note>
  This is 2026.9 documentation. Coverage here is incremental: a page exists only where 2026.9
  differs or is newly documented. For any other topic, switch to **Current** (2026.8 and earlier) in
  the version selector.
</Note>

An **AI Rule** is a standing instruction Speckle Intelligence follows in **every** conversation
in the workspace. You do not type a slash command. Enabled rules shape Chat and the viewer
sparkle on each turn until an admin disables or deletes them.

Use rules for organisation governance: currency, language, safety, disclosure, or any constraint
that must apply even when nobody arms a skill. For opt-in playbooks people invoke with
`/skill-name`, see [Reuse organisation playbooks with Intelligence
skills](/next/analytics/intelligence-skills). For where to ask questions, see [Ask questions about
your models with Speckle Intelligence](/next/analytics/intelligence).

<Note>
  AI Rules appear when the workspace plan includes Speckle Intelligence Chat. On a self-hosted
  server, Chat is available only on Speckle Enterprise Server. For deployment setup, see [Enterprise
  license — Intelligence](/developers/server/deployment/enterprise-license#optional-intelligence).
</Note>

## When to use a rule

Use a rule when the answer must always follow the same constraint — for example always report
costs in EUR, always write Reports in Turkish, never invent missing quantities, or always name
the version before a total.

Do not use a rule for an optional playbook (colour theme, cost method, carbon factors someone
chooses per ask). That is a **skill**. Do not use a rule for a one-off question.

If you only need the assistant to match the language of your question for that conversation, ask
in that language. Speckle Intelligence usually keeps replying in the same language without a rule.
Use a rule when the language must stay fixed even if someone asks in another language.

Rules are workspace governance. Only **workspace admins** create, edit, enable, disable, or
delete them. Every member can open **Settings → AI Rules** and read the instructions. In Chat, a
**Workspace rules** control shows which enabled rules apply to the conversation.

## Create a rule

As a workspace admin:

<Steps>
  <Step title="Open AI Rules">
    Open the workspace, select **Settings**, then **AI Rules**. You should see the heading **AI
    Rules** and **New rule** when you can manage rules.
  </Step>

  <Step title="Name the rule">
    Select **New rule**. Set **Name** to a short label such as `Currency` or `Turkish reports`.
    Members see this name in Chat under **Workspace rules**.
  </Step>

  <Step title="Write instructions and create">
    In **Instructions**, write what Intelligence must do on every turn — for example **Always report
    costs in EUR.** or **When creating or editing a Report, write all narrative in Turkish.** Select
    **Create**. You should see the rule on the list, enabled by default.
  </Step>
</Steps>

### Enable, disable, or delete

On the AI Rules list, use the switch to **Enable** or **Disable** a rule without deleting it. A
disabled rule shows a **Disabled** badge and stops applying on the next conversation turn.

Use the row menu to edit or delete. Delete asks for confirmation: conversations stop following
that rule on the next turn. Past replies stay as they were.

A workspace can hold up to 25 rules. Enabled rules share a combined instructions budget, so keep
standing text short. Prefer a focused skill for long playbooks.

## What members see in Chat

When at least one rule is enabled, Chat shows a **Workspace rules** control. Open it to see the
enabled rule names and the note that they are set by workspace admins and applied to every
conversation. Admins also see **Manage**, which opens **Settings → AI Rules**.

Rules apply whether or not a skill is armed. A skill adds an opt-in playbook on top; it does not
turn rules off.

## What to put in a rule

Keep rules short and absolute. Good standing constraints:

* Always report costs in the organisation's currency (for example EUR or GBP).
* When creating or editing a **Report**, write all narrative, titles, and labels in Turkish (or
  another language). Keep numbers and units from the data.
* Never invent quantities, rates, or carbon factors. If the data is missing, say so.
* Always name the version, the publisher, and the source application before any total.
* Prefer the organisation's words for coordination issues, levels, and packages.
* Do not give legal, safety, or compliance advice beyond what the published model states.
* Keep replies suitable for external clients (no internal codenames, no unreleased rates).

If the instruction is long, optional, or method-heavy (colour legends, factor tables, full cost
methods), put it in a [skill](/next/analytics/intelligence-skills) and keep the rule as the short
must-follow line.

## Rules and skills

* Standing constraint on every conversation — use an **AI Rule**.
* Opt-in playbook with `/skill-name` — use a **skill**.
* Match the language of this conversation — ask in that language (no rule required).
* One-off question — use Chat with no skill armed.

Create rules in [workspace Settings](/next/workspaces/settings) under **AI Rules**. Create
skills under **Skills**.

## FAQ

<AccordionGroup>
  <Accordion title="Who can create AI Rules?">
    Only workspace admins. Members and guests can read the rules list and see **Workspace rules** in
    Chat. They cannot create, edit, enable, disable, or delete rules.
  </Accordion>

  <Accordion title="Can a rule turn Speckle Intelligence off?">
    No. Rules constrain answers; they do not stop conversations. To make Chat and the viewer sparkle
    unavailable to the whole workspace, a workspace admin turns **AI features** off in **Settings**,
    then **General**. See [Turn AI features off for the
    workspace](/next/it-admin/introduction#turn-ai-features-off-for-the-workspace).
  </Accordion>

  <Accordion title="Do rules apply when I use a skill?">
    Yes. Enabled rules still apply. The skill adds extra instructions for that message on top of the
    rules.
  </Accordion>

  <Accordion title="Do rules change a report I already saved?">
    No. Opening a saved report does not re-run Intelligence. Rules apply when Chat creates or edits
    content. Ask Chat to revise an existing report if you need it rewritten under a new rule. See
    [Create and share Intelligence Reports](/next/analytics/reports).
  </Accordion>

  <Accordion title="What happens if I disable a rule?">
    The AI stops following it on the next conversation turn. The rule stays on the list with a
    **Disabled** badge so you can turn it back on later.
  </Accordion>

  <Accordion title="Why can't I add another rule?">
    A workspace can have at most 25 rules. Enabled rules also share a combined instructions length
    limit. Shorten or disable other rules, or move long playbooks into a skill.
  </Accordion>

  <Accordion title="Should Turkish reports be a rule or a skill?">
    Use a **rule** when every Report (and every Chat turn you care about) must be in Turkish without
    anyone arming a slash command. Use a **skill** when people opt in with `/turkish-reports` for
    some asks only. If you only need Turkish for one conversation, ask in Turkish — Speckle
    Intelligence usually keeps that language. See [Reuse organisation playbooks with Intelligence
    skills](/next/analytics/intelligence-skills) and [Create and share Intelligence
    Reports](/next/analytics/reports).
  </Accordion>
</AccordionGroup>


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