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

# Overview

> Build an app for your team on top of the Salesforce objects you already have.

Describe the job your team needs to do, then refine the result in a live preview. Start with [Build your first app](/docs/getting-started/quickstart) for a complete example, from an Opportunity list to a published app.

## Build an app

You work on a [project](/docs/getting-started/key-concepts#project): the conversation, files, and preview. Publishing makes a version available as an [app](/docs/getting-started/key-concepts#app) that people can open. Later edits stay in your project until you publish again.

[Key concepts](/docs/getting-started/key-concepts) explains the terms you'll see in Wisty, including connected orgs, host orgs, and sharing.

<Columns cols={2}>
  <Card title="Build your first app" icon="rocket" href="/docs/getting-started/quickstart">
    Connect an org, build an Opportunity list, and open the published result.
  </Card>

  <Card title="Start from a template" icon="layout-template" href="/docs/getting-started/templates">
    Preview a finished layout and adapt it to your org.
  </Card>
</Columns>

Already building? These pages cover the editor itself.

<Columns cols={3}>
  <Card title="Describe what you need" icon="message-square" href="/docs/building/describe-what-you-need">
    Example prompts, object mentions, and reference images.
  </Card>

  <Card title="Work on a project" icon="pencil-ruler" href="/docs/building/projects">
    Find your way around the builder and restore saved work.
  </Card>

  <Card title="Edit without AI" icon="mouse-pointer-click" href="/docs/building/editing-without-ai">
    Change text and styling in the preview. No credits used.
  </Card>
</Columns>

## Set up Salesforce for your team

A Salesforce admin installs the package once per org. A Wisty team admin then links the org so people with builder access can create apps inside Salesforce, and viewers can open shared apps. They use their Salesforce login.

<Columns cols={3}>
  <Card title="Install Wisty" icon="package" href="/docs/salesforce-setup/install">
    Add the package, assign builders, and show the Wisty tab.
  </Card>

  <Card title="Connect a host org" icon="link-2" href="/docs/salesforce-setup/connect-host-org">
    Let people build and use apps inside Salesforce with their Salesforce login.
  </Card>

  <Card title="Manage builders and viewers" icon="lock" href="/docs/salesforce-setup/control-access">
    Building access, app sharing, and Salesforce data permissions are separate
    controls.
  </Card>
</Columns>

To connect your own Salesforce login to the Wisty web app, follow [Connect Salesforce](/docs/getting-started/connect-salesforce).

## Open an app someone shared

[Share and open apps](/docs/publishing/share-apps) covers the Wisty workspace, the Wisty tab inside Salesforce, and shared web links. Salesforce viewers use their own Salesforce login and don't need a Wisty account.

## Understand data access

Wisty uses Salesforce metadata to generate your project. It doesn't retrieve Salesforce records for generation. The running app accesses records using the Salesforce permissions of the person using it. Messages and images you add to the conversation are also supplied to the generating model.

<Columns cols={2}>
  <Card title="How Wisty uses your data" icon="shield-check" href="/docs/security/data-handling">
    What goes to the AI, what stays in Salesforce, and how apps access records.
  </Card>

  <Card title="Control Salesforce access" icon="sliders-horizontal" href="/docs/building/salesforce-access">
    Choose which kinds of requests your app can make.
  </Card>
</Columns>

If you're stuck, [Fix common problems](/docs/help/troubleshooting) gives you a next step for connection errors, missing access, and apps that won't open.