# Sign up and create your org

> Create an account, create or join an organization, and switch between the orgs you belong to.

Source: https://nodus-platform-site.pages.dev/docs/guides/access/sign-up-and-orgs/
Build revision: 211ad9f836655b1c3a2668c4693e442471f28614

Everything you run on Nodus belongs to an **organization** (org). Credits, projects, members and API keys are all per org.

## Sign up

Sign up at the console with email, Google or GitHub. Nothing is created until you choose:

* If someone invited you, the console shows the invite first. Accept it to join their org.
* Otherwise the console asks you to **Create your org**. The name is filled in for you, and you can change it.

The first org you create with a verified email address receives the **$30 starter credit**, valid for 30 days. Joining an org by invite never adds credit, so accepting an invite does not use up your own starter credit.

## Start from the terminal

Terminal window

```bash
nodus login
```

This opens the console in your browser. Sign in, pick the orgs this computer should use, and the CLI stores one key per org in your OS keychain. If you have no org and no pending invite, `nodus login` creates your org for you, with the starter credit. On a machine without a browser, use [device login](https://nodus-platform-site.pages.dev/docs/guides/access/device-login/).

## Create another org

Terminal window

```bash
nodus create org acme --display-name "Acme Research"
```

You become its Owner. Every org starts with a project named `default`.

## Switch orgs

The console has an org switcher. On the CLI, each org is a context:

Terminal window

```bash
nodus config get-contexts
nodus config use-context acme
nodus get jobs --org acme          # one command in another org
```

API calls choose an org with the `Nodus-Org` header (the org name or id). Without it, a signed-in user acts in the org they used last.

## Org settings and activity

Admins can rename the org; its name (the slug in console URLs) stays the same:

Terminal window

```bash
nodus patch org acme --patch '{"displayName": "Acme Labs"}'
nodus get org acme -o yaml        # role, seats used and your org's enabled features
```

Admins and Owners see the org’s activity under **Settings → Activity**: sign-ins, key, member and invite changes, each with who did it and when, for the last day up to the last year, and **Export CSV** downloads what you see. The API serves it at `GET /apis/nodus.dev/v1/auditevents`, oldest first: `?action=auth.` selects sign-ins only, `since` sets the start, and a full page carries `metadata.continue` to pass as `continue` for the next one.