Heritage CommunitiesSenior living · marketingIn tenant

Brand Hub

A brand library where resident photos carry their consent

Logos, photos, video and templates for every community in one place, inside Heritage's own Microsoft 365 and Azure tenancy. Marketing approves what staff can see, and a photo of a resident can only be used while that resident's signed release is active.

EveryDownload re-checks the resident's signed release
0Secrets or certificates in the app registration
0Files shown to staff before marketing approves them

The problem

Brand files for a portfolio of senior living communities lived across shared folders, and the usual fix is to rent a brand portal from a SaaS vendor. But many of the best photos show residents, and each of those needs a signed release. A shared folder or a rented portal can store the photo; it can't know when the release behind it ends, or stop the photo from being downloaded the day after.

What we built

A brand library that runs entirely inside Heritage's own tenant. Files stay in SharePoint. Staff sign in with their existing Microsoft account to browse, preview and download what marketing has approved, by community and by type. Each photo of residents is linked to a signed release, and Brand Hub checks that release again every time the photo is downloaded, previewed or shared. When a release is revoked or expires, a daily job withdraws every photo linked to it and tells marketing.

“Qaswa has built seven platforms for us across finance, marketing, HR and my own office, all running inside our own Azure environment. What stands out is the discipline: every number ties back to the source, and nothing changes in our systems unless one of our people approves it. Every project since the first one, they earned by delivering the last.”

Farhan Khan, CEO, Heritage Communities ·

How a file becomes a brand asset

  1. UploadInto the community's folder in SharePoint
  2. DraftHidden from staff, community already filled in
  3. ReviewMarketing checks it and links the signed release
  4. ApproveA person publishes it
  5. Re-check + auditRelease checked on every use, every use logged

Marketing can also build campaign kits that download in one click, and send an agency or printer a link that expires, can be turned off at any time, and re-checks every resident release each time it's opened.

An assistant on every page

Hearth, the AI assistant, answers questions about the library and the brand guidelines and links every asset it mentions. It never identifies people in photos: marketing finds a resident's photos only through that resident's signed release. When a draft arrives, it can suggest tags and a description from the image, and a person reviews them before anything is saved.

Security and control

  • The app registration holds zero secrets and zero certificates: it signs in as the platform's own managed identity
  • The platform can reach only the SharePoint lists it needs — it writes to the brand library, reads the release register, and can't open the rest of the site
  • Every download, preview and share is checked and logged before the file is sent; if logging is unavailable, the file isn't sent
  • Residents' names stay on the server — staff see whether a photo is cleared, never who is in the release
  • Share links are the only thing that works without a Heritage sign-in, and each one holds a long random key that marketing can revoke
Where the AI runs. Models run as Heritage's own resource inside their tenancy, processed in the United States. Prompts and completions aren't used to train foundation models, and every request is tied to a person signed in through their own identity provider.

Do you know which photos you're still allowed to use?

If your brand files live in shared folders and your consent forms live somewhere else, that gap is the work we close. Tell us about it.

More of our work