People remember the image, not its path
Marketing may know that the spring launch lives three folders below “Campaigns”, while a salesperson only remembers the product, the colour and the image they saw last week.
A separate home for approved marketing media
Briefs, spreadsheets and collaborative work can stay in the tools your colleagues already know. Freedam can take over the approved media layer, so a salesperson can find the current product shot and an agency can collect the campaign files without learning the company folder tree.
Freedam takes the approved media layer only. Documents, sites and teamwork stay in SharePoint, and there is no native SharePoint connector yet, so the first move is sized around one campaign.
Nordi brand center
SharePointTwo kinds of work in the same organisation
This is less a verdict on SharePoint than a question of fit. A platform designed for documents, sites and teamwork asks different things of its users than a visual library for people who simply need the right image or campaign file.
Marketing may know that the spring launch lives three folders below “Campaigns”, while a salesperson only remembers the product, the colour and the image they saw last week.
A real campaign set may include video, RAW photographs, PDFs and layered design files alongside the documents SharePoint previews comfortably.
Updating the source does not automatically recall the brochure already sent through Teams, attached to email or saved in a regional folder.
An agency or dealer looking for three approved images may not need the navigation, identity and collaboration model used by internal SharePoint users.
A clear hand-off between the two
A change with a contained scope
Teams keep briefs, drafts, spreadsheets and supporting documents in the SharePoint workflow they already use together.
Once approved, the useful images, video, design files and collateral enter Freedam with the product details, status, rights and versions people will need later.
Marketing prepares a collection, protected share or public page that gives each audience a clear and recognisable route into the material.
Teams and partners have somewhere to return when a version changes, rather than relying only on the campaign ZIP they saved locally.
Working side by side
SharePoint collaboration
Freedam governed asset
Teams, agencies, and partners
A practical first move
Direct upload and supported source routes make it possible to test the new hand-off without planning a company-wide migration first. Freedam does not currently offer a native SharePoint connector, so the initial move should be sized around the material your team can comfortably bring across and maintain.
1. Choose the current set
Start with the images and campaign files still used in one product line or market, rather than copying every historical folder before anyone has tried the new routine.
2. Describe how people look for it
Add the product, campaign, rights, status and audience details people already mention when they ask marketing to find something.
3. Invite the real audience
Ask a few colleagues or partners to try search, an external portal or share, download choices and a version update before widening the scope.
A useful conversation with IT
Microsoft and Google SSO, workspace roles, user groups, and asset access rules cover different signed-in access patterns.
Public Portal access is read-only and enforced server-side; originals remain unavailable unless a guest rule explicitly grants them.
Versions, workflow transitions, rights events, shares, views, and downloads have their own histories or analytics surfaces.

Questions buyers ask
No. The practical boundary is marketing assets. Keep company documents, intranet content, records, Teams collaboration, and Microsoft 365 working files in SharePoint. Move approved images, video, design files, and campaign materials into a purpose-built asset layer.
Instead of navigating a tenant or waiting for a ZIP archive, external audiences can use public collections, a public read-only portal, controlled share links, or signed-in access according to the audience and asset policy.
Files can be uploaded directly or synchronized from supported Google Drive, WebDAV, and S3-compatible sources. Folder mapping, collection assignment, catalog metadata, sample runs, and dry runs provide a controlled path into the library.
Stay when the library is small, mainly document-based, rarely shared externally, and easy for the team to govern with existing Microsoft 365 skills. A switch should solve a recurring media workflow, not merely add another repository.
Continue exploring
Whether you are trying to improve the library you already have or considering a separate home for marketing media, these pages take the next step in the discussion.
Explore a small, realistic hand-off
The demo lets you look at search, rights, versions, collections and external access in Freedam while keeping the parts of SharePoint that already serve your organisation well.