Skip to main content
Essal ships six purpose-built apps, each targeting a distinct operational domain. They are not standalone products — they share a unified authentication layer, a common data model, and a single event bus, so data flows naturally between them.

​
The Six Apps

Office

Create and collaboratively edit documents, spreadsheets, and presentations. Files are versioned, exportable, and linkable from any other app.

Access

The identity backbone of the platform. Manages users, groups, SSO connections, and directory sync. All other apps delegate authentication to Access.

Sales

CRM capabilities including contact management, deal pipelines, and activity feeds. Contacts can be linked to Careers applicants or Project stakeholders.

Careers

End-to-end applicant tracking. Post jobs, collect applications, run scorecards, and move candidates through configurable hiring stages.

Project

Task management with sprints, boards, priorities, and time tracking. Projects can reference Sales deals and attach Office documents.

Guard

Security policy management, audit logging, and threat detection. Guard enforces access control across all five other apps.

​
How Apps Share Data

Apps communicate through the Essal Core API — a shared layer that resolves cross-app entity references. For example:
  • A Project task can reference a Sales deal as its business context
  • A Careers applicant can be promoted to an Access user on hire
  • An Office document can be attached to a Project task or a Sales contact
Cross-app links are represented as typed references in API payloads:

​
Enabling and Disabling Apps

Workspace admins can enable or disable individual apps from Settings → Apps. Disabling an app hides it from the dashboard and removes its API surface from your workspace, but does not delete underlying data.
Disabling an app that other apps depend on (e.g. Access) requires migrating linked data first. The API will return a dependency_conflict error if you attempt to disable a prerequisite app.