# Set rules for everyone in a workspace

On Enterprise, how the owner or an admin sets rules that refuse actions for everyone in the workspace, or send them to an approver first, such as payments above a limit, in chats, scheduled tasks and live pages, and what a member sees when a rule applies.

Workspace rules let the owner and admins refuse some actions for everyone in the workspace, or have someone approve them first. For example, a rule can refuse refunds above $10,000, more than $2,000 of payments per person in a day, emails to more than 500 recipients, or sharing outside the company from a task that an email started.

A rule applies to everything the assistant and your connectors do in the workspace: in chats, in scheduled tasks, in tasks started by an event, and on live pages. It is checked **before** anyone's own settings. Don't ask, **Never ask before changes**, and the permissions a task or a page has can't lift it.

Workspace rules are part of [Bluedeer Enterprise](https://support.bluedeer.ai/team-and-enterprise/plan-overviews/what-is-enterprise.md). On the Team plan they show locked, with an **Enterprise** badge, and owners and admins can select **Contact sales** from there.

## Add a rule

Only the workspace owner or an admin can see and change rules. On the web, open the **Workspace** page, select **Settings** and choose the **Rules** tab. On the phone, open **Manage workspace**, and on **General** tap **Workspace rules** under **Rules**.

1. Select **Add rule** and give the rule a name. Members see this name when the rule refuses something, so make it clear, such as "Refunds above $500".
2. Under **What it covers**, choose the actions:
   - **Kind of action:** money out (refunds, payouts and payments), sending messages, bulk messages, sharing outside the company, bulk deletes and others.
   - **Apps** and **Connectors:** only the actions of these apps or connectors, such as Stripe.
   - **Where:** chats, scheduled tasks, tasks started by an event, or live pages.
   - **Started by:** only tasks that a particular event started, such as a new email.
     Leave a group empty to cover everything in it. With nothing chosen, the rule covers every action, everywhere.
3. Under **What it does**, choose **Refuse it**, or **Ask for approval** and then **Who approves**: any workspace admin, the workspace owner, two workspace admins, or one member by name. See [Actions that need approval](#actions-that-need-approval).
4. Under **Refuse when** (or **Ask for approval when**), add the checks. Every check must hold for the rule to apply:
   - **Amount above:** the amount is above the limit, in one currency.
   - **Daily total per person above:** this action and the person's others in the last 24 hours add up to more than the limit, in the same currency, so a payment can't be split into smaller ones to get past a limit. Actions still waiting for an answer count too, while they wait.
   - **More than:** the action touches more records, or a message has more recipients, than the number.
   - **Risk at least:** the action's risk is at least the level you choose.
   - **Amount unknown:** the action's amount or currency can't be read.
   - **Someone outside the company:** a recipient is outside your [verified domains](https://support.bluedeer.ai/team-and-enterprise/identity-management/verified-domains.md). To let the AI contact some outside domains and addresses, see [Outside addresses](https://support.bluedeer.ai/team-and-enterprise/security-and-compliance/outside-addresses.md).
     With no checks, the rule applies to every action it covers.
5. Turn the rule on and select **Save rule**.

Below your rules, **Starting rules** lists suggested rules, each off. Turn one on to add it, then change its numbers if you need to.

## When something can't be read

Bluedeer reads the amount, the currency, the number of records and the recipients of each action where it can: from Bluedeer's own apps, and from the main connectors, such as the amount of a Stripe refund. When it can't read them, for example for a custom connector's tool, it treats the action as the riskiest kind:

- an amount or currency that can't be read counts as **above** any limit;
- a count that can't be read counts as **more** than any number;
- a recipient that can't be told inside or outside the company counts as **outside**. Without a verified domain, every recipient counts as outside.

So a rule over a kind of action or a connector refuses its unknown cases too. A rule can't pick out one amount from a custom connector's tool that Bluedeer can't read; it covers that tool as a whole.

## Actions that need approval

A rule set to **Ask for approval** doesn't refuse the action. It sends it to the approver you chose, and nothing happens until they answer:

- In the chat, the person who asked sees **Waiting for** the approver, with the rule's name and why it applies, and when it expires. They can open **Details** or **Cancel** it, but they can't approve it themselves, and the card has no **Don't ask again**.
- The approver gets an item under **Needs your attention** in the Inbox, an email and a notification on their phone. Opening it shows exactly what will happen: the action, its target, the amount, the recipients, the email itself for an email, and what a connector's tool is given. They select **Approve** or **Reject**. When rejecting, they can add a short reason (optional, up to 500 characters), which the person who asked sees with the rejection.
- Once approved, the action runs with the account of the person who asked, not the approver's. Its result goes back into that person's chat, and the assistant carries on from it. If it's rejected, nothing is done and the chat says so.
- If the action changes after it was sent, for example the email is edited, the approval is canceled and nothing is done. The person can ask again.
- If nobody approves it within 24 hours, it expires and nothing is done. The person who asked is told.
- With **Two workspace admins**, two different admins must approve it. One rejection ends it.

The person who asked never counts as an approver. If nobody else can approve it right now, for example because the rule names them, the action is refused at once instead of waiting.

### In scheduled tasks, tasks started by an event and live pages

Nobody is there to wait for an answer while a task runs, so the step waits instead:

- The run carries on with its other steps. The approver is asked exactly as for a chat, and the item says which of the person's scheduled tasks asked. The task's run history shows the step as **Waiting for** the approver, with **Details**, and the run's result says it's waiting.
- Once it's approved, the action runs with the task owner's account, and the same run shows how it went. The task owner is told, and the notice opens the task.
- If it's rejected, nothing is done for that step and the run shows **Declined by reviewer**, with who declined it and their reason if they gave one. If nobody approves it within 24 hours, nothing is done for it and the run shows **Approval expired**. A run shows **Succeeded** only when every step sent to an approver was approved and done. See [What is in a task's results and run history?](https://support.bluedeer.ai/using-bluedeer/tasks-and-inbox/task-results-and-run-history.md)
- Allowing an action for a task doesn't lift the rule: the step still waits for its approver every time. Before a task is scheduled, its permissions card lists such steps under **These steps will wait for an approver each time**. A rule over scheduling tasks also sends the task's own permissions card to the approver.
- On a live page, the page shows that the action is waiting for approval. Nothing happens until it's approved, and the person who used the page is told the answer in their Inbox.

### Emails you send from a draft card

Sending, saving or scheduling an email yourself from its draft card follows the same rules. If a rule sends it for approval, it goes to the approver exactly as when the assistant sends it:

- The card says **Waiting for** the approver, with the rule and when the request expires. While it waits, the card can't be changed or sent again.
- Once it's approved, it's sent with your Gmail and the card says **Email sent** (or **Saved to Gmail drafts**, or **Scheduled for** a time) and who approved it.
- If it's rejected, the card says who rejected it and that nothing was sent. If nobody approves it within 24 hours, the card says so and you can send it for approval again.
- The card shows the same state after a reload or on your other devices. An open card checks for the answer on its own: every few seconds at first, then less often.

If a rule refuses it, nothing is sent and the card names the rule.

### Tasks you save yourself

A rule over **New schedules and automations** also covers tasks you create or edit yourself on the Tasks page or in the app, not only the ones the assistant sets up. It's checked when you save a new task, and when an edit changes the task's instructions, its schedule, or adds an action it may take. Renaming a task, changing who is notified, its privacy or its limit isn't checked.

- If a rule refuses it, nothing is saved and the message names the rule.
- If a rule sends it for approval, nothing is saved yet and you see **Waiting for** the approver, with the rule. Once they approve, the task is created (or changed) as you saved it, and you're told the answer in your Inbox. If it's rejected, or nobody approves it within 24 hours, nothing changes.

If a refusing rule and an approval rule both apply, the action is refused.

## What a member sees

When a rule refuses an action, nothing is sent or changed. In a chat, the assistant says that the workspace rule refused it and names the rule. In a scheduled task or a task started by an event, the run carries on without that step, and its result says which rule refused it. A live page shows the same reason.

Only an owner or an admin can change a rule. A member who needs the action can ask them.

## Turn a rule off or remove it

Use the switch next to a rule to turn it off. It stays in the list without acting on anything. To remove it, select the bin next to it.

If the workspace moves from Enterprise to the Team plan, rules that are on keep acting. You can turn them off, remove them, or make them stricter, but not looser. A rule is stricter when it covers more actions or acts more firmly: for example, when you add a kind of action or an app to a list that already names some, clear a list so it covers everything, remove a check, lower an amount or a count, or choose **Refuse it** instead of **Ask for approval**. Naming fewer things, adding a check, raising an amount, changing the currency, asking for approval instead of refusing, or choosing another approver needs Enterprise. A choice that would loosen a rule is unavailable and says why when you hover over or focus it. Adding a rule, and changing or turning on a rule that is off, also need Enterprise.

## Always ask before anything goes outside

Separately from the rules above, and on every shared workspace plan (it doesn't need Enterprise), there are two protections for things that go to people outside the organization. Outside means anyone who isn't a member of the workspace, on one of your [verified domains](https://support.bluedeer.ai/team-and-enterprise/identity-management/verified-domains.md) or on the workspace's [allowed outside addresses](https://support.bluedeer.ai/team-and-enterprise/security-and-compliance/outside-addresses.md). Members count by the exact address they sign in with (another address of theirs, or one with a `+tag`, is outside); people invited who haven't joined, and people who were removed, are outside; members without a seat are inside.

- **Files always ask.** When the assistant would send or share a file with someone outside the organization, the approval card is always shown, even if the person chose **Don't ask** for that action. The card's **Don't ask again** is grayed out and says why when you hover over or focus it. A file that goes only to people on the allowed outside addresses follows the person's usual rule.
- **Always ask before anything goes to people outside the organization.** This switch is under **Outside recipients** on the **Rules** tab: on the web, open the **Workspace** page, select **Settings** and choose **Rules**. Only the workspace owner or an admin can change it, and it is off by default. When it's on, every email, invitation, share or message that would reach someone outside asks for approval every time, with or without a file, and **Don't ask again** is grayed out on those cards.

A scheduled task, a task started by an event, or the owner's own live page can't show a card. Its step waits for the person who owns the task or page to approve or refuse it from their Inbox (with a notification and an email), for up to 24 hours; nobody else can answer it, and the owner's earlier **Don't ask** never approves it. If nobody answers, nothing is sent. Later runs don't ask again for the same action while one waits. At approval, the workspace's rules are checked again, and a rule that now refuses the action or sends it to an approver wins. Someone else's use of a live page can't send it.

Neither applies to a personal workspace. A Slack channel, and a connector tool whose recipient Bluedeer can't identify, work as before. A workspace rule that refuses an action, or sends it to an approver, still does. Turning the switch on or off is a line in the workspace's Activity.

## Activity

Adding, changing, turning on or off and removing a rule are each a line in the workspace's [Activity](https://support.bluedeer.ai/team-and-enterprise/analytics-and-activity/workspace-activity.md), with the rule as it was. So is each action a rule refused, with who asked for it and the rule's name. For approvals, Activity shows the request, each answer (approved, rejected, withdrawn or canceled because it changed) and approvals that ran out of time, each with the rule as it was and the amount.
