Build an app
You work on a project: the conversation, files, and preview. Publishing makes a version available as an app that people can open. Later edits stay in your project until you publish again. Key concepts explains the terms you’ll see in Wisty, including connected orgs, host orgs, and sharing.Build your first app
Connect an org, build an Opportunity list, and open the published result.
Start from a template
Preview a finished layout and adapt it to your org.
Describe what you need
Example prompts, object mentions, and reference images.
Work on a project
Find your way around the builder and restore saved work.
Edit without AI
Change text and styling in the preview. No credits used.
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.Install Wisty
Add the package, assign builders, and show the Wisty tab.
Connect a host org
Let people build and use apps inside Salesforce with their Salesforce login.
Manage builders and viewers
Building access, app sharing, and Salesforce data permissions are separate
controls.
Open an app someone shared
Share and open 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.How Wisty uses your data
What goes to the AI, what stays in Salesforce, and how apps access records.
Control Salesforce access
Choose which kinds of requests your app can make.