Productify

Appearance

Managing Applications ​

Applications are the core entities in Manager, representing individual deployable services or apps within your SaaS platform.

What is an Application? ​

An application represents a deployable service with:

  • Unique configuration - Application-specific settings
  • One or more endpoints - Access points for the application
  • Trigger integration - Automation and scheduled tasks
  • User access - Role-based permissions

Creating an Application ​

Step 1: Navigate ​

Click Applications in the sidebar or go through a project.

Step 2: Click Create ​

Click the Create Application button.

Step 3: Fill Details ​

  • Name (required) - Application display name
  • Identifier (optional) - Unique identifier (auto-generated if omitted)
  • Tenant (required) - Select parent tenant
  • Project (required) - Select parent project
  • Description (optional) - Brief description

Step 4: Create ​

Click Create to save.

Application List ​

View all applications with:

  • Name - Application display name
  • Project - Parent project
  • Tenant - Parent tenant
  • Endpoints - Number of endpoints
  • Status - Active/Inactive
  • Actions - Edit, Delete, View

Filtering ​

Filter applications by:

  • Tenant - Show only apps in specific tenant
  • Project - Show only apps in specific project
  • Status - Active or inactive
  • Name - Search by application name

Application Details ​

Click an application name to view detailed information.

Overview Tab ​

  • Application metadata
  • Parent project and tenant
  • Creation and update timestamps
  • Endpoint count

Endpoints Tab ​

All endpoints for this application:

  • Endpoint URLs
  • Domains (managed/custom)
  • Health status
  • Quick actions

See Endpoints & Domains for details.

Settings Tab ​

Application-specific configuration:

  • Backend Settings - Modules, key-value pairs
  • Frontend Settings - Themes, locales, modules
  • Configuration Layers - View inheritance

See Settings Editor for comprehensive guide.

Triggers Tab ​

Automation configured for this application:

  • Cron schedules
  • Trigger names and descriptions
  • Last execution time
  • Enable/disable toggles

See Triggers & Automation for details.

Users Tab ​

User access to this application:

  • Users with permissions
  • Role assignments
  • Add/remove users

Editing an Application ​

  1. Navigate to application details
  2. Click Edit button
  3. Update fields:
    • Name
    • Description
    • Project (can reassign to different project)
  4. Click Save Changes

WARNING

Changing the project will affect configuration inheritance. Application-specific settings are preserved, but inherited defaults will come from the new project.

Application Status ​

Active ​

Application is operational and can:

  • Receive trigger executions
  • Accept requests to endpoints
  • Be accessed by users

Inactive ​

Application is disabled and will:

  • Not receive trigger executions
  • May not be accessible (depending on endpoint configuration)
  • Remain in the system for future activation

Toggle Status ​

  1. Navigate to application details
  2. Click Status toggle
  3. Confirm activation/deactivation

Deleting an Application ​

Permanent Deletion

Deleting an application removes all associated data including endpoints, triggers, and settings. This cannot be undone.

Steps ​

  1. Navigate to application details
  2. Click Delete button
  3. Review what will be deleted:
    • All endpoints
    • All triggers
    • All settings
    • User associations
  4. Type application name to confirm
  5. Click Confirm Delete

Application Domains ​

Applications can have multiple domains:

Managed Domains ​

System-generated domains following pattern:

<app-identifier>.<tenant-identifier>.<base-domain>

Example: myapp.acmecorp.productify.dev

Custom Domains ​

User-provided domains requiring DNS configuration:

app.example.com

See Endpoints & Domains for setup.

Best Practices ​

Naming ​

  • Use descriptive names: "Customer Dashboard", "Admin Portal"
  • Include version if needed: "API v2", "Dashboard v3"
  • Keep identifiers URL-friendly: lowercase, hyphens

Organization ​

  • Group related services in same project
  • Use consistent naming across environments
  • Document purpose in description field

Configuration ​

  • Override project settings only when necessary
  • Keep application-specific customizations minimal
  • Document custom configurations

Security ​

  • Regularly review user access
  • Use Personal Access Tokens for API access
  • Monitor audit logs for suspicious activity

Common Use Cases ​

Multi-Environment Setup ​

Separate applications for each environment:

Project: MyProduct
  ├─ Application: Production
  ├─ Application: Staging
  └─ Application: Development

Microservices Architecture ​

Each service as an application:

Project: E-commerce Platform
  ├─ Application: Auth Service
  ├─ Application: Product Catalog
  ├─ Application: Shopping Cart
  ├─ Application: Payment Service
  └─ Application: Order Management

White-Label SaaS ​

Different branding per customer:

Project: Enterprise Clients
  ├─ Application: Client A Portal (blue theme)
  ├─ Application: Client B Portal (green theme)
  └─ Application: Client C Portal (red theme)

Troubleshooting ​

Cannot Create Application ​

Issue: "Project not found" error

Solution: Ensure you have access to the selected project and tenant

Endpoints Not Accessible ​

Check:

  1. Is application status "Active"?
  2. Are endpoints configured correctly?
  3. Is DNS pointing to correct address?
  4. Check application logs

Settings Not Taking Effect ​

Reason: Configuration might be cached

Solution:

  1. View effective configuration
  2. Verify settings are saved
  3. Restart application if needed
  4. Check configuration inheritance

Triggers Not Executing ​

Check:

  1. Is application "Active"?
  2. Are triggers enabled?
  3. Is backend registered and healthy?
  4. Check backend logs for errors

See Also ​