Skip to main content

General Settings

General Settings is where you adjust the governance thresholds that Audit 360 uses to categorize spaces by activity level and identify cleanup candidates in the Spaces Audit.

Overview

The Spaces Audit relies on activity thresholds and work-item counts to categorize each space and calculate governance risk. By adjusting these thresholds, you can fine-tune which spaces surface as "active," "low-activity," or "cleanup candidate" signals to match your organization's governance policy.

Adjusting Thresholds

When you open General Settings, you see four numeric fields. Each represents a threshold that Audit 360 reads at the start of the next Spaces Audit run.

To adjust a threshold:

  1. Go to Config (gear icon in the top navigation).
  2. The General Settings tab opens by default.
  3. Edit any threshold value directly in its field.
  4. Click Save configuration to persist your changes.

If you make a mistake or want to revert, click Reset to defaults to clear all unsaved changes and restore the default values shown on screen. This action does not make a network call — it only resets your local edits.

On success, a confirmation message appears briefly, and the thresholds take effect immediately. Future Spaces Audits use your new values.

The Four Thresholds

Active Activity Threshold (days)

Default: 90 days

Valid range: 1 to 3,650 days

What it does: Spaces updated within this many days are flagged as active. For example, if you set this to 90 days, any space with a change in the last 90 days is considered active.

When to adjust: Lower this value if you want to mark spaces as active more aggressively (sooner after their last update). Raise it if you want to be more conservative and wait longer before flagging a space as active.

Low Activity Threshold (days)

Default: 180 days

Valid range: 1 to 3,650 days

What it does: Spaces with no updates for this long are flagged as low-activity. For example, if you set this to 180 days, a space without any changes for 180 days or more is considered low-activity.

When to adjust: Lower this value if you want to identify stale spaces faster. Raise it if your organization tolerates longer periods of inactivity before considering a space at-risk.

Important: The Low Activity Threshold must be greater than or equal to the Active Activity Threshold. For example, if your Active Activity Threshold is 90 days, your Low Activity Threshold must be at least 90 days. If you try to save a combination that violates this rule, Audit 360 rejects the change and shows an inline error message.

Low Activity Work-Item Count

Default: 5 work items

Valid range: 0 to 100,000 work items

What it does: When a low-activity space has this many work items or fewer, it becomes a cleanup candidate. For example, if you set this to 5, and a space is flagged as low-activity with 3 or 4 work items, it is marked as a potential cleanup candidate.

When to adjust: Lower this value if you want to mark more spaces as cleanup candidates (only the emptiest, least-active spaces). Raise it if you want to flag low-activity spaces more aggressively regardless of work-item count.

Trash Retention (days)

Default: 60 days

Valid range: 7 to 365 days

What it does: Audit runs you move to trash are automatically deleted this many days after being trashed. For example, if you set this to 60, a run moved to trash today will be permanently removed 60 days from now if you do not restore it first.

When to adjust: Lower this value if you want shorter retention (to clean up trash faster). Raise it if you want a longer grace period to recover trashed audits.

Retroactive effect: Unlike the activity thresholds, changing trash retention has a retroactive effect. If you lower the retention window, audit runs already in trash that are old enough may become eligible for immediate deletion on the next daily purge. If you raise the window, runs already trashed get a longer grace period.

Cross-Field Validation

Audit 360 enforces one rule across the active and low-activity thresholds:

Low Activity Threshold must be ≥ Active Activity Threshold

This ensures the time windows do not overlap logically — the low-activity window cannot end before the active window. For example:

  • ✅ Active: 90 days, Low-Activity: 180 days — valid (low-activity window is longer)
  • ✅ Active: 90 days, Low-Activity: 90 days — valid (they can be the same)
  • ❌ Active: 180 days, Low-Activity: 90 days — invalid (active window is longer than low-activity window)

If you try to save a combination that violates this rule, Audit 360 rejects the change and highlights the problem field with an inline error message. Fix the value and try again.

Default Values

If you reset all thresholds to defaults or if a threshold has never been saved, Audit 360 uses these built-in defaults:

ThresholdDefault
Active Activity Threshold90 days
Low Activity Threshold180 days
Low Activity Work-Item Count5 work items
Trash Retention60 days

When Changes Take Effect

  • Activity thresholds (Active Activity Threshold, Low Activity Threshold, Low Activity Work-Item Count) take effect on the next Spaces Audit run. Existing audit results are never recalculated — only future runs use your new values.
  • Trash retention takes effect immediately and is evaluated retroactively on the next daily automatic purge. Trashed runs are assessed for deletion based on the current retention window, not the value that was in effect when the run was trashed.

Customized Indicator

When any threshold differs from its default value, a Customised badge appears next to the General Settings heading. This visual cue lets you quickly see that you are using non-default governance thresholds.

The badge disappears if you reset all values back to defaults.

Error Handling

If Audit 360 cannot save your changes, an error message appears briefly at the top of the page. Your changes are not lost — they remain in the form so you can try again or adjust them further.

Common reasons for save failures:

  • A network error prevented communication with the backend.
  • You were disconnected during the save operation.

Click Save configuration again to retry.