Manage Tenant Rules

In /activeguard/core/rule_sets/, you have two kinds of folders. Everything in 90_local acts as the default configuration for all tenants. In the _tenant folders, you can override the configuration by adding new files or overwrite those from 90_local. This structure is automatically used when you create a campaign or add list entries for a single tenant.

Folder structure of /activeguard/core

/
├─ activeguard/
│  ├─ core/
│  │  ├─ active_guard.yml
│  │  ├─ rule_sets/
│  │  │  ├─ 90_local/
│  │  │  ├─ _tenant1/
│  │  │  ├─ _tenant2/
│  │  │  ├─ ...
├─ ...

Tenant-Specific Rules

If you want to create a rule that only applies to a single tenant, place the rule file in: /activeguard/core/rule_sets/_tenantX/rules/custom/.

Tenant-Specific Parameters

You can do the same for .properties files. To set different rule parameters for individual tenants, set up tenant.properties like this:

In /shared/guarded_tenants.yml, add tenant.properties to the rule profiles:
guarded_tenants.yml
tenants: - name: example ruleProfiles: - tenant.properties

Create /activeguard/core/rule_sets/90_local/params/tenant.properties and add a placeholder comment:

/activeguard/core/rule_sets/90_local/params/tenant.properties

# This is a placeholder for the tenant-specific properties file.
# Create and edit the tenant-specific file at:
# /activeguard/core/rule_sets/_tenantX/params/tenant.properties

Add your configurations in /activeguard/core/rule_sets/_tenantX/params/tenant.properties for the individual tenants.
For example, you can add the contents of profile_no_subject_rewrite_no_quarantine.properties to tenant.properties to enable a tenant-specific “toothless mode.”

​Tenant-Specific Rules

​Tenant-Specific Parameters

Tenant-Specific Rules

Tenant-Specific Parameters