Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Vendors is switched off
The companies that install and repair, and who looks after each. This demo has the Vendors module switched off in Organisation settings.
Engagement · Integrator for a projectAG-INT-2025-04Simulated
Aigna and Northlight AV
In force · 4 sites and 1 project shared · 3 jobs open, 1 past targetchecked just now
- 4Sites in scope
- 3Jobs open
- 1Past target
- 184Days left
The scope
Sites
- New York office
- Chicago office
- Toronto office
- Juneau office
Projects
- PRJ-14 · Juneau office fit-out
What flows
- Offices and spaces in scope
- Jobs handed to the provider
- Visit readiness
- As-builts
- Handovers
- Design proposals
Northlight AV sees a record of Aigna's only when it sits inside this scope, and work only when it was handed to Northlight AV. Change the scope and the next record follows the new one.
Activity
signed, and held in both audit logs- Northlight AV · Marked Tuesday's Chicago survey ready: access booked, kit packedSigned by Northlight AV · in both audit logs
- Aigna · TASK-14-2-03 now waiting on switch ports: the clock paused for both sidesSigned by Aigna · in both audit logs
- Aigna · Handed TASK-14-2-03 to Northlight AV: record serials and MACs, 2.03Signed by Aigna · in both audit logs
- Aigna · Handed SURV-0412 to Northlight AV: survey before the 12.09 refitSigned by Aigna · in both audit logs
- Aigna · Handed SNAG-14-02 to Northlight AV: reframe the camera in 2.02Signed by Aigna · in both audit logs
- Northlight AV · Sent the as-built for 2.05; it landed in Aigna's record as a reviewed change, accepted by MarcusSigned by Northlight AV · in both audit logs
- Aigna · Engagement signed by both sides, with the data processing agreementSigned by Aigna · in both audit logs
Revoke
Stops the flow at once: Northlight AV receives nothing new and can send nothing back. Each side keeps its copy of what was shared before, and the revoke is written in both audit logs.
Revoked just now (simulated). Nothing flows; each side keeps its copy.
How the two Keias connect
Aigna runs Keia in repo mode: what it shares leaves as a signed export, and what Northlight AV sends back arrives as a pull request a person reviews.
Northlight AV runs Keia in database mode: it shares and receives over the API and events, each one signed.
No shared database: each side keeps its own Keia and its own copy.