Preserve the source reference
A linked record identifies its origin so a reviewer can return to the material behind the assessment.
Use the records your teams already maintain.
Lexa connects compliance reviews to documents and operational activity. Agree the source systems, data required and permissions before introducing a connection.
CONNECTION OPTIONS
Documents, work records and data feeds.
| Source | Typical use | Connection scope |
|---|---|---|
| Microsoft 365 and SharePoint | Policies, review documents and supporting files | Document metadata, source links and agreed records |
| Jira and ServiceNow | Implementation and remediation activity | Issue references, assigned owners and progress |
| Structured file imports | Existing registers and historical records | Field mapping, validation and exception review |
| APIs and agreed data feeds | Other operational and reporting systems | Defined fields, access permissions and refresh arrangements |
Connector availability, permissions, synchronisation frequency and any custom work are confirmed in your implementation proposal. Source-system licences are separate.
Control the access
Start with the information required for the use case. Read-only access is the default proposal where writing to the source is unnecessary.
Review data quality
Validate imported fields and surface missing information or failed updates for investigation. Connection does not imply that a record has been accepted as sufficient.
IMPLEMENTATION
Start with a manageable
set of records.
An initial deployment can use a structured register and selected document sources. Further connections can follow once ownership, review arrangements and data quality are established.
The implementation scope sets out which system owns each record, how updates are handled and who resolves an exception.
Implementation approach