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 installationEngagement · Maintenance vendorQM-MAINT-26Made-up clientSimulated
Quillmark Publishing and Northlight AV
In force · 2 sites shared · 1 job openchecked just now
- 2Sites in scope
- 1Jobs open
- 0Past target
- 275Days left
The scope
Sites
- Denver head office
- Seattle studio
What flows
- Offices and spaces in scope
- Jobs handed to the provider
- Visit readiness
Northlight AV sees a record of Quillmark Publishing's only when it sits inside this scope, and work only when it was handed to Northlight AV. Quillmark Publishing sets the scope; ask your contact to change it.
Activity
signed, and held in both audit logs- Quillmark Publishing · Handed QM-1142 to Northlight AV: podcast studio mixer humsSigned by Quillmark Publishing · in both audit logs
- Northlight AV · Closed QM-1139 with the fix and a photo of the panelSigned by Northlight AV · in both audit logs
- Quillmark Publishing · Engagement signed by both sidesSigned by Quillmark Publishing · in both audit logs
Standards
Quillmark Publishing's standards apply to everything you do for Quillmark Publishing. You can offer Northlight AV's own as a template: Quillmark Publishing decides whether to adopt any of it.
How the two Keias connect
Northlight AV runs Keia in database mode: it shares and receives over the API and events, each one signed.
Quillmark Publishing 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.
No shared database: each side keeps its own Keia and its own copy.
A provider's own Keia
This is Northlight AV's side of the engagement
Only Northlight AV's people see their own Keia. Quillmark Publishing is a made-up client of Northlight AV; Aigna never sees it.