GEN-17 · Presence

GEN Hubs

One workspace per person: owners and employees each see exactly their slice of the system.

Core system component

Watch

GEN Hubs, presented

The film — GEN Hubs

A short walkthrough: what GEN Hubs is, how it works, and how it's set up. Opens with the GEN mark and this product's name — every film in the library is made for its product.

What it is

What GEN Hubs is

Hubs are the personal layer of GEN: every owner and every employee gets a role-scoped hub — their tiles, their records, their calendar, their number, their vault — over the same governed data the company runs on. A hub is not a separate database; it is a view, scoped by the permission matrix and verified per action. People can hold several roles across several companies; each hub shows exactly what that role may see and do.

How it works

A person is registered and issued their number, login, and assigned phone number.

Their hub is generated from their role: owner, operator, employee, or bench member.

Tiles appear by permission: pipelines, calendar, vault, dashboards, communications.

Actions are verified per action — membership in a company never silently grants another company's data.

When roles change, the hub changes with them; nothing lingers.

The details

Owner hubs come before employee hubs in every rollout — oversight first, then the team.
One person, many hubs: roles across companies stay separated by scope, not by separate logins to memorize.
The parent's hub is the oversight hub: aggregate views and the snapshot, never a master key.
Hubs are where the system's discipline becomes personal: my queue, my next actions, my stale records.
Every hub action is attributable — the audit trail names the person and the hub.

Set up