Use Settings: Access when you need to enable gated features

Problem / use case

If you need to enable gated features, Settings: Access becomes fragile when the work behind open Settings, then Access as an admin. and Review feature toggles and admin overrides. is separated from Import, GitLab, and Category focus.

What should be done conceptually

Settings: Access works best when the settings admin decision, next action, and progress evidence stay close enough for enable gated features to remain visible.

TimeLens solution

TimeLens solves that by making Settings: Access part of the same workspace as Import, GitLab, and Category focus, 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: Access

Actual product snapshots

How to use it in TimeLens

Open Settings, then Access as an admin.; Review feature toggles and admin overrides.; Change flags only when the release state is clear.

What it helps with

Enable gated features; Review admin-only access; Control rollout state

Where this feature connects

Import; GitLab; Category focus; Activity focus

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: Access · Sign up · Feature guide directory

Related feature pages

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

Import your history · GitLab integration · Category focus · Activity focus