This is a collection of some common Authelia Rules.
:::note[RULE ORDER]
It is important that rules are created in the correct order in Authelia. Rules are processed from top to bottom with the first matching rule being applied. The most narrow rules should be applied first with the most broad rules last.
For theses rules to work as intended, your default access control policy must be set to `deny`.
:::
All rules requiring Authelia authentication were configured with `two_factor` (2FA). If you do not want 2FA on some or all rules replace the Policy with `one_factor`.
In this guide we assume you have a group `admin` and a group `user` in ldap.
Members of the `admin` group will have access to everything.
Members of the `user` group will only have access to a select set of apps you choose.
This rule will bypass Authelia for API level access in most apps. This should always be your first rule.
Domain: `*.domain.tld`
Policy: `bypass`
Subject: `Not Used (Do Not Add)`
Networks: `Not Used (Do Not Add)`
Resources:
-`^/api([/?].*)?$`
-`^/identity.*$`
-`^/triggers.*$`
-`^/meshagents.*$`
-`^/meshsettings.*$`
-`^/agent.*$`
-`^/control.*$`
-`^/meshrelay.*$`
-`^/wl.*$`
![authelia-api](./img/authelia-api.png)
## Vaultwarden
These rules will protect the Vaultwarden admin page with Authelia but bypass when accessing the web vault. The order of these rules is critical or the admin page will not be protected.