Skip to content

Organizations and Projects

Everything in edgeContinuum lives in an organization, and the resources you deploy live in projects inside it.

graph TD
    A[Organization] --> B[Members & Groups]
    A --> R[Roles]
    A --> Q[Quotas]
    A --> C[Infrastructures]
    C --> F[Service Configs]
    A --> D[Projects]
    D --> E[Applications, Managed Services<br/>and Compute & Network]

Organizations

An organization is your tenant: a company, business unit or customer. Organizations are isolated from each other: members, roles, resources and quotas never cross between them. An organization holds:

  • Members, groups and roles: who belongs to it and what they can do. See Users, Groups and Permissions.
  • Infrastructures: the clouds it deploys onto, and the service configs that offer managed services on them. See Infrastructure.
  • Quotas: how many resources it can hold, shared by all its projects. See Resource Quotas.
  • Projects: where the resources live.

When you sign up, the platform creates an organization for you named after you (for example, Ana's Organization), with a project named after you (Ana's Project), unless your platform operator has turned this off. It is an ordinary organization: you own and administer it and can invite others into it. If you start with no organization, Organizations & projects shows No organizations yet: create one, or accept an invitation from My invitations.

Projects

A project is a workspace inside an organization. Every resource you deploy belongs to exactly one project: application clusters, fleets and instances, Kubernetes clusters, PostgreSQL databases, virtual machines, routers, networks, firewalls and SSH keys. Use projects to separate environments (my-app-dev, my-app-production), applications, or teams, and to give people access to only part of the organization.

Projects keep their resources to themselves, with one exception: a project can share a network, firewall or SSH key with other projects in the same organization. See Sharing resources between projects.

Manage organizations and projects

Open IAM & SECURITY > Organizations & projects. The tree on the left lists the organizations you are a member of; expand one to see its projects. Jump to… (Ctrl+K, or ⌘K on macOS) searches organizations and the projects of the one you have open.

Inside an organization you see every project if you may list projects on the organization, and otherwise only the projects where you were granted permission to list them.

No projects in the tree?

If your platform operator has turned off the projects view, the tree lists organizations only and organizations have no Projects tab, so you can't create projects or manage project access from the console. Your organization's default project is still there and works as usual. Ask your platform operator if you need more projects.

An organization's page has tabs for Projects, Members, Groups, Roles and Check access; a project's page has Members and Groups tabs for its access. Their use is described in Users, Groups and Permissions.

Create an organization

Click New organization at the bottom of the tree, enter a name and click Create organization. You become its owner and an organization administrator, and it starts with a project named after you, like your first organization. The new organization opens, but it does not become your active one (see Browsing is not switching).

The organizations you own need different names. Each account can own a limited number of organizations, your first one included: two unless your platform operator has set a different limit. This limit isn't part of the organization's quotas and doesn't appear on the Quotas page. Once you reach it, creating another is refused.

Create a project

Open the organization's Projects tab, click New project, enter a name and click Create project. Project names must be unique within the organization, and each project counts against the organization's projects quota. You need permission to create projects in the organization.

Rename an organization or project

Click Rename organization or Rename project on its page. Only the name changes; members, grants and resources stay as they are.

Organizations and projects can't be deleted

Plan your structure with that in mind, and rename an organization or project if its purpose changes.

Work in an organization and project

The console always works in one active organization. Infrastructure, applications, managed services, compute and network resources, dashboards and quotas all follow it, and new resources are created in it.

Switch organization

Click the Organization crumb in the header, or press Ctrl+K (⌘K on macOS) outside Organizations & projects, and pick an organization. Recently used ones are listed first.

Filter by project

On resource lists, the header also shows a Project crumb. Pick All projects or a single project: lists show only that project, and create forms start with it selected (you can still change it in the form). The choice is kept in the page address, so a link you share keeps it. Switching organization resets it to All projects.

Browsing is not switching

Opening another organization or project in Organizations & projects does not change your active organization, so you can manage access elsewhere without moving the rest of the console. To start working in the organization you're looking at, click Make <organization> active on its page, or Work in <organization> on one of its projects. Check which organization is active before creating resources.

Access control

People get access through grants on the organization, which reach all its projects, or in a single project. Access only ever adds up. How grants, roles and groups combine is explained in How access adds up.

To structure access well, grant broad access per project rather than on the organization, and use groups and roles; see Best practices.