Use Settings: Website when you need to audit website pages

Problem / use case

If you need to audit website pages, Settings: Website becomes fragile when the work behind open Settings, then Website as an admin. and Review public and admin-only website pages. is separated from Feature guide pages, Changelog, and Templates.

What should be done conceptually

Settings: Website works best when the settings admin decision, next action, and progress evidence stay close enough for audit website pages to remain visible.

TimeLens solution

TimeLens solves that by making Settings: Website part of the same workspace as Feature guide pages, Changelog, and Templates, so the feature helps the work move instead of becoming another isolated page.

Actual app screen

The public guide links to the real TimeLens route instead of showing a recreated mockup. Open the linked TimeLens screen to see the same route in action.

Open Settings: Website

Actual product snapshots

How to use it in TimeLens

Open Settings, then Website as an admin.; Review public and admin-only website pages.; Use the list for manual QA before pages are discoverable.

What it helps with

Audit website pages; Find admin-only pages; Support launch review

Where this feature connects

Feature guide pages; Changelog; Templates

Open this in TimeLens

This guide covers an admin-only product surface. Admins can open the matching TimeLens menu item after signing in.

Open Settings: Website · Sign up · Feature guide directory

Related feature pages

Continue with the most relevant TimeLens guide pages for this workflow.

Feature guide directory · Settings: Feedback · Templates · Settings: Week