A separate place for approved marketing media

A visual library for your assets, next to SharePoint

Briefs, spreadsheets and shared work can stay in the tools your colleagues already know. Freedam can hold the approved media, so a salesperson can find the current product shot and an agency can collect campaign files without having to learn the company folder structure.

Freedam handles the approved media only. Documents, sites and teamwork stay in SharePoint. There is no native SharePoint connector yet, so it usually makes sense to start with one campaign.

Explore the demo Plans and pricing

Drag the handle to compare the same Nordi files in an internal SharePoint library and a curated brand center.

Two kinds of work in the same organisation

When media can be harder to work with in SharePoint

This is more about fit than about SharePoint itself. A platform built for documents, sites and teamwork asks different things of people than a visual library does for someone who just needs the right image or campaign file.

People remember the image more than the folder

Marketing may know that the spring launch is three folders below “Campaigns”, while a salesperson usually remembers the product, the colour and the image they saw last week.

Many of the files are not Office documents

A campaign set often includes video, RAW photographs, PDFs and layered design files alongside the documents SharePoint previews well.

Copies end up outside the library

Updating the source does not change the brochure already sent through Teams, attached to an email or saved in a regional folder.

Occasional visitors may want something simpler

An agency or dealer looking for three approved images may not need the navigation, sign-in and collaboration setup that internal SharePoint users work with.

Who handles what

Splitting the work between SharePoint and Freedam

What stays in SharePoint

Company documents and records
Briefs, plans, spreadsheets, and working files
SharePoint and Teams collaboration
Intranet and retention workflows where appropriate

What moves to Freedam

Approved product and lifestyle imagery
Video, PDF, RAW, and design files
Campaign materials, logos, and guidelines
Rights, versions, prepared sizes, collections, shares, and portals

A change with a limited scope

Change only the hand-off

01
Create and collaborate
Teams keep briefs, drafts, spreadsheets and supporting documents in SharePoint, where they already work together.
02
Publish approved media
Once approved, the images, video, design files and collateral people need go into Freedam, with the product details, status, rights and versions they will look for later.
03
Set up where people find it
Marketing prepares a collection, protected share or public page, so each audience has a clear place to find the material.
04
Point people to the current files
When a version changes, teams and partners have somewhere to come back to, so they rely less on the campaign ZIP they saved locally.

Working side by side

How the two systems work together

SharePoint collaboration

once approved →

Approved asset in Freedam

sharing →

Teams, agencies, and partners

A practical first step

Start with one campaign

With direct upload and the supported sources, you can try the new hand-off without planning a company-wide migration first. Freedam does not currently offer a native SharePoint connector, so it usually helps to start with material your team can comfortably bring across and keep up to date.

1. Choose the current set

Begin with the images and campaign files still in use for one product line or market. Older folders can follow once people have tried the new routine.

2. Describe how people look for it

Add the product, campaign, rights, status and audience details people tend to mention when they ask marketing for something.

3. Invite a few real users

Ask a few colleagues or partners to try search, an external portal or share, the download options and a version update before you widen the scope.

Talking with IT

Agreeing on ownership with IT

Identity and roles

Microsoft and Google SSO, workspace roles, user groups and asset access rules cover the different ways signed-in users get access.

Guest policy

Public Portal access is read-only and enforced on the server. Originals stay unavailable unless a guest rule grants them.

Auditable changes

Versions, workflow transitions, rights events, shares, views and downloads each have their own history or analytics.

Freedam access rule tester evaluating the exact policy an anonymous portal visitor receives — Administrators can test what a guest can see, preview and download, and which watermark applies, before publishing.

Questions buyers ask

Before you make the change

Does Freedam replace all of SharePoint?

No. For most teams the boundary is marketing assets. Company documents, intranet content, records, Teams collaboration and Microsoft 365 working files can stay in SharePoint, while approved images, video, design files and campaign materials move into Freedam.

What improves for external agencies and partners?

External audiences can use public collections, a read-only public portal, controlled share links or signed-in access, depending on who they are and the asset policy. That usually means less time finding their way around another company's SharePoint or waiting for a ZIP file.

How can we migrate existing marketing assets?

You can upload files directly or sync them from Google Drive, WebDAV or S3-compatible storage. Folder mapping, collection assignment, catalog metadata, sample runs and dry runs let you bring files across gradually and check the results as you go.

When should marketing stay on SharePoint?

SharePoint may be the better fit when the library is small, mostly documents, rarely shared outside the company and easy for the team to manage with existing Microsoft 365 skills. A switch makes most sense when it solves a media task that keeps coming up. Adding another place to store files may not help on its own.

Continue exploring

The SharePoint guide series

Four longer guides with the numbers behind this page: what SharePoint can do with media, what each option costs, how the two systems share the work, and how a migration runs.

Part 1

SharePoint as a DAM: the real limits

File, storage, library, search and AI-tagging limits, each one sourced from Microsoft documentation.

Part 2

SharePoint vs DAM: what each one costs

SharePoint seat licences, extra storage, pay-as-you-go image tagging, build hours and search time, in one model.

Part 3

DAM and SharePoint together

Which content stays in SharePoint, which moves, and how Teams, OneDrive, Copilot and Office reach the assets.

Part 4

Migrating from SharePoint to a DAM

Inventory, dedupe, column mapping, permission translation, link redirects and a timeline by asset volume.

Continue exploring

More help with the SharePoint decision

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.

Decision guide

SharePoint vs DAM

Compare the two approaches across media discovery, governance, external access, and ongoing ownership.

Technical guide

Using SharePoint as a DAM

A practical guide to the libraries, metadata, search, automation, permissions, and maintenance involved.

See a small hand-off in practice

Look at one familiar campaign

In the demo you can look at search, rights, versions, collections and external access in Freedam, while the parts of SharePoint that work well for you stay as they are.