Purpose & responsibilities
Office administration and assigned company or branch services.
Office administration and assigned company or branch services.
Office administration and assigned company or branch services.
The application name and intended workspace are listed here. Its live URL, installation file, supported platforms and version information will be connected after the actual release files are supplied and checked.
Release pending · No download available
Access remains restricted to the assigned company, branch and responsibilities. A role name does not grant access to all records.
Browse all applications →Explore the departments and handoffs that match your operation, then prepare a product enquiry around your company structure.
Coordinate office records and requests, with clear ownership between the company and its departments.
Explore module →In developmentLet the Customer Super Admin manage each company identity separately: logo, business name, contacts and company-specific email setup.
Explore module →Planned expansionKeep business documents, templates, versions and approvals inside the departments and workflows that require them.
Explore module →Supplied map: PartialGive employees an internal company inbox for direct and department messages, with controlled attachments and personal read status.
Explore module →Source present · live validation pendingOrganize company chat in member-controlled threads, with incremental message polling and personal read cursors.
Explore module →Source present · live validation pendingControl the lifecycle of Office Mail attachments through private storage, retention review, legal holds and company storage limits.
Explore module →Source present · live validation pendingCapabilities remain subject to assigned rights. Source presence does not establish a released mobile app.
Previously documented product scope; release availability is assessed separately.
Previously documented product scope; release availability is assessed separately.
Previously documented product scope; release availability is assessed separately.
Previously documented product scope; release availability is assessed separately.
Company administrators can manage internal-mail departments and active members. Only permitted members can send department mail.
Direct and department messages, private attachments and personal notifications connect to the dedicated Office Mail workspace.
Customer Super Admin manages the identity for each company separately; completed implementation is not established here.
Use company-specific incoming/outgoing identity and the authorized company-mail setup.
Authorize branding changes for the selected company, maintain change history and clear stale context when switching companies.
Limit document categories and access to the departments that need them.
Use authorized file handling for the linked business record.
Provide a print/PDF option where the specific document type supports it.
Enable the right templates for the relevant department and workflow.
Retain the document version associated with an approval or change.
Route the chosen version to assigned reviewers.
Track sensitive document access and lifecycle actions.
Find authorized files by their record and metadata.
Export permitted document-list metadata when the workflow requires it.
Attach supported documents contextually; no universal document menu or format grant.
Private Office Mail attachment storage, hold/review and recovery workflows are documented in their own modules. They do not implement versioning or governance for every Document Center record.
Company-scoped employee-to-employee messages, message detail, sent history and personal archive are present in source. Recipients are company users, not public email addresses.
An active department member can send to up to 100 other active members. Department delivery is recorded as one database transaction.
Internal notices identify new messages and uploaded attachments. Users can mark only their own notices read; this does not establish mobile push delivery.
Sender upload supports PDF, PNG, JPEG and plain text up to 5 MiB. Private storage, randomized keys, SHA-256 checks and authorized downloads are in source.
Retention previews, legal holds, configured company quotas and independent cleanup review connect to the dedicated governance workspace.
Office Mail stays inside the company database. It does not use SMTP/IMAP or create a company-domain mailbox.
Thread creation, membership checks and text message records are present in the cumulative communications source.
Thread participation and company identity determine which messages an authenticated user can access.
Fetch up to 100 messages newer than the caller cursor from threads they belong to. Polling is distinct from WebSockets or background push.
A thread member can advance their own read position. This is not a delivery confirmation or a read receipt for every participant.
Realtime push, voice/video transport and mobile background delivery require separate infrastructure and validation.
Review attachment usage and recovery-reference inventory inside the authorized company.
Configure no expiry or a 30–3650 day retention period and inspect bounded expiration candidates without deleting files.
Record a reason for legal hold and authorized release. Held attachments are excluded from cleanup previews and approval.
Quota checks use a locked company record during uploads. Companies without a configured quota remain unlimited.
A requester cannot approve their own cleanup request. Approval records a review only; it does not delete a file.
Record backup references and connect them to independent backup verification. A reference alone does not prove a recoverable backup.
Allowed uploads and downloads use company checks, randomized storage keys and SHA-256 verification.
The cleanup worker remains preview-only. Destructive cleanup and actual antivirus/content scanning are not implemented.