Live as packaged installs today Automotive Dealer groups A rooftop already runs a supplier feed, a payment provider and a handful of systems nobody else has heard of. Here is where each one lands. Inventory feeds in File drop or direct pull, with field mapping — so the supplier feed a dealer already has keeps working unchanged. Two rooftops never collide The identity key is DealerCode|VIN, not VIN. Keyed on VIN alone, two stores overwrite each other’s price and photos on every sync. Payments as placed modules CarJiffy, placed on the vehicle page from the admin. With no checkout configured the buy control isn’t rendered at all, the page falls back to a native enquiry form, so it fails to an enquiry, not a broken button. The systems a rooftop already runs Anything in-house connects through the module contract below: an entity, a controller, a UI file, a manifest. It becomes a peer of everything else on the site.
Live as packaged installs today Public sector Authorities and agencies The documents, calendars and reports already live in Microsoft’s stack. The job is to reach them from the public site and the staff portal without moving them. Documents where they already are SharePoint and OneDrive, placed as modules; the file stays in the tenancy, the page reads from it. Bookings, calendars and signature Microsoft 365 Bookings and Calendar for appointments; DocuSign where a signature closes the process. Reporting in public Power BI Embed puts a report on a public page. Power BI Query reads from one where a page needs the figures rather than the chart. One login for staff and residents Portals for staff and the public on one identity and one permission set and training for employees and the public from the same module and data model.
Live as packaged installs today Automotive Dealer groups A rooftop already runs a supplier feed, a payment provider and a handful of systems nobody else has heard of. Here is where each one lands. Inventory feeds in File drop or direct pull, with field mapping — so the supplier feed a dealer already has keeps working unchanged. Two rooftops never collide The identity key is DealerCode|VIN, not VIN. Keyed on VIN alone, two stores overwrite each other’s price and photos on every sync. Payments as placed modules CarJiffy, placed on the vehicle page from the admin. With no checkout configured the buy control isn’t rendered at all, the page falls back to a native enquiry form, so it fails to an enquiry, not a broken button. The systems a rooftop already runs Anything in-house connects through the module contract below: an entity, a controller, a UI file, a manifest. It becomes a peer of everything else on the site.
Live as packaged installs today Public sector Authorities and agencies The documents, calendars and reports already live in Microsoft’s stack. The job is to reach them from the public site and the staff portal without moving them. Documents where they already are SharePoint and OneDrive, placed as modules; the file stays in the tenancy, the page reads from it. Bookings, calendars and signature Microsoft 365 Bookings and Calendar for appointments; DocuSign where a signature closes the process. Reporting in public Power BI Embed puts a report on a public page. Power BI Query reads from one where a page needs the figures rather than the chart. One login for staff and residents Portals for staff and the public on one identity and one permission set and training for employees and the public from the same module and data model.