Overview
Company Overview gains three capabilities that give admins a direct read on who uses Pipefy, how licenses are distributed, and how much AI is being consumed. You track users by status and role, see AI credit consumption almost instantly in Single Tenant structures, and export API usage reports with a single click.
What's new?
- Users Usage Stats: a dedicated user view inside Company Overview, available in the Users tab. It shows the total number of users across the ecosystem, the split between paid and free users, users inactive for more than 60 days, and distribution by role.
- Near real-time AI credit usage charts for Single Tenant: credit consumption by agents and assistants now appears almost instantly in Single Tenant structures too, in the same AI monitoring panel.
- API export available to everyone: the API usage export button is now available across the enterprise base. You download the consumption report with a single click, straight from the API visibility panel.
How does this help?
- You optimize license allocation with a clear split between paid and free users, matching the contract to actual usage.
- You spot seat-reclamation opportunities by immediately seeing which users have been inactive for more than 60 days.
- You govern permissions precisely through user distribution by role, with no spreadsheets needed to know who has which access.
- You monitor AI consumption without waiting for sync in Single Tenant environments, with near-instant reads of credits per agent and assistant.
- You take API data wherever you need it by exporting the consumption report with a single click, with no request or manual process involved.
Use cases
1. An IT admin reviewing the contract before renewal.
Opening the Users tab in Company Overview, the admin sees that 40 of 220 paid seats belong to users inactive for more than 60 days. They export the list, validate it with the business areas, and reclaim the idle seats before renewing, sizing the contract by real usage instead of a historical headcount.
2. Permission governance across a multi-company structure.
An admin responsible for several companies uses distribution by role to check how many users hold an admin profile in each one. They find administrative access that was granted ad hoc and never reviewed, then adjust the roles, keeping least-privilege in place without a manual audit.
3. AI consumption control in a high-compliance Single Tenant client.
A company in a Single Tenant environment tracks the AI credits consumed by its triage agents and support assistants. With the near real-time read, the team notices a consumption spike right after enabling a new agent and adjusts its scope that same day, instead of waiting for a sync cycle to close before reacting.
4. Reporting API consumption to finance.
A technical lead needs to hand finance the quarter's API consumption, broken down by operation name, PATs, and service accounts. Instead of opening a ticket, they export the report directly from the panel with one click and deliver the data in the format finance uses for internal chargeback.
5. Diagnosing adoption before expanding the account.
Before proposing expansion to new areas, an admin cross-references total active users with the paid-versus-free split and distribution by role. They find that most paid seats are concentrated in a few teams and use that picture to ground where growth makes sense, rather than expanding blindly.
Most relevant for
- IT admins
- IT Leaders
- License and contract managers
- Admins of multi-company structures
Plans and availability
API report export is available across the enterprise base. Near real-time AI usage charts apply to Single Tenant structures. Users Usage Stats live in Company Overview, in the Users tab.
