vituliani
Case study 04

Every guest, accounted for.

An overview dashboard for external users in Microsoft Teams: who they are, which teams they can reach, who vouched for them, and when that access expires.

Role Product designer
Scope Research, IA, UI, themes
Platform Teams tab, light and dark
Year 2023
external user manager / overview
External User Manager overview in the light Teams theme
Scroll
01 / The problem

Guest access is invited once and forgotten forever.

Contractors, agencies and partners get added to a channel by whoever needed them that week. Months later nobody can say how many externals hold access, which teams they can still open, or who is responsible for them. Admins asked for one place, plus the reporting to prove it to leadership.

Need All externals, and their teams, at a glance
Pain No analytics, so no way to spot a trend
Limit Sensitive identity data, handled inside Teams
02 / References

No direct competitor, so I studied the adjacent field.

External User Manager had no like-for-like product on the market. Instead of benchmarking a competitor, I built the reference set from enterprise identity and user-management platforms, research papers and industry reports, plus consultations with experts in UX and Microsoft Teams administration.

Each one answered a different question: what admins expect to monitor, how such tools stay usable at scale, and how access and permissions are normally governed.

Reference 01 Okta User Management Customizable dashboards that let administrators monitor user activity, access requests and other critical data points.
Taken forward: the counters at the top are the admin's to-do list, not decoration.
Reference 02 Ping Identity A scalable platform built for large enterprises, able to manage millions of users across many applications.
Taken forward: the table has to survive hundreds of rows, so filtering lives in one panel.
Reference 03 IBM Security Identity Governance Comprehensive governance of user access and permissions across multiple applications and systems.
Also in the mix Research papers and industry reports on enterprise user management
Also in the mix Best practice guides for governing guest access at scale
Also in the mix Expert consultations in UX and Microsoft Teams administration
Needs, pains and limitations from stakeholder interviews
Research board of needs, pains and limitations
03 / The overview

Four numbers that start every morning.

The header carries the live count with a trend curve, then three counters that are really a to-do list: dormant guests to remove, requests to approve, violations to investigate. Each one is a filter into the table below.

Header, as built
KPI header with external user count and trend
04 / One table

Users, teams, organisations.

The same records, pivoted three ways, because admins arrive with three different questions. Status is always a chip, the responsible person always has a face, and every column is filterable from one panel instead of six menus.

Users view
External users table with status chips
Teams view, expanded
Teams view with expanded rows
Filter panel
Filter panel for the external users table
05 / The guest profile

Access with an expiry date.

Each guest gets a record: who they are, who invited them, every team they touch, and a lifecycle bar that runs from granted access to renewal to deletion. The history column is the audit trail, so an approval decision never depends on memory.

Profile, light theme
Guest profile in the light Teams theme
Profile, dark theme
Guest profile in the dark Teams theme
06 / Theme parity

It has to feel native in both Teams themes.

Every surface, chip and chart was specified twice against the Teams palette. Status colour keeps the same meaning in both, contrast is checked on the dark side where the soft green and red normally collapse.

Overview, light theme
Overview in the light Teams theme
Overview, dark theme
Overview in the dark Teams theme