# dcupl Console

The dcupl Console at [console.dcupl.com](https://console.dcupl.com) is where a
project's files live: models, data, the loader configuration and scripts. You
run the project as an application in the browser, deploy workflows and
REST API (RAPI) instances from it, and your own app loads the same files with
the dcupl SDK. How the console fits next to the SDK and the CLI is on
[Architecture](/learn/concepts/architecture).

## Where things are

The sidebar of a project:

- **Applications** runs an application or a quick run and opens it in the
  [five views](/console/applications#the-five-views-on-a-run), among them the
  **Data Explorer** and the **Quality Analyzer** ([Applications](/console/applications)).
  Its **Connect** tab inspects your own running app
  ([Debugging with Console](/sdk/guides/debugging)), and **Loader
  Configuration** lists what `dcupl.lc.json` declares
  ([Loader configuration](/console/loader)).
- **Workflows**: workflow templates, deployments and runs
  ([Workflows](/console/workflows)).
- **REST APIs**: API templates and deployed instances
  ([REST APIs](/console/rapi), [MCP endpoint](/console/rapi/mcp)).
- **dcupl Cloud → Version Manager**: the project's file versions (see
  [File versioning](#file-versioning)).
- **Project Settings**: **General** (name and Project ID), **Members**
  (see [Roles](#roles)), [Sources](/console/sources),
  [API Keys](/console/api-keys), **Billing** (owners only) and
  [Reporting](/console/workflows/reporting).

The file editor sits on the right-hand rail; its **+** menu opens
[Import Data](/console/data-import) and [Create Model](/console/models).
Viewers see only Applications and Project Settings → General. **Workflows**
and **REST APIs** are on for new projects; if either entry is missing, ask your
dcupl contact to turn it on for your project.

## Getting started

New to the console? [Your first console project](/console/getting-started)
walks through it in five steps: create a project, import a CSV, check the
inferred model, run the application and load it from your code.

Coming from the previous console? During the transition, **Previous console**
in the account menu opens it at `v1.console.dcupl.com`.

## By role

- **You build an app on console data.** Read [Applications](/console/applications)
  and [Loader configuration](/console/loader), pick a key on
  [API keys](/console/api-keys), then load the project from code:
  [Load from the console](/sdk/guides/load-from-console) and the
  [Console + Loader setup](/sdk/setup-options#console-loader).
- **You manage the data.** [Importing data](/console/data-import),
  [Models in the Console](/console/models), [Sources](/console/sources) and,
  for imports on a schedule, [Workflows](/console/workflows).
- **You serve data to other systems or to agents.** [REST APIs](/console/rapi),
  [scripted endpoints](/console/rapi/scripted-endpoints) and the
  [MCP endpoint](/console/rapi/mcp) for AI agents, where it is turned on.
- **You run the project.** Members and roles below, [API keys](/console/api-keys)
  and [Reporting](/console/workflows/reporting).

## Key concepts

### Projects

A project holds models, data files, scripts, workflows, REST API templates and
variables (named values for workflows; a new project starts with
`dcupl_version` and `dcupl_api_key`). New projects are private: the CDN serves
their files only to requests that carry one of the project's
[API keys](/console/api-keys). Browser apps use the seeded **Browser
(read-only)** key.

### File versioning

Project files live in named **versions**, managed under **dcupl Cloud →
Version Manager**:

- **draft**: the version every project starts with and the console's default
  source. The SDK loads it unless you pass another `version`.
- **Other versions** (for example `production`): created by copying an existing
  version, served from the CDN the same way, and selectable as a
  [source](/console/sources).

### Roles

You sign in with email and password, or with Google or GitHub. What you can do
in a project depends on your role in it; owners invite members under
**Project Settings → Members**.

| Role       | Permissions                                                                       |
| ---------- | --------------------------------------------------------------------------------- |
| **Owner**  | Full access, plus inviting members, renaming or deleting the project, and billing |
| **Editor** | Create, edit, deploy resources                                                    |
| **Viewer** | Read-only access to project resources                                             |

## Next steps

- [Your first console project](/console/getting-started) — From an empty account to an app that loads your data
- [Load from the console](/sdk/guides/load-from-console) — Connect the SDK to your console project
- [Workflows](/console/workflows) — Build automated data processing pipelines
- [REST APIs](/console/rapi) — Deploy and manage REST APIs