Client management workspace with contact records, notes, files, portal access, account health, and dedicated client communication.
Lyniti Clients Hub keeps relationship data, communication, and supporting files together so teams do not have to rebuild client context across multiple systems. It is useful for teams that need both operational records and active client follow-up in one place.
| Capability | Details |
|---|---|
| Client list with search and filters | Clients view supports search plus status filtering so teams can review active, prospect, inactive, churned, and on-hold accounts fast. |
| Priority and health tracking | Each client carries priority, status, and health score fields, making it easier to spot important relationships and at-risk accounts. |
| Client notes and detail records | Client detail page stores contact details, notes, relationship metadata, and editable profile data in one place. |
| Client files and secure portal access | Each client can have dedicated file area plus portal invite flow so shared documents and client-facing access stay organized. |
| Embedded client chat | Client detail page connects with client-specific chat, and main client list surfaces unread counts from those conversations. |
A client portal gives an external client a dedicated way to access shared work without exposing the full internal workspace. Lyniti connects portal access to the client record so files and communication remain attached to the relationship the team already manages.
Portal access begins through a client invite flow. The current product does not claim white-label branding, e-signatures, or a configurable client permission matrix.
Client records can connect to a dedicated file root where teams organize folders, upload material, preview files, and keep shared documents close to client context. This reduces the need to maintain a separate drive structure for every account.
Client-specific chat stays connected to the client detail page. Unread counts surface in the client list so follow-up work remains visible instead of disappearing into a separate inbox.
Internal teams can keep contact information, notes, relationship data, status, priority, and health score in one client record. Search and filters help teams review active, prospect, inactive, churned, and on-hold relationships.
Clients Hub is most useful when portal files and communication sit beside project tasks, approvals, meetings, and invoices. The shared context helps service teams move from client request to delivery and billing without rebuilding the account story across tools.
Clients Hub stores client details, notes, status, priority, health score, file areas, portal access, and client-specific chat.
Yes. Each client can have a dedicated file area, plus portal invite flow for client-facing access.
Yes. Client detail pages connect to client-specific chat, and unread counts surface in the main clients list.
A workspace member can generate a client portal invite and share the resulting access link with the client.
No white-label portal or e-signature capability is claimed. Current portal workflow focuses on client access, files, and connected communication.
Give clients portal access to files and communication while teams manage profiles, notes, health, priority, and status.