# An introduction to Rules

### What are Rules?

Rules are automations that you can put in place to help streamline your team's workflows so that you can spend more time on your customers and less on managing an inbox.

For each shared inbox, you can have a different set of rules set up. The rules work using an 'IF-THEN' logic. There are a number of criteria for you to choose from to ensure that each rule performs exactly as you need.&#x20;

**NOTE: Rules are only available on our Pro Plan upwards. If you'd like to talk to us about upgrading your plan please get in touch at <support@intheloop.io>**

### Where can I find Rules?

Only an admin can access, create or edit rules. They can be found in the shared inbox settings. (Settings > Shared Inbox & Team Settings)&#x20;

### Example Rules

In Loop, we have set up three example rules for you. Feel free to use these as they are, edit them or remove them completely.

The three rules are:

* **Remove unwanted email:** For inbound emails, if the sender's email starts with 'noreply', 'no\_reply' or 'no-reply' then the email is deleted.
* **Assign new emails to team lead:** For inbound emails which are part of a new email thread, assign them to a particular person. (You would need to choose the person)
* **Archive email after sending new email or replying:** For outbound emails, send them to the archive folder.

[Take a look at some other examples of rules that you could set up.](/workflow-automation/examples-of-popular-rules.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.intheloop.io/workflow-automation/an-introduction-to-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
