Using Tenant Config Templates

A config set supports the following parameters. All those parameters can also be set directly on a tenant.

guarded_tenants.yml

configSets:
  default:
    interTenantMessageSplitting: true
    tenantSelector: {}
    tenantSelectors: []
    autoLoginLink: {}
    quarantine: {}
    dataRetention: {}
    emailTemplateStyle: default
    messageProcessing: {}
    emailReporting: {}
    trustedMTAs: {}
    ruleProfiles: {}

Checkout the guarded_tenants.yml for more details what each attribute supports.

You can overwrite single parameters of the default set without having to specify all other parameters.

You can create new config sets and reference them in some tenants. The default set is always applied to all tenants with the least precedence.

guarded_tenants.yml

configSets:
  allowPhishingRequest:
    quarantine:
      quarantines:
          - name: Phishing
            canRelease: true

tenants:
    name: xorlab
    ## Applied config sets, notice that later occurrences will override earlier config set occurrences.
    ## Further, the "default" set is implicitly referenced with least precedence.
    configSets:
        - allowPhishingRequest

⌘I