CMP Suite brings an organization’s collaboration services into a coherent workspace: email, calendar, files, contacts, tasks and approvals. Users work with the information they need while administrators control membership, access and service configuration. Personal workspaces and organizations remain separate contexts, even for the same person.
Connect IMAP/SMTP accounts, browse provider folders and track read status and flags. References and message identifiers preserve the relationship between replies. Drafts and the outbox separate writing from submission; attachments can continue their journey in Files. Updates use server synchronization and recovery mechanisms according to the installation configuration.
Personal and shared calendars organize meetings by time range, time zone, location and availability. Participants belong to an event; access to a shared calendar does not imply permission to modify its owner’s meetings. Planning can start from a conversation and continue with the documents needed for the meeting.
Upload and download files in the workspace where you work. Metadata preserves the name, type, size and source; storage limits protect account capacity. Shared links can be controlled through expiry, passwords and revocation. A saved attachment becomes a managed resource separate from its original message.
The directory presents active workspace members together with their configured role and department. Personal contacts retain addresses, phone numbers, companies and notes. Internal membership and external people are separate concepts, so an email address does not automatically confer organization access.
Tasks preserve descriptions, priorities, deadlines and progress. Approvals identify the requester and the designated decision maker; a decision closes or continues work according to the applicable workflow. Users can track their actions without turning every email exchange into an informal list of obligations.
Knowledge pages retain instructions and decisions. Spaces organize collaboration, lists structure records, and forms collect information through defined fields. These resources provide a common entry point for repeated work; access is determined in the context of the organization and the resource.
Language, time zone, theme and accessibility preferences adapt the working experience. Account Center brings profiles, sessions, devices, security and privacy requests together. Notifications identify relevant changes; the visibility of their data follows the permissions of the active context.
A request arrives in Mail. Its owner reads the conversation, saves the relevant document in Files, schedules a meeting in Calendar and tracks the next action in a task. When a decision is needed, an approval names the responsible person. The outcome can be documented in Knowledge so the team can find it later.
Members work with their own and shared resources. Managers track requests and decisions within their permitted area. Administrators manage the organization, members, enabled products and service integration. A mailbox owner can delegate distinct rights; reading and sending must not be confused with account administration.
Switching organizations changes the available resources. Active membership is checked on the server, rather than inferred from a visual selector. A file or message identifier from another workspace does not constitute authorization. This separation supports people working with several companies without mixing their information.
Web and mobile sessions are managed and can be revoked. Modification requests are validated on the server; the web application uses CSRF protection. Email HTML is sanitized and transport secrets are protected in storage. Technical measures do not replace correct configuration, restoration checks or the operator’s access policy.
Trust Center →Privacy policy →Suite provides working context for documents, people, messages and actions. Specialized products have their own permissions and licenses; enabling them does not automatically open all organization data. An integration must define the resource, exchange direction and responsible person to avoid duplicate documents and records.
The /api/v1 API exposes verified resources in the user and organization context. OpenAPI describes the contract, and request identifiers support diagnostic correlation. Incremental synchronization and record versions support mobile updates and conflict detection. Integrating a client does not bypass the platform’s access rules.
Shared foundation →The web interface adapts to small screens; the Android app uses the same core resources. Local caches and offline operations require reconciliation when connectivity returns. Device registration and push complement synchronization; notification delivery depends on the configured service and operating system restrictions.
The operator configures SMTP, IMAP, scheduled jobs and notification providers. Queues, retries and diagnostics distinguish an accepted request from a submission confirmed by its transport. Schema Health checks and applies database updates. Backups must include the database and files, and restoration must be verified.
A document, conversation and decision can be followed in the same working context. Members find the responsible person more easily, while administrators identify services and sessions requiring attention. The intended benefit is continuity: information needed for the next stage remains available to authorized people.
Licensing defines the contracted products, organizations, services and limits. CMP Suite can be discussed separately from specialized modules or alongside them. Advanced functions of modules still under development must be explicitly included in project assessment; an ecosystem presentation does not promise that every extension is already available.
Yes, connections use the account’s IMAP and SMTP settings. A provider may require an application password, enabled access or special rules. Configuration and transport testing must confirm access before use; Suite does not automatically change the provider’s policy.
The user selects the working context. The server checks membership and permissions for that workspace. Organization resources do not become one combined list simply because the person uses the same sign-in account.
There is no universal latency guarantee. Message detection, server jobs, the push provider and device operating system influence update timing. Periodic synchronization offers a recovery path when notifications are delayed or a device is offline.
Start with a concrete workflow, the people performing it and existing data sources. A project discussion determines available products, required extensions, providers, migration and acceptance criteria. The contact form submits that request; it does not automatically activate a trial or contract.
Tell us what your organization needs. Discuss CMP or a custom solution.
