Repository
Repositories are secure containers for organizing assets and content by team, project, or purpose. They manage permissions, workflows, and publishing across departments.
📁Repositories
In Content Lion, a repository is like a centralized "bucket" where all the content and digital assets for a team, campaign, or department are stored and managed. Repositories ensure that content is logically organized, access-controlled, and easy to retrieve and publish.
▶️ Types of Repositories
Content Lion supports two main types of repositories:
1. Business Repositories
Designed for content that supports external-facing digital experiences, such as:
- Web-ready images and video files
- Marketing content (blog posts, banners, press releases)
- Multilingual assets for global websites
These repositories are optimized for publishing, localization, and reuse across channels.
2. Document Repositories (Coming Soon)
Used to manage internal or structured business content, such as:
- Contracts, invoices, and reports
- HR records (employee profiles)
- Supplier and operational data
These repositories typically serve internal users and are not meant for public publishing or translation.
▶️ How Repositories and the DAM Work Together
In Content Lion, repositories are the foundational storage containers that hold different types of content, including structured content items and digital assets.
Here’s how it connects:
- The DAM (Digital Asset Management system) operates within a repository—specifically, a Digital Asset Repository.
- These repositories store all the media used across sites and content items—images, videos, audio files, and documents.
- When a user uploads a media file into the DAM, it is technically being uploaded into a repository assigned to their Mane.
- That repository powers all media access across entries, pages, and templates via global APIs and a CDN.
- You can manage permissions to these repositories via Mane-level roles, especially roles like Content Admin, Site Admin, and Mane Admin.
✅ Repositories are the backbone — the DAM is the interface and system that makes managing assets in those repositories efficient, visual, and powerful.
▶️ Access & Permissions
Access to repositories in Content Lion is managed at the Mane level, not per individual repository. This means that user permissions are tied to their role within a Mane, which governs what they can do across all repositories, sites, and dev components within that environment.
Mane-Level Roles and Repository Access
Role | Repository Permissions |
🦁 Mane Admin | Full control: can create, edit, delete, and assign users to any repository in the Mane. |
🗂 Content Admin | Full access to all repositories across the Mane. |
✂️ Content Admin Lite | Access limited to repositories they are assigned to manage. |
📦 Site Admin / Dev Admin | No default repository access unless granted separately. |
👀 Enterprise User / Lite Roles | View-only or task-specific access, if granted. |
So, instead of setting access per repository, administrators assign users a role within the Mane (like “Content Admin” or “Site Admin Lite”), and their access to all repositories in that environment is controlled accordingly.
▶️ Creating & Managing Repositories
With the proper privileges, you can create and manage repositories from:
Content Lion Software > Content > Dropdown: Repositories
When creating a repository, you define:
- Repository name and description
- Type (coming soon)
- Asset Types
- Publishing Channels
- Taxonomies