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

# Create and edit an App

> Start with an outcome or a template, then build and review your App before publishing.

You need edit access to the destination team or folder to create an App, and **Can edit** access to change an existing one.

## Create an App

<Steps>
  <Step title="Choose a destination">
    Open **Content** from your profile menu, choose the team and folder, then select **New → App**.
  </Step>

  <Step title="Describe the outcome">
    Enter what the App should do, check the suggested name, and choose **Create app**. For example:

    > Build a supplier order dashboard with filters for supplier and expected delivery date. Show overdue orders and let me open the related NetSuite record.

    Your brief is prepared in the editing conversation. Review it and send it when ready.
  </Step>

  <Step title="Build and review">
    Work with Erstan in the editing chat. Explain the intended users, required data, and which actions need approval. Review the preview and the [Data section](/apps/data) as the App takes shape.
  </Step>

  <Step title="Publish when ready">
    Test the screens, inputs, and permissions, then choose **Publish**. Saving a draft and publishing it are separate actions. See [Publish and share](/apps/publish-share).
  </Step>
</Steps>

To start from an existing design, choose **Start from a template** in the creation dialog or open **Library → Apps**. Review the template's setup requirements and select destinations you can access. An installed template can already have a published version; check its setup and status before sharing. See [Adding Apps](/marketplace/add-apps) for resource choices and included Agents.

## Edit an existing App

Open the App and choose **App actions → Edit App**. The editor has three sections:

| Section | What you do there |
| - | - |
| **App** | Preview the App and move between its pages. |
| **Code** | Inspect and edit its source files. Check the save status before publishing. |
| **Data** | Add or configure Data Sources, App resources, and actions. |

Use the editing chat to request changes in plain language. The ordinary **Open chat** conversation helps you use the App; choose **Edit App** for changes to its design, code, or data configuration.

## Preview changes

Draft changes are visible to authorized editors and do not replace the published App. Use the draft preview to check the layout, navigation, and reads before release. Draft previews can read real data with your access, but cannot perform production writes through the App bridge.

An **Unpublished changes** indicator means the working draft differs from the published version. A data refresh alone is not a code change.

<Tip>
  Ask for a small change, review its preview, then continue. For example: “Add an overdue-only filter and keep the existing columns.”
</Tip>

## Pages, files, and history

Use **Settings** to configure available page and presentation options. Native Sheet and Database pages keep the permissions of their original resources. Page configuration changes belong to the draft until published.

**App actions → Revisions** lets editors inspect the draft, published version, and earlier revisions. **Open folder** takes you to the source files in Content. Use **Restore revision** only after reviewing the version you intend to make active.

## If something fails

Check **App activity** for the failed read or action. For a save error, use **Retry save** and confirm it succeeds before publishing. If a connection is missing, reconnect it and retry the read. If data access is denied, check both App access and access to the underlying resource with its owner.