Skip to main content
The Users page shows everyone in your workspace and the status of each Fluency desktop agent. Admins use it to confirm the rollout is capturing, find users who need help, and invite other admins. Open app.usefluency.com → Settings → Users.
Settings Users table with status, device, and activity columns

Users: everyone in your workspace, their team and role, and the live status of each Fluency Desktop Agent.

​
The users table

The table lists up to 100 users per page. Use the filter box to search by name or email, and the column picker to show or hide optional columns. Select Invite Admin to add someone who can view Fluency without running the desktop agent.

​
Agent statuses

Most users show Capturing. If something needs attention, the status tells you what to do.
The agent is running and capturing activity.What to do: Nothing.
The user paused capture themselves. It resumes automatically at the end of the pause duration set in Agent Policy.What to do: Nothing, capture resumes on its own.
An admin paused this user.What to do: Resume the user from the row menu when you’re ready.
The current time is outside the observation window set in Agent Policy.What to do: Nothing, unless the window is set incorrectly.
The agent is missing macOS Screen Recording permission, or the equivalent on other systems.What to do: Ask the user to grant the required permissions so the agent can capture.
The agent hasn’t checked in during hours when it should be running.What to do: Check that the device is on and the agent is installed.
The user’s device is enrolled but the agent hasn’t checked in yet.What to do: Ask the user to launch the Fluency agent on their computer.
The user is signed out, or hasn’t installed the agent.What to do: Ask them to sign in or install the agent.

​
How Fluency picks a status

The agent checks in every few seconds while it’s running. Fluency combines those check-ins with your observation window to pick the right status:
  • Devices that are off outside the observation window aren’t flagged as a problem.
  • Offline only applies during hours when the agent should be running.
  • Issues that need action, like Permission required, show up at any time.
  • Paused by admin takes priority over other statuses.
  • The observation window respects timezones and can cross midnight. See Agent Policy.
Leaders don’t manage this table, they see team activity on Overview and Work Explorer. IT installs the agent, and admins use this page to confirm the rollout is capturing.

Agent Policy

Observation window, pause duration, and exclusions.

Deploy the agent

Installers, permissions, and network allowlists.

Teams

Group users so activity rolls up correctly.

PII Protection

Control what the agent redacts before it leaves the device.