Platform Services Overview
QTO ERP includes the main user-facing modules shown in the application shell, plus shared services used across those modules.
These services support access control, organization data, user profiles, notifications, file storage, analytics, configuration, backups, AI provider configuration, website content, and personal todos.
Verified services
Section titled “Verified services”| Service area | Implemented app | What it supports |
|---|---|---|
| Accounts and access | accounts |
Login, logout, token refresh, user list, current-user permissions, activity logs, and LDAP sync tools. |
| Organization | organization |
Organizations, offices, departments, designations, employees, employee ID format settings, teams, memberships, groups, permissions, and employee error reports. |
| Profiles | profiles |
User profile, education, work experience, certifications, location dropdowns, completion status, and application auto-fill data. |
| Deep permissions | deep_permissions |
Dynamic apps, pages, sections, fields, buttons, highlights, filters, columns, row actions, data scopes, and user overrides. |
| Notifications and email | pulse |
Notifications, preferences, email groups, email templates, email logs, mail keywords, push notification registration, and error monitoring. |
| Files | file_manager |
Folders, files, upload, sharing permissions, public link access, and storage statistics. |
| Todos | todos |
Personal todos, subtasks, labels, reminders, bulk actions, archive state, completion state, and productivity summary. |
| Analytics | analytics |
Attendance, leave, team, organization, and CRM analytics endpoints used by dashboards and reports. |
| Website and CMS | website |
Wagtail CMS, documents, public API, events, announcements, policies, memories, team pages, contact pages, polls, and feedback. |
| System configuration | project_config |
Email, storage, encryption, log retention, geodata, Sentry, push notification, currency, and LDAP settings. |
| AI Core | ai_core |
AI provider configuration, prompt templates, inference endpoints, request logs, response cache, and connection testing. |
| Backup and federation | backup_manager, federation |
Backup records/configuration/restore/downloads and federated file/server/share workflows. |
How these services appear to users
Section titled “How these services appear to users”Some services appear through module pages. For example:
- File storage is used by profile documents, Careers attachments, and project files.
- Pulse templates and notifications support Careers emails, reminders, and system alerts.
- Organization records drive Attendance, Payroll, Careers, Project Management, and permissions.
- Analytics endpoints feed dashboards and reports.
- Deep permissions decide which navigation items, fields, buttons, and records a user can see.
Other services are administrator or operator tools and may be visible only through admin pages or internal configuration screens.
Confirmation-needed areas
Section titled “Confirmation-needed areas”The codebase includes several implemented backend services whose final user-facing placement is not fully visible from the current React shell. Dedicated end-user pages should be added only after product confirms where those tools are exposed in production.