Purpose & responsibilities
Access own requests, employee information and published payslips.
Access own requests, employee information and published payslips.
Access own requests, employee information and published payslips.
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.
Give employees a clear place to view their own information, request leave and receive published payslips.
Explore module →Planned expansionExplain role-based mobile work, manager approvals, notifications and the roadmap for supported API/provider connections.
Explore module →Supplied map: PlannedGive 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 pendingCapabilities remain subject to assigned rights. Source presence does not establish a released mobile app.
Adapt authorized workspaces to supported screen sizes.
Prioritize tasks and forms relevant to mobile users.
Provide employee-specific requests and published information.
Expose only assigned approval work with applicable limits.
Plan configured delivery channels and permission-aware routing.
Publish supported authorized integration interfaces as they are implemented.
Connect authorized providers and retain source/update context.
Deliver configured business messages through approved providers.
Build and release role applications separately for their target platforms.
Connect assigned rider, sales, collection and supervisor tasks.
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.