VNCdirectory

VNCdirectory is the control layer of the suite. It answers two questions for every product: who exists and what may they use. Tenants, organizational units, persons, seats, external parties, product entitlements and access grants all live here, and every other product projects what the directory publishes instead of keeping its own copy.

That is the architectural decision that makes the suite a suite. There is one identity, one org structure, one entitlement decision and one grant store. A user is disabled once and loses access everywhere. A product is removed once and its tile disappears from the portal.

What it delivers

One system of record for people and access. No product maintains a second user list, and no employee exists twice.
An organizational structure that means something. Units nest from company to team, and products inherit down the subtree — assign once at the top and every unit below has it unless overridden.
Seats as a lifecycle, not a boolean. Active, suspended and retained are distinct stages, so a departure can revoke a seat without deleting the record.
Deny by default. Access is opened only by an explicit grant, and the grant store is here, so every product’s sharing writes to the same place.
Auditability. Grants, changes and administration carry an audit trail.
External parties in parallel trees. Customers, partners and suppliers are modelled separately and referenced by identity, never duplicated.

Main capabilities

Capability	What it gives you
Tenants	Isolated organizations with their own directory.
Org units	A nested tree — company, region, branch, team — with divisions and departments.
Persons	Identity records with placements (primary and secondary) and memberships.
Seats	Active, suspended and retained lifecycles, with reactivate and retain.
External parties	Customers, partners and suppliers in parallel trees, referenced by identity.
Products and entitlements	Products assigned to units and inherited down the subtree.
Access grants	The single grant store, with grantee, resource, effect and expiry.
Roles	Roles and role templates per unit and person.
Guided setup	A guided path from an empty tenant to org, people, roles and access defaults.
Users console	Every person in the tenant in one console.
Usage and billing	A flat per-seat price plus metered functions.
Works with existing identity infrastructure	The suite’s identity provider, secrets management and directory services are managed from here.

Typical use

An administrator runs the guided org setup for a new tenant: units, people, roles and products, in one flow.
A new employee is created once; a mailbox, calendar, address book and file space are available at first sign-in because the products project the directory.
A product is entitled at the company unit and inherits to every team below; one team is then excluded explicitly.
A colleague shares a file in VNCfiles; the resulting grant appears in the directory’s Access tab, where it can be reviewed and revoked.
A departing employee’s seat is suspended, then retained for the audit record without consuming a seat.

How it fits the suite

VNCportal asks the directory which products a user is entitled to and shows those tiles.
Every product projects persons, units, roles and access from here instead of owning them.
VNCcontacts shows the organization read-only from the directory and owns only external contacts.
VNCfluid uses directory members for workspaces.
VNCcrm and VNCprm reference external parties by identity.
VNClagoon AI resolves the caller’s identity and policy from here.

Roles

Role	What they do
Directory administrator	Tenants, units, persons, seats, products and grants.
Unit lead	Manage the members and access of their own unit.
Security / audit	Review grants, changes and the audit trail.
End user	See the org structure and the people they may reach.