Platform
One Foundation. Multiple Possibilities.
ALINEA connects the everyday work of an organization, from operations and people to documents, customers and public presence, through a shared foundation and modular applications. This page explains how the pieces are meant to fit together.
The idea
Define the organization once. Let every application work from the same understanding of it.
What the platform connects
Six areas of organizational work
Business operations
Customers, projects, quotations, orders and delivery, seen as one flow instead of separate lists.
Organizational management
Structure, roles, departments, branches and the permissions that follow from them.
People and administrative workflows
Employees, attendance, leave, students, classes and the routine requests that move between people.
Customer-facing digital presence
Public websites and inquiry channels that feed the same records the team works from.
Documents, approvals and reporting
Files attached to the work they belong to, decisions with a visible trail, and reports built from shared records.
Future integrations
Connections to accounting systems, payment services, messaging and other tools, added deliberately and described publicly only when verified.
Architecture
Foundation and applications
The foundation provides what every organization needs, whatever its sector. Applications provide what a particular kind of work needs. Keeping the two separate is what allows modules to be added without disturbing the rest.
The foundation provides
- Organization and workspace structure
- Users, roles and permissions
- Shared records for people, customers and documents
- Notifications and activity history
- Reporting that spans modules
Applications provide
- Domain workflows such as payroll, attendance, invoicing or stock
- Screens and forms designed for each kind of user
- Rules specific to a type of organization
- Reports for the work they cover
Following the work
How information moves between modules
The value of a shared foundation appears when work crosses a boundary. Consider a purchase request raised by a site supervisor.
- 01
Raised
The supervisor submits a request from a project in ALINEA Business.
- 02
Routed
ALINEA Workflow sends it to the manager, then to finance, following the organization’s rules.
- 03
Recorded
The decision is logged with who approved it and when, attached to the project.
- 04
Reflected
ALINEA Finance sees the commitment against the project budget, and ALINEA Inventory expects the delivery.
Illustrative scenario of how the modules are intended to cooperate.
Workspaces and roles
One platform, different views
Every organization has its own workspace. Within it, access follows responsibility, so the same platform presents different work to different people.
| Role | Typically sees |
|---|---|
| Owner or director | Organization-wide overview, reports and approvals. |
| Department manager | Their team’s work, requests and results. |
| Finance officer | Transactions, invoices, budgets and statements. |
| Teacher or field staff | Only the classes, tasks or projects assigned to them. |
Illustrative example
Looking ahead
Designed to connect outward
Organizations rarely start from nothing. They have accounting tools, payment providers, messaging channels and older systems that still matter. The architecture is intended to accommodate connections to these over time. Each integration will be scoped, built and verified with the organizations that need it, and described publicly only when it is ready.
Design principles
Private by default
Workspaces are separate from one another, and access is granted rather than assumed.
Traceable decisions
Approvals and changes leave a visible record of who did what, and when.
Records stay with the organization
Data belongs to the organization that creates it.
Tell us how your organization works.
Describe your processes, your tools and the friction you want to remove. We welcome conversations about use cases, digital infrastructure and future collaboration.