---
title: Understanding Scaleway Organizations and Projects
description: Understand how Scaleway Organizations and Projects work together to structure access to your account, group resources, and manage quotas.
tags: organization project owner resource quota
dates:
  validation: 2026-09-09
---

Organizations and Projects are the 2 structures Scaleway uses to organize access to your account and group your resources. This page gives you an overview of how they work together, and explains the related terminology in a logical order.

## Your Organization

When you create a Scaleway account, an [Organization](/organizations-and-projects/concepts/glossary/#organization) is automatically created, of which you are the [Owner](/iam/concepts/glossary/#owner). As Owner, you have full access and rights to all resources within your Organization, as well as to Organization-level features such as billing and IAM.

<Message type="note">
  If you were invited to join an existing Organization, you can be added as a [Member](/iam/concepts/glossary/#member). Your permissions in that Organization depend on the policies set for you by the Organization administrator. A personal Organization is still automatically created for you when you sign up, even in this case.
</Message>

Every Organization has an Organization ID, which you can find on the [Organization settings page](https://console.scaleway.com/settings/organization/information) of the console. You can also set an Organization alias as an easier-to-remember alternative to the Organization ID, which Members can use to log in directly. See the [How to set an Organization alias](/organizations-and-projects/organization/set-organization-alias/) documentation for more information.

## Group resources into Projects

A Project is a grouping of Scaleway [resources](/organizations-and-projects/concepts/glossary/#resource), such as Instances, Private Networks, or Kubernetes Kapsule clusters. Each Organization comes with a default Project, and you can create new Projects to organize your infrastructure. Projects are cross-region, so resources located in different regions can belong to the same Project.

Grouping resources into different Projects also lets you use IAM to define custom access rights for each Project, and makes it easier to track resource usage on your invoices. See the [How to create a Scaleway Project](/organizations-and-projects/project/create-a-project/) documentation to create one, and [How to add resources to a Project](/organizations-and-projects/project/add-resources-project/) to start populating it.

<Message type="tip">
  You can view an overview of the resources, settings, and credentials of a Project on its Project dashboard in the console.
</Message>

See the [How to change the name of a Project](/organizations-and-projects/project/change-project-name/) and [How to delete a Project](/organizations-and-projects/project/delete-a-project/) documentation for more information on managing existing Projects.

## SSH keys

An SSH key allows passwordless connection to an [Instance](/instances/concepts/#instance). It consists of a private key, which you keep on your local computer, and a public key, which you upload to the Scaleway console and which is transferred to your Instance during the boot process. See the [How to generate an SSH key pair](/iam/security/create-ssh-key/) documentation for detailed instructions.

## Quotas

Every Organization has quotas, which are limits on the number of Scaleway resources it can use. Quotas apply per product and product type, and are designed to prevent abuse. You can view your quotas on the Organization dashboard of the console.

See the [Understanding Organization quotas](/organizations-and-projects/organization/organization-quotas/) documentation for the full list of available quotas, and [How to manage Organization quotas](/organizations-and-projects/organization/manage-quotas/) to view and request an increase for yours.

## Secure your Organization

As Organization Owner, you can enforce Multifactor Authentication (MFA) for all Members of your Organization, requiring them to set up a second authentication factor before they can access their account. See the [How to enforce Multifactor Authentication for an Organization](/iam/security/enforce-mfa/) documentation to set it up.