# Open Cambium

Connect to an existing service and understand what sign-in and readiness each prove.

Open the address supplied by the workspace operator and sign in through its configured provider. Check the installed package separately when diagnosing an access problem.

## Before you begin

You need the workspace's browser address and an identity admitted by its sign-in provider. The operator controls that address and the provider configuration. The public service and a loopback address can reach the same installation through different network paths.

## Check the local package

**Inspect the installed command**

```bash
cambium --version
cambium --help
cambium serve --help
cambium mcp --check
```


The version identifies the executable. The MCP preflight checks its packaged fonts and drawing support. Neither command opens a project or proves a user's access.

## Enter the workspace

1. Open the workspace address and use the configured sign-in flow.
2. Open Projects. If there are no projects, the empty state says "No projects yet."
3. If the door refuses a read, retain its named resource and action and follow [Access and refusals](/cambium/operations/access-and-refusals/).

## Create a project

Choose New project and name it "Ward rounds walk". The item pane opens after creation.

**Project creation confirmation**

```text
Project Ward rounds walk created
```


## Add a task

Inside the project, choose New item and select Task. Name it "Check bed 4 obs".

**Task creation confirmation**

```text
Check bed 4 obs created
```


Board shows the task under "No status yet". With this single task, the heading is "No status yet 1". The item pane offers Take.

## Continue

Read [Conversations](/cambium/concepts/conversations/) or [connect an agent seat](/cambium/getting-started/agent-seat/).