Who can enter a workspace?
Alignis uses authenticated sessions for workspace access. Public pages, sign-in and password reset routes remain separate from protected application routes.
AlignisSecurity and control
Performance records need controlled access and traceable actions.
Alignis is built around authenticated workspace access, organisation-scoped records, role-aware workflows and auditability. Contractual security requirements are reviewed as part of implementation and procurement.
Who can see and act on records?
Application navigation and workflow access are shaped by assigned workspace roles, including administrators, leaders, supervisors and staff users.
How are organisations separated?
Performance records are tied to the organisation tenant, its users, units, staff placement and reporting structure.
How are public and workspace areas separated?
Authenticated application areas are separated from the public site and guarded by server-side user context checks.
Which actions can be reviewed?
Administrative and workflow actions use audit services so important changes can be reviewed by authorised users.
What browser protections are configured?
The application config includes browser security headers such as content type protection, frame restrictions and a content security policy.
Security review
What buyers should ask during procurement.
Review the roles that will access Alignis, the organisation structure to be configured, the records that need approval, and the internal administrators responsible for setup and support.
Customer-specific data processing, service and security requirements are reviewed during procurement and recorded in the applicable agreements and implementation scope.
Discuss control requirements
Include your IT and security reviewers in the walkthrough.
We can walk through workspace roles, organisation scope, record routing, audit history and implementation responsibilities.