Online Help

Schedules Reference

Reference for the per-Site Scan and Audit schedule catalogs: list view, fields, attachment rules, RBAC split, and Audit-log footprint.

Two separate catalogs

Schedules live in two distinct catalogs at the same menu depth:

Catalog Menu path Type Attachment target
Scan schedules Admin Center > Site Settings > Settings > Scan schedules Scan Segments (one or more)
Audit schedules Admin Center > Site Settings > Settings > Audit schedules Audit Devices (max one schedule per device)

A schedule defined in one catalog cannot be promoted to the other; a Scan schedule cannot be assigned to a device, and an Audit schedule cannot be attached to a Segment.

List view

Both catalogs share the same column set:

Column Type Description
Name String, link User-set label. Sorted ascending by default.
Type Enum (Scan / Audit) Derived from which catalog the schedule lives in.
Created at DateTime System-set on creation.
Last execution DateTime Most recent run. Empty until first run.
Next execution DateTime Computed from the schedule cadence.

Toolbar: Default View ▼ / + New schedule / Filter / ⋯ / ⚙️.

Fields on the create form

Field Required Description
Name yes Human-readable label. Surfaces in the catalog grid and in the Scan log / Audit log.
Granularity yes Daily, Weekly, or Monthly. Per-cadence detail fields (specific time of day, day of week, day of month) may vary by deployment.

Attachment rules

Schedule type Where attached Constraint
Scan Segment view → schedule slot A schedule may attach to many Segments; a Segment may carry many scan schedules.
Audit Device → Audit tab → Assign schedule A device holds at most one Audit schedule at a time. Assigning a different schedule replaces the existing one.

Log footprint

Schedule type Log Initiator value
Audit Audit log Schedule
Scan Scan log Schedule (per docs; may vary by deployment)

RBAC

The administrative split is the load-bearing fact for this section:

Action Site Administrator Site User
Create a schedule definition yes no
Edit a schedule definition yes no
Delete a schedule definition yes no
Assign a schedule to a device or Segment yes yes
Unassign a schedule from a device or Segment yes yes

This split lets a Site User own a device's audit cadence — picking and switching among schedules the administrator has defined — without giving them the ability to add or remove schedule definitions from the Site catalog.

Constraints

  • A device cannot hold more than one Audit schedule. Use multiple schedules with different attachments, not one schedule with multiple attachment slots.
  • Cadence detail beyond Daily / Weekly / Monthly is not authoritatively documented at this build level.
  • Scan-log rows for scheduled scans (Initiator = Schedule) may not appear in every deployment; absence is not a definitive failure indicator on its own.