What is the workforce view?
The workforce view is the roll-up across every Digital FTE an organization runs. It lists each role with its status, its named manager, its approval rate, and the count of items waiting on someone, and it combines the roles' morning briefs into one list ordered by what blocks the most, so a finance exception waiting on the controller appears above a routine outreach approval a team member will clear.
It is the organization's view of its digital workforce, in the same sense that a team lead's view of their people is a list of who is doing what and who is waiting on whom.
How does it work on ftes.ai?
On ftes.ai the workforce view is the landing screen for an organization with more than one role, and the place from which a new role is hired. Each row links to that FTE's own workspace. The combined brief draws from each role's Today tab and orders items by their blocking effect: escalations and gated proposals above detections, roles with the oldest waiting items first.
For organizations with several properties, the view filters by property, so an agency can see one client's roles alone. Adding a role from here runs the first-run wizard, which pre-fills everything the platform already knows and asks only for what is new to the function.
Why does it matter for a manager of several roles?
It matters because it keeps management time from growing with each role. A manager who had to open three workspaces every morning would read three briefs; the workforce view gives them one, ordered, and their day starts with the items that matter most regardless of which role raised them. The routine items are already routed to team members and cleared from there.
It also makes patterns across roles visible. An FTE whose waiting count keeps growing has an approver who is not approving, which is a routing fix. An FTE whose approval rate is falling is drifting, which is a remit or source fix. Two FTEs whose targets overlap are duplicating work, which is a boundary fix.
- Growing waiting count: an approver who is not approving
- Falling approval rate: drift, read the send-back reasons
- Overlapping targets: a remit boundary to redraw
- Rising usage with flat outcomes: a model tier or scope question
How does it relate to the individual workspaces?
The workforce view does not replace the individual workspaces; it is the roll-up above them. A manager decides most items from the combined brief, because each carries its evidence, and opens a role's workspace for the review, the remit, the memory, and the setup. The monthly review is per role, from each role's own report.
It is also the manager's own manager's view. A head of operations who does not manage any role directly can see the state of the whole workforce, who manages what, and where things are waiting.
What is it often confused with?
It is confused with a dashboard of metrics; it is a list of roles and their waiting work, ordered, with the brief items attached. It is confused with the Discover page on the marketing site, which lists roles available to hire; the workforce view lists roles the organization has hired. And it is confused with an admin console; it is a management view for the organization, not an operator tool.
It is sometimes assumed to show every organization's roles to every user. It shows one organization's, under that organization's roles and permissions.
Where do you see it?
It is the app's landing screen for a multi-role organization and is reachable from any workspace. The combined brief, the per-role rows, the property filter, and the hire action are all there. Manager assignments made from it are logged.
Related terms: morning brief, workspace, property, approval rate, first-run wizard.
A practical habit for a manager of several roles is to clear the combined brief before opening any single workspace, and to open a workspace only for a review, a remit change, or a memory correction. Managers who do this find that three roles cost little more morning time than one, which is the whole point of the roll-up.