How pedrowerkhaizer/emb-people-intelligence-hub works
People Intelligence Hub is an internal People Analytics catalog: employees open the portal, receive group-aware visibility, search or navigate to an item, and view its details or linked report. The administration console manages the catalog and related navigation, audience groups, useful links, and updates; server-side catalog logic validates and persists changes. The README documents additional features such as favorites, feedback, and simulation, but sampled excerpts do not establish all of their wiring, so those connections are not inferred.
Main entry points: server.js HTTP server · app.js Catalog experience · admin-core.js Admin workflow · catalogStore.js Catalog persistence
Components 19
Employee portal
- Hub interface
public/index.html - Catalog experience
public/app.js - Shared helpers
public/lib/catalog-utils.js
Identity and access
- MSAL authentication
public/msal-auth.js - Role resolution
api/GetRoles/index.js
Catalog administration
- Admin console
public/admin.html - Admin workflow
public/admin-core.js - Catalog table
public/admin-table.js - Catalog editor
public/admin-forms.js - Form validation
public/lib/validate-payload.js
Server and catalog data
- HTTP server
server.js - Catalog persistence
api/catalogStore.js - Catalog data
- Initial catalog seeds
seed/items.json
Other components
- Employee
- Admin user
- Entra ID
- Microsoft Graph
- Linked reports
Connections 22
- Employee → Hub interface: opens
- Hub interface → Catalog experience: loads
- Catalog experience → HTTP server: fetches catalogs
- HTTP server → Catalog persistence: reads catalogs
- Catalog persistence → Catalog data: reads and writes
- Initial catalog seeds → Catalog persistence: seeds missing data
- Catalog experience → Shared helpers: uses status helpers
- Catalog experience → MSAL authentication: initializes sign-in
- MSAL authentication → Entra ID: authenticates
- Catalog experience → HTTP server: requests roles
- HTTP server → Role resolution: resolves groups
- Role resolution → Microsoft Graph: checks membership
- Admin user → Admin console: opens
- Admin console → Admin workflow: loads
- Admin workflow → Catalog table: renders catalogs
- Admin workflow → Catalog editor: loads editor
- Catalog editor → Form validation: validates input
- Admin workflow → MSAL authentication: gets access token
- Admin workflow → HTTP server: calls admin API
- HTTP server → Role resolution: authorizes admin
- HTTP server → Catalog persistence: mutates catalogs
- Catalog experience → Linked reports: opens linked report