VNCfluid

VNCfluid is the shell of the suite. It does not replace any product; it puts them on one board. Instead of opening an application, finding the project, and then opening the file, a user arranges the things they work with as portlets — a living view of a product, not a screenshot or a link — and moves between them without changing context.

The shell replaces the old pattern of a portal made of embedded iframes. A portlet is a real application surface, bound to a real object (this project, this channel, this board), and it stays live while the user works elsewhere on the board.

What it delivers

One workspace instead of many tabs. A user composes a board out of the tools and objects they need, and returns to it exactly as they left it.
An arrangement you own. Portlets can be dragged, resized and grouped into Spaces — named tabs such as My day, Project X or Support.
One session across the suite. Signing in once is enough; a portlet opens the product already signed in.
Personal spaces and shared workspaces. More than a private dashboard: a team can have a shared workspace with members, a scoped set of apps and a group chat, with one layout for everyone.
A single entry point for the day. A start page that shows what matters now — not a launcher list.

Main capabilities

Capability	What it gives you
Portlets	Each product as a live tile bound to a concrete object.
Grid and layout	Drag, resize and group portlets; the layout is saved per user and roams across devices.
Spaces	Named tabs that group a particular kind of work.
Space templates	Administrators publish a template per role or team; a user starts from it.
Workspaces	A shared area with members, start and end dates, a scoped set of apps and an automatic group chat named after the workspace.
Shared layout	The workspace layout is shared across members; the owner and moderators edit it.
Omnibar and composer	Compose a message or ask for an object from one input, with template chips.
App rail	The products available to the user, with display names configured for the organization.
Cross-product events	Unread counts and search span the suite instead of stopping at one product.
Cell-specific naming	The rail, catalog and wordmark use the names configured for the organization.

Typical use

An employee opens a personal Space in the morning: today’s calendar, unread mail, the tasks due and the project board, all at a glance.
A project team works in a Workspace: the project, its files, its board and its channel are bound to one area, the layout is shared, and the group chat is created with it.
A salesperson builds a Space per customer with the CRM record, the latest mails and the shared folder.
An administrator publishes a template for new hires so their first board is not empty.

How it fits the suite

VNCportal is the entry point with the app launcher; VNCfluid is the working surface after that.
VNCdirectory supplies identity, members and access for workspaces.
Every product in the suite can appear as a portlet: chat, channels, mail, calendar, contacts, CRM, tasks, projects, files, boards, workflow.
VNCchat is provisioned automatically for a workspace’s group chat.

Roles

Role	What they do
End user	Arrange personal Spaces and use portlets.
Workspace owner	Create a workspace, choose apps, manage members and layout.
Administrator	Curate the catalog, publish Space templates, set the org’s product names.