Summary
Request for per-site SharePoint look‑back controls so admins can set site‑level windows (e.g., “Site A = 1‑year” and “Site B = all‑time”), rather than a single global time restriction for all sites.
Problem statement
A single global time restriction does not work because different sites have different retention, compliance, and freshness needs. Admins need the flexibility to tailor look‑back windows at the site level.
Key use cases
- For regulated or sensitive sites, use a shorter look‑back (e.g., 90 days or 1 year) to reduce exposure and limit processing scope.
- For high-value knowledge hubs or long-running projects, keep all‑time history to preserve discoverability and context.
- For pilot, archival, or low‑signal sites, tighten look‑backs to reduce crawl volume, speed up syncs, and improve signal‑to‑noise.
Why this matters
- Aligns to retention/compliance policies while maintaining discoverability where needed.
- Reduces crawl volume, speeds up syncs, and improves signal‑to‑noise for low‑value sites.
Questions for the community
- Would you prefer configuring this as a global default + site overrides, or entirely site‑by‑site?
- What look‑back granularity do you need (e.g., 30/90/180 days, 1/2/3 years, all‑time)?
- Should exceptions be managed by explicit site lists, by site templates, or by classifications/labels?
