> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.cloudraker.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server. # Quickstart In this guide you sign in, open a space, upload documents, run a playbook, and approve the drafts that the AI assistant produces. Each step links to the page that covers the detail. **The assistant drafts; you decide what to approve.** The agent and automated steps never commit data on their own. They produce drafts: proposed records, filled forms, and generated documents. You review, edit, approve, or reject before anything becomes real data. ## What you'll need * A **work account** in a CloudRaker organization. Your company's identity provider handles sign-in. * A **space** to work in, or permission to create one. * A few documents to work on, and a playbook that your space type makes available. New to the terms? Read [Key concepts](/workspace/get-started/concepts) for the glossary. Read [What CloudRaker is](/workspace/get-started/introduction) for the big picture. Admins who set up an organization for the first time start with the [Administration](/workspace/admin/organization-settings) section, then space types, playbooks, and actions. This quickstart assumes those exist. ## The happy path #### Sign in Go to [app.cloudraker.com](https://app.cloudraker.com) and sign in with your **work account**. Your organization's identity provider handles the login. There is no CloudRaker password. The hosted sign-in screen with email, Google, and Microsoft options #### Open or create a space A **space** is the workspace for one body of work. It holds the files, records, and people for that job. In the sidebar, find the **Spaces** group. Spaces are listed under a collapsible header for each **space type**. Expand one and click a space to open it. To start fresh, click **New space** and create one from a space type. The sidebar Spaces group with the Accounts payable space type expanded to show a space, and the New space link below The space type you pick matters. It decides which playbooks and actions are available inside the space. See [Create a space](/workspace/spaces/create-a-space) and [Space types](/workspace/spaces/space-types). #### Upload your documents Open the space's **Files** tab. Drag files onto the page, or use **Upload files** to pick them. The app processes uploaded files automatically. There is nothing to trigger. Let processing finish before you run a playbook over the files. See [Files](/workspace/spaces/files). The space Files tab listing uploaded and processed invoice PDFs with their sizes and upload times #### Run a playbook Open the space's **Playbooks** tab and click **Run playbook**. Pick a playbook that fits the work. Choose which files the run may use: **all files** in the space or a **selected** subset. Then click **Start run**. The run starts and the run page opens. Only playbooks that your space type makes available appear in the picker. See [Run a playbook](/workspace/playbooks/run-a-playbook). The Run playbook screen for the 'Invoice intake' playbook, showing its tasks, actions and approvals, and the File access choice between all files in the space and selected files #### Follow the run and approve On the run page, the agent works through the playbook's tasks on its own. It **pauses at approval cards** when it has drafts for you. Open a card to review the assistant's drafted values. When the extraction action has **grounding** turned on, extracted values link back to their exact source. Grounding is off by default. The source is a page and region in a PDF, or a timecode in audio. Use the links to confirm each value before you approve. Then: * **Approve** the drafts you trust. * **Reject** anything wrong, with a note that says what to fix. Your approval turns a draft into real data. See [Approvals and steering](/workspace/playbooks/approvals-and-steering). A playbook run paused at an Approval needed card for a drafted consult note, showing the agent's rationale, its source recording, and inline Reject and 'Approve & resume agent' controls Rejecting sends the work back. Write a specific note so the next attempt fixes the right thing. #### See your results Approved extraction records land in the space's **Data** tab. There you can filter, sort, and reuse them. Generated files, such as filled forms and produced documents, land back in the **Files** tab. See [Records](/workspace/data/records). The space Data tab showing the Invoice record type's table with two approved invoice records as rows ## Where to go next #### [Key concepts](/get-started/concepts) Plain-language definitions of every term you will meet in CloudRaker. #### [Approvals and steering](/playbooks/approvals-and-steering) Go deeper on reviewing drafts, approving, and steering a run. #### [Run a playbook](/playbooks/run-a-playbook) More on starting runs and choosing which files a run can use. #### [Spaces](/spaces/overview) See how a space is organized across its Files, Playbooks, Data, and other tabs.