Skip to content

VNCportal

VNCportal is where a user starts. It is the central sign-in page and the launcher for the whole suite: one sign-in, then a grid of the products the user is entitled to.

It is deliberately small. The portal holds no business data and no user list of its own — identity comes from the suite’s identity provider, entitlement comes from the directory, and the portal shows what those two allow. Its value is that the user never signs in twice, and never has to remember which address belongs to which product.

  • One sign-in for the suite. The user authenticates once at the portal; every entitled product opens without a second prompt.
  • A launcher that reflects entitlement. Tiles come from the directory. A product the user may not use is marked as no access rather than silently opening an error page.
  • A consistent entry point per organization. The portal and its product addresses are configured for the organization, so there is one address to communicate to users.
  • A thin, auditable layer. No business data lives here, which keeps the security surface and the data-protection scope small.
Capability What it gives you
Central sign-in OpenID Connect with PKCE against the suite’s identity provider.
Single sign-on across the suite After sign-in, each product authenticates the user silently and opens directly.
App launcher A space-toggled grid of product tiles for the whole suite.
Entitlement-aware tiles A tile the user is not entitled to is shown as no access.
Organization branding The portal and product addresses are configured per organization.
Account and sign-out The account menu and a single sign-out that ends the suite session.
Direct product login Products can also be opened directly and handle their own sign-in.
  • An employee opens the organization’s portal address, signs in once, and selects a tile — the product opens already signed in.
  • A new team member sees exactly the products their role entitles them to, and the rest marked as no access.
  • An external partner uses the same portal to reach the partner portal, with only the tiles their relationship allows.
  • An administrator gives users one address to remember instead of a list of product links.
  • VNCdirectory decides entitlement and supplies identity attributes.
  • The suite’s identity provider performs the authentication.
  • Every product trusts the session the portal establishes.
  • VNCfluid takes over as the working surface once the user has chosen where to start.
Role What they do
End user Sign in and open their products.
Administrator Configure the portal address, branding and app registry.
Security Review the sign-in path and the session policy.

Applies to VNClagoon 2026.1 and later. Last reviewed on 19 October 2026.

© 2026 VNC - Virtual Network Consult AG. All rights reserved.