Caisey Docs

docs/getting-started.md

Getting Started with Caisey

User-focused walkthrough for signing in, enabling your workspace, and starting remote troubleshooting sessions.

Caisey lets you troubleshoot a remote computer from the browser while keeping the session, approvals, and audit trail in one place. Use this guide when you are signing in for the first time or trying to start your first remote session.

Before you start

Make sure you have:

  • a Caisey account,
  • access to the correct workspace or organization,
  • at least one endpoint installed or an installer command ready to run,
  • and permission from the device owner or customer to troubleshoot the machine.

If you are helping a family member, use the personal connection flow instead of an MSP/client installer.

First login checklist

  1. Sign in.
  2. Choose the right workspace from the account controls.
  3. Open Machines.
  4. Check whether the target computer is already listed.
  5. If it is not listed, add the device using the setup path that matches your workspace.
  6. Wait for the machine to show ready.
  7. Open the machine and start a chat.

Start your first session

Choose a ready machine from Machines, then open Chat. Ask for the outcome you want, not just the command you think should run. For example:

  • "Find out why QuickBooks will not open for the front desk user."
  • "Check why this Mac is running out of disk space."
  • "Review recent Windows update errors and summarize the likely cause."

Caisey may ask you to approve tool actions before it continues. Review those prompts carefully. If an action looks broader than the task requires, deny it and ask for a narrower approach.

What Caisey records

Caisey keeps operational records for accountability:

  • machine and session context,
  • chat messages and tool activity captured through the control plane,
  • permission decisions,
  • share-link activity,
  • and workspace audit events.

Live display and future audit records use common PII and secret redaction, but you should still avoid pasting passwords, private keys, customer secrets, or unrelated personal data into chat.

Good first-session habits

  • Confirm the device name before sending a prompt.
  • Ask Caisey to explain what it found before making changes.
  • Approve only the tool actions needed for the current task.
  • Use a shared snapshot only after reviewing the transcript.
  • Check the audit log when you need a record of what happened.