Administration Overview

This guide provides an overview of Agility CMS administration, including the interface, capabilities, and key administrative concepts.

Understanding Agility CMS Architecture

As an administrator, it's important to understand how Agility CMS is structured. Agility CMS follows a headless architecture pattern:

Agility CMS uses a headless architecture where content is managed separately from presentation. Content is created in the Content Manager, exposed through Content APIs, and consumed by frontend applications. Assets are delivered via CDN. This architecture enables multi-channel publishing and independent scaling.

Understanding the Data Model

Agility CMS organizes content using a structured data model:

The Agility data model shows how Sitemap organizes Pages, Pages contain Components, and Components display Content Items. Each entity has a corresponding Model that defines its structure. As an administrator, you'll manage these Models (Page Models, Component Models, Content Models) and configure how they relate to each other.

Admin Interface Sections

The Agility CMS administration interface is organized into four main sections:

The Agility CMS interface is organized into: Content (Lists/Items), Assets (Files/Images/PDFs), Pages (Sitemap/Pages/Components), and Web Studio (Preview). As an administrator, you'll work across all these sections to configure and manage the instance.

Detailed Interface Areas:

1. Content - Manage content models and content items
2. Pages - Manage pages, sitemap, and page models
3. Components - Manage component definitions
4. Assets - Manage media library
5. Settings - Instance configuration
6. Users - User and role management
7. Security - Access control and API keys

Admin Capabilities

As an administrator, you can:

• Create and modify content models
• Define component structures
• Manage user accounts and permissions
• Configure instance settings
• Access API keys and security settings
• Manage sitemaps and page models
• Configure workflows via Security settings
• Set up webhooks
• Access reports and analytics

Key Administrative Concepts

Models vs Instances

• Models: Define structure (content models, component models, page models)
• Instances: Actual data (content items, components, pages)

Permissions vs Roles

• Permissions: Base-level actions (Read, Edit, Publish, etc.)
• Roles: Collections of permissions (Editor, Publisher, Admin, etc.)

Workflows

Workflows are configured through:

• Global Roles: Assign roles to users
• Security Settings: Configure permissions on lists and pages
• Item-Level Permissions: Granular access control

Administrative Workflow

Initial Setup

1. Configure locales
2. Set up sitemap
3. Create content models
4. Create component models
5. Configure page models
6. Set up users and permissions

Ongoing Management

1. Monitor content and usage
2. Manage users and permissions
3. Update models as needed
4. Configure workflows
5. Monitor security and API usage

Best Practices

1. Start with Minimum Permissions: Begin with minimum required permissions
2. Document Configurations: Document all configurations and decisions
3. Regular Reviews: Review user access and configurations regularly
4. Security First: Prioritize security in all decisions
5. Monitor Usage: Track instance usage and performance

---

Next: User Management - Users and permissions