Skip to content

Partner-level settings

The Settings page in your partner menu is where your defaults live. Almost every setting in Tailor on a per-client basis has a partner-level counterpart that cascades to every client you onboard. Set them once here and most clients won’t need any per-client customization at all.

To get there, open the partner menu in the top-right of any page and click Settings.

The cascade model

Every cascading setting follows the same rule:

  • Per-client value (if set) → partner default.
  • Blank at the client level means “inherit the partner default” — never “show nothing.”

A consequence: changing a partner default automatically updates every client that hasn’t customized that field. The moment a client does customize a field, they stop following the partner default for that field going forward.

The Settings tabs

The main Settings page is a tabbed panel. Six tabs.

Whitelabel & Branding

Your default logo, sending name, and sending email. These are what your clients’ users see in training emails, phishing tests, the learning portal, and report PDFs unless a specific client overrides them in their Tailor.

Set these first — they’re the foundation everything else builds on. The Whitelabel checkbox on training reminders, the sender on breach notifications, the logo on report headers — all inherit from here.

See Branding defaults and per-client overrides for the per-client override workflow.

Automated Reports

The default set of report types that ship to clients in the monthly bundle, plus your global recipients — partner-side mailboxes that receive every monthly bundle for every client (your own address, your security team’s distribution list, etc.).

A footer reminds you when the monthly bundle goes out: monthly, on the 1st at 11:00 UTC.

See Scheduled reports for what’s in each report type and the per-client override surface.

Training Defaults

Four settings, all defaults for new clients only — existing clients keep whatever they had:

  • Schedule Frequency — Quarterly (4/year), Every 2 months (6/year), Monthly (12/year), or a custom number 1–12. This is how often new clients get training scheduled.
  • Time to Complete — how many days a user has to complete a course after it’s assigned.
  • Framework Time to Complete — the same window, but specifically for framework-required courses. Independent of the general value above.
  • Topic Priorities — the category order the adaptive scheduler walks for new clients. Reorder with the up/down arrows on each category; toggle individual categories off when you don’t want them in the rotation.

Each setting has a Reset to system default link when you’ve overridden it. Using system default with a placeholder value tells you what you’re inheriting.

See Control how training is scheduled for the in-depth walkthrough of these controls.

Phishing Templates

Your default category list and template-level enables. New clients inherit this configuration; per-client overrides happen in Tailor.

See Phishing templates for the categories vs library distinction and the simulation frequency / external email banner settings (which only exist at the per-client level).

Onboarding

Two settings on this tab — both shape the first impression your clients’ users get.

Welcome Email — partner-wide default. A single master toggle: Send welcome emails on or off. When on, every newly-synced user at every client receives a partner-branded welcome email before any training is assigned. Per-client overrides live in Tailor → Training → Onboarding as a tri-state (Inherit / On / Off), so you set the partner-wide intent here and only touch a client’s override when their needs differ. Off here keeps welcome emails off for any client whose per-client override is Inherit — those clients quietly start sending the moment you flip this on.

Default onboarding flow. The default onboarding modules new clients inherit — the in-portal flow new users see the first time they log in. Reorderable list of modules from the INFIMA catalog plus any custom modules (video or PDF) you upload yourself. The reordering sets the sequence; the Enable/Disable action gates whether a module is included. Custom modules can be deleted entirely; INFIMA-provided modules can only be enabled/disabled.

See Welcome email and onboarding for the per-client override mechanics and the “what the email looks like” example.

Dark Web

Default breach notification behavior — whether notifications fire, whether the affected user is notified directly, and your partner-side admin email list. Each client can either inherit these defaults or override per-client in their Tailor.

See Breach notifications for the tri-state inherit / yes / no behavior and the additive admin email semantics.

Training reminders

Open via Settings → Training reminders (a separate page off the main Settings panel). Configure the “course due soon” and “course overdue” email templates — subject, body, sender — with the same template variables and preview pane as the per-client surface.

See Training reminders for the full walkthrough.

Other Settings pages

A few partner-level settings live on their own pages off the main Settings panel:

  • Admins at Settings → Admins. Your admin team: invites, SSO, roles. See Manage your admin team.
  • Integrations at Settings → Integrations. PSAs (ConnectWise Manage, Datto Autotask, HaloPSA). See Integrations overview.

What you should set up first

A practical sequence the first time you set up your partner account:

  1. Whitelabel & Branding — logo, sending name, sending email.
  2. Training Defaults — pick a cadence (Quarterly is the most common starting point), set Time to Complete, leave Topic Priorities at defaults unless you have specific reasons to tune.
  3. Automated Reports — add yourself as a global recipient and pick which report types you want clients to receive by default.
  4. Dark Web — set your partner admin email so you get every breach notification.
  5. Training reminders — review the default copy. Most partners keep ours as-is.
  6. Onboarding — flip Send welcome emails on if you want every client sending welcome messages by default, and review the module list and reorder if needed.
  7. Admins — invite the rest of your team.
  8. Integrations — connect your PSA when you’re ready to automate billing.

After this, the typical Tailor pass on a new client is just branding → Report Phishing button setup → done. Everything else inherits.

Frequently asked

I changed a partner default — does that update every client immediately? For most fields, yes — except clients who’ve already overridden that specific field at the per-client level. Those clients stay on their own value. The exception is Training Defaults, which apply at client-creation time only and don’t reach existing clients (see the cascade note above).

How do I reset a client to inherit the partner default again? Depends on the field. Branding and reminder fields: clear the per-client value. Dark Web tri-state toggles: switch to Inherit. Automated Reports: there’s no current “reset to partner default” button — toggle the report types back to match your partner default manually, or contact our support team.

Settings changes I make now — do they apply to existing clients or only new ones? Existing clients with no per-field override pick up partner-default changes immediately. Existing clients who’ve overridden a field stay on their override. The Training Defaults tab is the exception — it explicitly says “These settings apply to new clients you add. Changes you make here won’t affect clients you’ve already created.”

Can my whole team have admin access? Yes — see Manage your admin team for invites and SSO setup.

Where do PSA settings live? Settings → Integrations. Different page, different model. See Integrations overview.

I want every client to send welcome emails to new users — do I have to flip the toggle on each client? No. Flip Settings → Onboarding → Send welcome emails on. Every client whose per-client override is Inherit (the default for newly-created clients) picks it up immediately. You only need to touch a specific client’s override under Tailor when their needs differ from the partner default.