Managing Projects
Projects are the top-level organizational unit in Manager. A project contains tenants (environments), which in turn contain applications.
What is a Project?
A project is a container that:
- Contains tenants - Each environment (dev, staging, production) is a tenant within the project
- Groups applications - Applications live inside the project's tenants
- Shares configuration - Project settings are the base layer inherited by tenants and applications
- Owns shared resources - Language packs, pilet packages, and audit logs are project-scoped
Creating a Project
- Click Projects in the sidebar
- Click New Project
- Enter the Name
- Enter the Slug (auto-filled from the name, max 10 characters)
- Click Create
Viewing Projects
The projects list displays:
- # - Project slug
- Name - Project display name
- Created at / Created by - Creation metadata
- Updated at / Updated by - Last modification metadata
Project Details
Click a project to view its detail page and sub-pages:
Overview
- Project information
- Creation and modification dates
- User access management
Tenants
List of tenants (environments) in this project. See Managing Tenants.
Settings
Project-level configuration:
- Backend Settings - Module configuration
- Frontend Settings - Themes, locales, modules
- Key-Value Pairs - Custom configuration
These settings serve as the base defaults for all tenants and applications in the project.
Language Packs, Pilets, and Audit Logs
Project-scoped resources, each with its own page:
- Language Packs - Translations shared by the project's applications
- Pilets - Microfrontend packages (see Pilet Management)
- Audit Logs - Activity history (see Audit Logs)
Editing a Project
- Navigate to project details
- Click Edit
- Update the Name
- Click Save Changes
Deleting a Project
Destructive Action
Deleting a project removes all its tenants, applications, and their configurations. This cannot be undone.
Steps
- Navigate to project details
- Click Delete
- Review what will be deleted
- Confirm the deletion
What Gets Deleted
- Project record
- All tenants in the project
- All applications in those tenants
- All endpoints, triggers, and settings for those applications
- Project-scoped language packs and pilet packages
Best Practices
Naming Conventions
Use descriptive names that indicate purpose:
- [OK] Good: "Customer Portal", "Internal Tools", "Mobile Apps"
- [NO] Avoid: "Project 1", "Test", "Misc"
Organization Strategy
By Product Line
Projects
├─ Project: ERP System
├─ Project: CRM Platform
└─ Project: Analytics DashboardEach project then contains its own tenants for environments:
Project: ERP System
├─ Tenant: Development (dev)
├─ Tenant: Staging (qas)
└─ Tenant: Production (run)Configuration Management
- Set common defaults at project level - Avoid repeating settings in each application
- Override only when necessary - Let applications inherit project settings
- Document special configurations - Note why an application has custom settings
Configuration Inheritance
Projects sit at the top of the configuration hierarchy:
Project Settings (most general)
↓
Tenant Settings
↓
Application Settings (most specific)When an application needs a setting:
- Check application settings first
- If not found, use tenant settings
- If not found, use project settings
Example:
- Project sets:
theme: "light",locale: "en" - Tenant sets:
theme: "dark" - Application sets:
locale: "es"
Result for the application:
theme: "dark"(from tenant)locale: "es"(from application, overrides project)
Common Tasks
Clone Project
To duplicate a project with its settings:
- View the source project's settings
- Switch to JSON editor mode
- Copy the configuration JSON
- Create the new project
- Paste the configuration into the new project's settings (JSON editor)
- Manually recreate tenants and applications (they are not cloned; applications can be copied between tenants with
copyApplication)
Bulk Application Creation
When adding many similar applications:
- Set up project-level default settings
- Create first application with specific settings
- Use first application as template for others
- Adjust individual applications as needed
Project Templates
Save common project configurations:
- Configure a "template" project with ideal settings
- Copy its settings JSON from the JSON editor
- When creating new projects, paste the template JSON into their settings
- Customize as needed
Troubleshooting
Cannot See Projects
Reason: You are not a member of the project
Solution: Ask a project owner or administrator to add you to the project
Settings Not Applying to Applications
Check:
- Are application settings overriding project settings?
- Is the configuration syntax correct?
- View effective configuration in settings editor
Cannot Delete Project
Reason: The project still contains tenants or applications
Solution: Delete the contained tenants and applications first
See Also
- Managing Applications - Configure individual applications
- Configuration Layers - Understand inheritance
- Settings Editor - Configure project settings