Skip to content

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

  1. Click Projects in the sidebar
  2. Click New Project
  3. Enter the Name
  4. Enter the Slug (auto-filled from the name, max 10 characters)
  5. 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

  1. Navigate to project details
  2. Click Edit
  3. Update the Name
  4. Click Save Changes

Deleting a Project

Destructive Action

Deleting a project removes all its tenants, applications, and their configurations. This cannot be undone.

Steps

  1. Navigate to project details
  2. Click Delete
  3. Review what will be deleted
  4. 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 Dashboard

Each project then contains its own tenants for environments:

Project: ERP System
  ├─ Tenant: Development (dev)
  ├─ Tenant: Staging (qas)
  └─ Tenant: Production (run)

Configuration Management

  1. Set common defaults at project level - Avoid repeating settings in each application
  2. Override only when necessary - Let applications inherit project settings
  3. 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:

  1. Check application settings first
  2. If not found, use tenant settings
  3. 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:

  1. View the source project's settings
  2. Switch to JSON editor mode
  3. Copy the configuration JSON
  4. Create the new project
  5. Paste the configuration into the new project's settings (JSON editor)
  6. 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:

  1. Set up project-level default settings
  2. Create first application with specific settings
  3. Use first application as template for others
  4. Adjust individual applications as needed

Project Templates

Save common project configurations:

  1. Configure a "template" project with ideal settings
  2. Copy its settings JSON from the JSON editor
  3. When creating new projects, paste the template JSON into their settings
  4. 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:

  1. Are application settings overriding project settings?
  2. Is the configuration syntax correct?
  3. 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