Hierarchy

The hierarchy within ContentPaul is designed to help organizations of all sizes effectively manage and organize their work. By structuring your tasks and content within this hierarchy, you can streamline workflows, maintain clarity, and ensure that sensitive information is appropriately managed. Here’s an overview of the ContentPaul hierarchy and its benefits:

Key Benefits of the ContentPaul Hierarchy:

Scalable Structure: The hierarchy can grow with your organization, allowing you to expand as needed without losing visibility or control over your work.

Controlled Access: Projects and items can be organized in different workspaces, ensuring that sensitive information is only accessible to those who need it.

The hierarchy is composed of eight levels, starting with the Company and ending with Assets.

1. Company

At the top of the hierarchy is the Company level. This encompasses your entire organization and all the work within it. By default, every organization has at least one workspace. As your organization grows, all your work remains visible and manageable within this overarching structure.

2. Workspace

Workspaces are flexible and can be customized based on your organization's needs. Depending on your subscription, you can create multiple workspaces to group your work logically—whether by departments, teams, major initiatives, or clients. Each workspace has its own settings, and access can be controlled to ensure that only the relevant team members have visibility. Workspaces also allow for the movement or copying of items between them, providing flexibility in how you manage your content.

3. Project

Projects are used to structure your content and apply specific workflows or types of work. They can be organized by campaigns, activations, or any other project type that fits your needs. Projects can also include additional information like tags, dates, and documents to enhance organization. For even more granularity, projects can contain sub-projects, allowing for complex work to be broken down into more manageable pieces.

4. Folder

Folders are an optional layer in the hierarchy but are highly useful for organizing content within projects. They provide another level of structure to keep related content grouped together.

5. Content Item

An content item is where the actual content creation happens. Items can be either unstructured using one single rich text content editor or structured using a template assemble by single content blocks . Structured items are particularly useful when you need to ensure that content displays correctly in previews or when publishing directly to platforms like blogs or social media channels.

6. Version

Versions are closely tied to items, serving as variations that are logically connected to the parent item. Versions are useful for purposes such as creating translations or A/B testing different content approaches. They share important attributes with their parent item, such as dates and storage locations.

7. Content Block

Every content item requires a content block to represent its content. There are various types of content blocks available, with the most general being the Document Content Block. This block allows the content item to function as a freely editable, unstructured document, similar to what you may be familiar with from other systems. By combining different content block types, users can create a structured content layout that can be integrated with other systems or used for previews.

8. Asset

An asset refers to any file associated with a content item, such as images, videos, audio files, or documents. Assets are stored in the asset library and can be reused across multiple items, ensuring consistency and efficiency. Assets can be stored either at the workspace level or the company level, depending on whether they need to be accessible across the entire organization.