# Projects

> Group work inside an org with projects, and restrict members and keys to some of them.

Source: https://nodus-platform-site.pages.dev/docs/guides/access/projects/
Build revision: 211ad9f836655b1c3a2668c4693e442471f28614

A **project** is a namespace inside your org. Jobs, Sandboxes, Volumes, Secrets and the other resources you create live in one project. Every org has `default`, which cannot be deleted.

Terminal window

```bash
nodus create project research --display-name "Research"
nodus get projects
nodus run -p research -- python train.py
```

In the console, **Team › Projects** lists each project with how many members can use it, its spend over the last 30 days and its spend limit, and has **New project**. Give each team its own project: its runs, storage and keys stay apart, and its spend shows on its own line.

A project name is lowercase letters, digits and dashes. `nodus`, `team`, `settings`, `billing`, `integrations`, `infrastructure` and `support` are reserved.

Creating, changing and deleting projects needs the `projects:write` scope, which Admins and Owners hold. Deleting a project deletes everything in it: running work is cancelled first. Usage and billing records are kept.

## Restrict access to projects

Members and API keys can be limited to some projects:

Terminal window

```bash
nodus edit member usr-01j9abc --projects research
nodus create apikey ci --projects research --scopes jobs:write
```

A member or key with a project list sees and changes only those projects. An empty list means every project.

## Cap a team’s spend

A budget scoped to a project caps that team. From **Team › Projects**, open a project’s menu and choose **Set a spend limit**, or:

Terminal window

```bash
nodus create budget vision-monthly --limit 500 --scope-project vision-team
```

Budgets can also cap one person, or one person inside one project. When several budgets cover the same work, the tightest one applies.