The Users Overview report gives you a workspace-level view of the people represented in GUIDEcx.

For administrators, operations teams, and delivery leaders, it helps answer a practical question:

Who is in our workspace, and what do we need to know about their access, role, and participation?

Use the report to review internal, customer, and partner users, understand user status and role distribution, inspect capacity information, and investigate individual workspace-member records.

Use Users Overview to understand:

Unlike most other Standard reports, Users Overview has no report-level filters.

There are no report-level filters on Users Overview.

The report is designed to provide a workspace-level view of users rather than a project- or task-filtered population.

That makes the workflow slightly different from other GUIDEreports:

Summary metric → user breakdown → workspace-member details

If you need to investigate a particular person, use the available user-level detail rather than looking for the standard Customer, Project Status, Task Status, or date filters found on other reports.

Start with the summary metrics to understand the overall makeup of the workspace.

Question it answers: How many users are represented in the workspace reporting population?

Total Users counts workspace users while excluding Super Admin users.

Use this as the broadest membership count in the report.

Question it answers: How many workspace users are part of our internal team?

This metric excludes:

Use it when you need to separate internal workspace membership from external customer and partner participation.

Question it answers: How many customer users are represented in the workspace?

This metric counts workspace members with the Customer role.

Use it to understand the overall external customer-user population represented in GUIDEcx.

Question it answers: How many partner users are represented in the workspace?

This metric counts workspace members with the Partner role.

Use it when your delivery model includes partners and you want to understand their representation separately from internal and customer users.

Summary counts tell you how many users exist.

Status and role views help explain how those users are represented.

Question it answers: What is the current status distribution of our workspace members?

Use this view to move beyond the overall user count and understand how members are distributed across the statuses represented in GUIDEreports.

If one status stands out, use the member details to investigate the individual records behind it.

Question it answers: How is workspace membership distributed by role?

This view groups users using the role represented in the widget's reporting data.

Use it to understand the makeup of the workspace rather than treating every user as part of the same population.

Note: The exact workspace-role values represented in your results depend on the user records in your workspace.

Users Overview can also help distinguish broad workspace membership from users represented across project teams.

Question it answers: How many team members are represented across our projects?

Use Total Team Members for a broader view of project-team participation.

This is different from Total Users, which describes workspace membership.

Question it answers: How many team members are represented on currently active project work?

Active Team Members focuses on people allocated to projects that are not:

Use it when your question is about current delivery participation rather than overall workspace membership.

These concepts answer different questions:

Do not assume these metrics should always match.

Question it answers: Which internal assignees currently have the greatest concentration of Stuck work?

This view ranks up to 20 task assignees by the number of tasks currently marked Stuck.

Projects that are:

are excluded.

Use this as an investigation starting point rather than a performance score.

A user appearing in this view tells you that Stuck work is concentrated with that assignee.

It does not tell you:

Review the underlying work before drawing conclusions.

The Workspace Members detail view provides the individual user records behind the summary metrics.

It can include:

For the canonical field definitions, see the GUIDEreports drilldown field reference.

The detail table is especially useful when a summary number tells you something is worth investigating.

Invitation Accepted At shows when the workspace member accepted their invitation.

Use this field when you need to distinguish between the presence of a user record and the available invitation-acceptance information for that user.

For example, if you're reviewing workspace onboarding, the field can help identify which records have a recorded acceptance date.

Do not assume the reason for a missing value from the report alone.

Review the underlying user record and applicable workspace process if further investigation is needed.

Allotted Capacity Hours shows the capacity value associated with the workspace member.

Use it as context when your organization uses GUIDEcx capacity settings for resource planning.

The field describes the configured value associated with the user.

It should not be interpreted by itself as:

For actual tracked-time analysis, use Standard report: Advanced Time Reporting.

The member details can include:

These fields provide reporting context about the workspace-member record.

Use them as investigation signals.

For example, if a user appears to have an access issue, these fields can provide useful context about whether lock, failed-login, or deactivation information is recorded.

The report itself does not establish why an account was locked, why a login failed, or why a user was deactivated.

The following is an illustrative administrator scenario.

An administrator is preparing for a team transition and wants to understand the current workspace membership.

Their question is:

Do our user records reflect the people and access we expect?

They start with:

This gives them a high-level picture of the workspace.

They check:

One user-status group deserves a closer look.

They use Workspace Members to inspect:

For internal users involved in resource planning, they also review Allotted Capacity Hours.

Where a record does not match expectations, the administrator can use the underlying user information to determine what action is appropriate.

Instead of manually reviewing every user from scratch, Users Overview helps identify which records deserve attention.

These are suggested reporting practices rather than product requirements.

This report is designed for user and membership analysis.

If your question is primarily about project progress, tasks, CSAT, or tracked time, use the corresponding Standard report instead.

You cannot narrow Users Overview with the standard GUIDEreports report-level filters.

Use the available summary views and member details to investigate the workspace population.

Workspace membership and project-team participation are related but different concepts.

Use Total Users for workspace membership and the team-member views when your question is about project participation.

A user status can help identify records worth reviewing.

Use the individual member details before deciding what the status means operationally for that person.

A failed-login count tells you what is recorded in the reporting data.

It does not establish the reason for the failed attempts.

Allotted Capacity Hours represents configured capacity information.

Use Advanced Time Reporting when you need actual tracked effort.

If an internal user appears in Internal Users with Most Stuck Tasks, review the underlying tasks and project context.

Concentration identifies where blocked work exists, not who caused it.

No.

Users Overview does not have report-level filters.

It provides a workspace-level view of the users represented in reporting.

Total Users represents the broader qualifying workspace-user population.

Total Internal Users excludes Customer, Partner, and Super Admin users.

No.

Total Users excludes Super Admin users.

Total Users describes workspace membership.

Total Team Members describes people represented across project teams.

They answer different questions and should not be expected to match.

It counts team members allocated to projects that are not Cancelled, Pending, or Done.

Use it when your question is about current project participation.

The Invitation Accepted At field shows the recorded invitation-acceptance date when available.

It is the capacity-hours value associated with the workspace member.

It is different from actual tracked time.

For actual time worked, use Advanced Time Reporting.

No.

It provides the number of failed attempts recorded for the user.

Use it as account context rather than a diagnosis of the underlying issue.

It shows when the workspace member was deactivated, when a deactivation date applies.

The report can provide operational context such as capacity, project-team participation, or concentration of Stuck work.

Those values do not by themselves establish individual performance.

Review role, workload, project context, and the underlying work before drawing conclusions.

See the GUIDEreports drilldown field reference.

Review the available user and resource-allocation widgets in the GUIDEreports widget library.

If you need a different combination of available widgets, you can build a custom GUIDEreport.