Analytics only counts things. It never includes prompts, code, file contents,
diffs, secrets or terminal output.
Who can see it
You need the View usage analytics permission. Admins have it by default. Without it, Analytics doesn’t appear in the sidebar. See Members and roles. On OpenWork Cloud, Usage & adoption and Workflow Runs are part of the Enterprise plan. On other plans, Usage & adoption shows an Enterprise notice instead of numbers, and the Workflow Runs tab doesn’t appear. Usage is still recorded, so it shows up as soon as the plan includes it. See Pricing and licensing.Numbers appear once members sign in to the OpenWork app with your
organization and run tasks. Until then, the page shows No activity yet.
See Sign in from the desktop app.
Usage and adoption
The Usage & adoption tab answers “is my team using OpenWork, and does it work for them?”- OpenWork users: people in the organization, and how many invitations are still pending.
- Active this week: people with at least one event in the last 7 days, and how many were active in the last 30 days.
- Sessions this week: sessions in the last 7 days, and in the last 30 days.
- Tasks this week: tasks in the last 7 days, and their success rate.
Look at one project
Use the project filter (All projects by default) to narrow the numbers to one project, for example to follow a rollout. OpenWork users stays the organization total. Click Refresh analytics to load the latest numbers.Plugins and connectors
The Plugins & connectors tab shows which parts of your Library people actually use. It’s available on every plan.- Choose Plugins, Skills or Connectors.
- Choose a time range: 7 days, 30 days or 90 days.
- Skills: each time an agent loads the skill.
- Plugins: their skills’ loads plus their workflows’ runs. Failed counts failed runs.
- Connectors: each tool call made through OpenWork. Failed counts calls that failed.
Workflow runs
The Workflow Runs tab lists your own runs of saved workflows and one-off tasks, newest first. Each run shows its name (or One-off task), when it finished, and Succeeded or Failed. Click Details on a run to see:- the workflow’s steps, when the run came from a saved workflow
- under Technical details: where the run came from (Source), the Tool calls it made, its Duration, and the Error if it failed
Related
- Audit logs: who changed what in your organization.
- Counting usage: AI Gateway requests, tokens and spend.