Organizations and Projects¶

edgeContinuum uses a hierarchical structure to help you organize and manage your platform resources. At the top level, you'll work with Organizations, which contain Projects where your day-to-day work happens.

Understanding the Hierarchy¶

The platform's structure is designed to give you flexibility and control:

graph TD
    A[Organization] --> B[Users & Groups]
    A --> C[Infrastructures]
    A --> D[Projects]
    D --> E[Managed Services]

Organizations¶

Organizations are the top-level container in edgeContinuum. Think of an organization as your company's dedicated workspace on the platform.

Each organization is completely isolated from others, making it perfect for:

Multi-tenancy: Different business units, departments, or clients can have their own separate organizations
Complete independence: Resources, configurations, and data don't overlap between organizations

What Lives in an Organization?¶

At the organization level, you'll manage:

Users and Groups: Invite team members and organize them into groups for efficient permission management
Infrastructures: Define the infrastructure you want to manage
Projects: Create and manage projects

Projects¶

Projects are workspaces within your organization where you deploy and manage your services. They help you organize related work and control who can access what.

Why Use Projects?¶

Projects give you flexibility to organize your work in ways that make sense for your team:

Separate by Environment

Isolate different stages of your deployment pipeline
- my-app-dev
- my-app-staging
- my-app-production
Separate by Application

Organize projects around different applications or services
- frontend-services
- backend-services
- data-processing
Separate by Team or Customer

Give each team or customer their own workspace
- team-alpha-project
- team-beta-project

What Lives in a Project?¶

Projects contain your Managed Services, the actual services and applications you deploy and run on the platform.

Access Control¶

edgeContinuum's hierarchical structure gives you fine-grained control over who can do what. Permissions can be granted at both the organization and project levels, with some permissions automatically inherited from the organization to its projects.

For detailed information about available permissions, see the Permissions Reference.

Best Practices¶

To get the most out of Organizations and Projects:

Create separate organizations when you need complete isolation between tenants or business units
Group related services in the same project to keep ownership clear
Use multiple projects to separate concerns - whether by environment, application, or team
Use user groups to simplify permission management
Plan your project structure before deploying services to make permissions management easier
Invite collaborators at the organization level, then grant them access to specific projects as needed