> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vegalake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform quickstart

> Sign in, establish your organization and workspace scope, and choose a first VegaLake workflow.

# Start with VegaLake

This dashboard-first path gets you to an implemented product workflow without assuming administrator access.

## Prerequisites

* A VegaLake account that is approved for an organization
* Membership in at least one workspace
* Permissions for the product resources you plan to view or create
* For API use, a bearer token or service-principal API key accepted by the selected operation

## 1. Sign in

Open the [VegaLake dashboard](https://dev.vegalake.com/) and sign in. If your account or organization is pending approval, finish that process before continuing. If your organization requires two-factor authentication, complete enrollment when prompted.

## 2. Select an organization

The organization controls membership, security policy, roles, groups, service principals, and workspace access. Navigation and actions are permission-aware; a missing menu item usually means your current identity lacks the corresponding permission.

## 3. Select a workspace

Product resources are workspace-scoped. Record the organization and workspace IDs if you plan to call an API because customer product paths include `org_id` and `workspace_id`.

## 4. Choose a supported first workflow

<CardGroup cols={2}>
  <Card title="Move data with VegaFlow" icon="diagram-project" href="/vegaflow/quickstart">
    Create a connection and cluster, configure a QuickFlow, and inspect its first run.
  </Card>

  <Card title="Explore metadata with VegaGraph" icon="share-nodes" href="/vegagraph/quickstart">
    Search for an entity, open Entity 360, and follow its lineage.
  </Card>
</CardGroup>

VegaDB is currently a preview. See [VegaDB availability](/vegadb/quickstart) instead of attempting an operational setup.

## 5. Automate through APIs

Read [API fundamentals](/api-reference/introduction) before using the generated reference. Match the service base URL, authentication method, organization/workspace path parameters, and permissions shown for the operation.

## If something is missing

Verify the selected organization and workspace first, then confirm your role or direct permission. See [troubleshooting](/platform/troubleshooting) for common authorization, validation, connection, cluster, run, and lineage symptoms.