Skip to main content

Multi-Organization Management

For holding companies, enterprise groups, and organizations with multiple business units, managing operational data across entities requires coordination. This guide covers patterns for automated multi-organization workflows.

Organization Structures

Dcycle supports hierarchical organization structures:
Each organization can have:
  • Its own users and permissions
  • Separate facilities, vehicles, and data
  • Independent or consolidated reporting

Common Use Cases

1. Consolidated Corporate Reporting

Aggregate emissions data across all subsidiaries:

2. Centralized Data Upload

Upload data to multiple organizations from a central source:

3. Cross-Organization Comparison

Compare performance across business units:
Output:

Automation Patterns

Pattern 1: Hub and Spoke

Central team manages automation, subsidiaries provide data:

Pattern 2: Federated

Each subsidiary manages their own automation with central oversight:

Pattern 3: API Key Per Organization

For complete isolation, use separate API keys:

Reporting Across Organizations

Consolidated Emissions Report

Year-over-Year Comparison by Subsidiary

Best Practices

Consistent Naming

Use consistent naming conventions across organizations for facilities, vehicle types, and categories.

Centralized Templates

Maintain CSV templates centrally to ensure data consistency across subsidiaries.

Permission Boundaries

Use separate API keys when subsidiaries shouldn’t access each other’s data.

Audit Logging

Log which organization context was used for each operation for compliance.

Next Steps

AI-Assisted Analysis

Use AI to analyze cross-organization data

Reporting Pipelines

Set up automated reporting workflows