Is your DAM delivering what it promised?
Many organizations can’t answer that question with any confidence. Assets can’t be found, so they’re recreated Metadata drifts. Users download files from email threads because they’ve stopped trusting the system. And when leadership questions the investment, no one has a clear baseline to work from.
A DAM health check gives you evidence of how your DAM is being used and how it’s performing.
What‘s included
Portal setup: Custom URL, SSO configuration, initial homepage, and brand theming. The platform will look and feel like yours from day one.
Taxonomy and metadata: Workshops to design a logical, intuitive taxonomy and metadata model your team can navigate and maintain. Includes UAT and client sign-off before configuration.
Permissions: Out-of-the-box permission profiles, user groups, access restrictions, and asset-level visibility rules scoped to your team structure.
Derivatives/renditions: Configuration of asset derivatives so the right file formats are available for the right use cases.
Admin training: Two training sessions covering management of the homepage, users, permissions, and taxonomy. Your team leaves able to run the platform independently.
Asset migration: Scoped separately. Ntara will introduce migration options during onboarding to prepare you for the next phase.
How the engagement is structured
The onboarding follows a structured week-by-week plan. Key phases include:
Initial setup (weeks 1–2)
Kickoff, portal provisioning, custom URL and SSO configuration, brand theming.
DAM 101 workshop (week 3)
Education session covering DAM fundamentals, taxonomy, metadata, and asset criteria to align your team before design begins.
Taxonomy workshops (weeks 4–7)
Four workshops to design, test, iterate, and finalize your taxonomy. Includes client sign-off.
Permissions and configurations (weeks 8–11)
User acceptance testing, permissions design and sign-off, derivative configuration, API token overview, and plug-in information.
Admin training (weeks 13–14)
Two dedicated training sessions covering homepage management, user and permission management, and taxonomy management.
Adoption support (weeks 14+)
Follow-up check-in meetings and technical support through launch.
What comes next
Onboarding establishes the foundation. From there, teams typically move into one or more of the following:
- DAM implementation: custom workflows, metadata enrichment, and deeper governance design
- Asset migration: bringing your existing library into the platform with metadata intact
- DAM integrations: connecting to PIM, ecommerce, CMS, or print automation
- Admin-as-a-service: ongoing oversight and platform management
Ready to get your DAM stood up correctly?
Schedule a kickoff call. We’ll scope the engagement, clarify what’s in and out, and map a path to a platform your team will actually use.
