SharePoint Consent-Linked Image Library
Budget: $1,500 – $3,000 AUD
I’m looking for a developer who can turn SharePoint Online into a secure image library where every single photo is automatically bound to a verified informed-consent record. The aim is strict compliance and traceability, not public display.
The solution must recognise three role‐based audiences: Administrators, Compliance Officers and Regular Users. Administrators need the ability to manage user roles, audit consent records and approve or revoke access in real time. Compliance Officers must be able to audit those records as well, monitor actual image usage across the site and generate exportable compliance reports. Regular Users simply add, search and use images—but only within the permissions that the linked consent allows.
Core expectations
• When a user uploads an image the system should force a link to an existing consent item or prompt creation of a new one, capturing subject details, permitted uses, expiry and revocation status.
• Before a file is opened, downloaded or shared the library must check that the attached consent is valid and unrevoked; otherwise access is blocked and logged.
• Every view, edit, download or share event has to be written to an immutable audit log available to Compliance Officers.
• Consent records must be easy to revoke, expire automatically by date and support full auditing history.
• Standard SharePoint security (versioning, retention labels, no external sharing) should be enforced, and Power Automate / Power BI may be used if they streamline workflows and reporting.
Deliverables
1. Configured SharePoint Online site collection with custom library, lists, metadata and automated consent-validation flows
2. Role-based permission model mapped to the three audiences above
3. Dashboard or report pack showing usage metrics and consent status for Compliance Officers
4. Admin and end-user guides plus commented Power Automate/PowerShell scripts (where used)
5. Short hand-over session to walk through configuration and answer questions
I need clean, maintainable configuration—not a one-off hack—so future admins can extend or modify without code rewrites. If you know your way around SharePoint libraries, metadata, compliance centre tools and Power Platform, I’d love to see how you would tackle this.
The solution must recognise three role‐based audiences: Administrators, Compliance Officers and Regular Users. Administrators need the ability to manage user roles, audit consent records and approve or revoke access in real time. Compliance Officers must be able to audit those records as well, monitor actual image usage across the site and generate exportable compliance reports. Regular Users simply add, search and use images—but only within the permissions that the linked consent allows.
Core expectations
• When a user uploads an image the system should force a link to an existing consent item or prompt creation of a new one, capturing subject details, permitted uses, expiry and revocation status.
• Before a file is opened, downloaded or shared the library must check that the attached consent is valid and unrevoked; otherwise access is blocked and logged.
• Every view, edit, download or share event has to be written to an immutable audit log available to Compliance Officers.
• Consent records must be easy to revoke, expire automatically by date and support full auditing history.
• Standard SharePoint security (versioning, retention labels, no external sharing) should be enforced, and Power Automate / Power BI may be used if they streamline workflows and reporting.
Deliverables
1. Configured SharePoint Online site collection with custom library, lists, metadata and automated consent-validation flows
2. Role-based permission model mapped to the three audiences above
3. Dashboard or report pack showing usage metrics and consent status for Compliance Officers
4. Admin and end-user guides plus commented Power Automate/PowerShell scripts (where used)
5. Short hand-over session to walk through configuration and answer questions
I need clean, maintainable configuration—not a one-off hack—so future admins can extend or modify without code rewrites. If you know your way around SharePoint libraries, metadata, compliance centre tools and Power Platform, I’d love to see how you would tackle this.
Related categories:
PHP
.NET
C# Programming
Sharepoint
Compliance
Data Governance
Power BI
Power Automate