📊Users Analytics

Canonical expansion of the ~140-word stub. This is still one Users page, not a new analytics product.

What this is / when to use it

Users Analytics shows how people use the published app: who signed in, which screens they open, and (when enabled) visitor counts on public screens.

Use it to answer “is anyone using this?” and “which role is stuck.” It is not Notion analytics and not Workflow run history.

Before you start

The app has been published and at least one user (or guest on a public screen) has opened it.

Build it

You do not build Analytics. Open Users → Analytics (or the Analytics item in the Users rail).

Every control

Control	What it does
Date range	Limits the report.
App users	Signed-in people (plan meter: app users).
Visitors	Public/anonymous hits (plan meter: visitors).
Screen breakdown	Which screens were opened.
Searchable field types	Which property types the everyday Search screen can index (text-like fields). Not a separate product — Search configuration lives on Search.
Activity kinds	What the Activity chrome lists: queue, notification, approval, workflow (and related automation item types). See Activity.

End-user notification prefs are not this page. Users set them on Profile. Makers set audience defaults in the how-to Configure App Audience and Notification Prefs.

What users see

Nothing. Analytics is a maker surface.

Limits and plans

Visitor and app-user meters are plan-gated. Over cap, new visitors may still open public pages but the report and billing treat them as overage — see Plans.

Example

After launch week you see 12 app users, 40 visitors on the public Welcome content page, and almost no opens of Workflow Status. You move Status out of the client nav.

Fix problems

Symptom	Likely cause	What to do
All zeros	Not published, or no traffic	Publish. Open the app yourself.
Visitors but no users	Public screens only	Expected for a landing page.

Related

App Users. Plans. Everyday chrome Search / Activity / Profile.