---
title: Projects
description: Every account starts with a default project; create more to separate keys, databases, files, links, and pages.
---

# Projects

A project groups your keys, databases, files, links, and pages — for
dashboard organization and access control. It has nothing to do with
public URLs: a page's `p.shebang.pro` address never changes because you
move it between projects.

## Your default project

Signing up creates one project automatically, named and slugged
`default`. Every resource you create lands there until you say
otherwise — most accounts never need a second one.

## Creating another

From the dashboard, open the project switcher in the top bar and choose
**New project**. Give it a name, a tag, a color from the platform's
curated palette, and a slug.

From the MCP server or the API, use `project_create` — `slug` is
required, not generated for you: 3 to 30 lowercase letters, numbers, or
underscores, and not one of a reserved-word list enforced server-side.

```
project_create({ name: "Acme launch", tag: "acme", color: "#3b82f6", slug: "acme_launch" })
```

You pass that same `slug` as `project` to other tools when you want to
act on that project instead of your key's home project.

## Dashboard routes

Each project has its own area: `dash.shebang.pro/<slug>/page`, `/serve`,
`/link`, and `/base`, plus a `/settings` tab. Account-wide settings —
keys, connected apps, security — live at `dash.shebang.pro/account`,
outside any single project.

## Moving resources

`project_assign`/`project_unassign` move an existing key, database, file,
link, or page between projects without recreating it. See
[projects and scoping](/concepts/projects-and-scoping) for how a key
decides which project it's allowed to touch in the first place.

## Next

[Your first key](/getting-started/your-first-key) — mint the credential
that talks to any of this.