Skip to main content
Open Install package from Wisty’s Salesforce connection dialog to add Wisty to your org. You need Salesforce admin access, and you only install it once per org. The package includes Wisty’s External Client App, the Wisty tab, the Wisty App component for Lightning pages, and the Wisty Builder permission set. It adds no custom objects.

​
Install the package

1

Open the installer from Wisty

In Wisty, open Connected orgs and start Connect Salesforce org. A Wisty team admin can also start from Host orgs, then Add host org.In step 1 of the dialog, click Install package.
2

Choose the org type

Choose Production, Sandbox, or Custom domain to match the org where you’re installing. For a custom domain, enter the My Domain name shown before .my.salesforce.com.
3

Install in Salesforce

Click Install in Salesforce and sign in as a Salesforce admin. Choose Install for Admins Only and complete the Salesforce installer.
4

Return to Wisty

When installation finishes, click Continue in Wisty to return to setup.
Choose Install for Admins Only unless you’ve deliberately chosen specific builder profiles. Install for All Users grants the package’s Wisty: Build Apps permission to every profile, allowing those users to build and spend credits. Viewers don’t need this permission.
Install for Admins Only grants the builder permission to the System Administrator profile. Other builders can receive it through the permission set below. If you already installed for all users, review Custom Permissions on those profiles and remove Wisty: Build Apps where it isn’t needed. If you’re building from your Wisty account, continue with Connect Salesforce. To let people use Wisty inside Salesforce, complete the access steps below, then connect the host org.

​
Assign builders

Give this access only to people who should create projects and publish apps inside Salesforce.
  1. In Salesforce Setup, open Permission Sets.
  2. Select Wisty Builder.
  3. Click Manage Assignments and add the users who should build.
  4. Have those users open Wisty again to pick up their new role.
The permission set contains Wisty: Build Apps and makes the Wisty tab visible. It doesn’t grant access to Salesforce records. Each person’s existing Salesforce data permissions still apply. If you use your own permission sets, add the Wisty: Build Apps custom permission there instead. Manage builders and viewers explains how this differs from Wisty web team membership.

​
Show the Wisty tab to viewers

Viewers don’t need Wisty Builder. They do need tab visibility to open the app launcher, because an admin-only install leaves the packaged tab hidden from other profiles. Choose one way to make the tab available:
Open Setup, then Profiles. Select the profile, open Object Settings, select Wisty, and set Tab Settings to Default On.
People opening an app directly on a Salesforce page don’t need the Wisty tab. They still need permission to use Wisty’s Salesforce External Client App and access to the shared app.

​
Finish setup and check a first launch

Connect the org as a host org to link it to your Wisty team and enable sharing. Then have a viewer open Wisty from the Salesforce App Launcher. With the default All users can self-authorize policy, they see Wisty isn’t connected yet the first time. They click Connect Wisty and approve access in Salesforce. The approval window closes and Wisty opens in the original tab. A viewer should reach the app launcher. A builder should also have access to project creation. If the tab or builder controls are missing, see Fix common problems.

​
What Salesforce authorization allows

Wisty ships a Salesforce External Client App. It requests these OAuth scopes: The custom-permissions scope is required for Salesforce builders. If Wisty can’t confirm the permission, it refuses generation and publishing. How Wisty uses your data explains what reaches the generating AI and what happens only when an app runs.

​
Pre-authorize users

Pre-authorizing lets you choose who can open Wisty inside Salesforce, and those people skip the Connect Wisty step.
1

Switch the policy

Open Setup, then External Client App Manager, and select Wisty’s app. Under Policies, open OAuth Policies and set Permitted Users to Admin approved users are pre-authorized.
2

Choose who gets access

The profile and permission-set pickers appear under App Policies once the policy is switched.
Move each profile that should open Wisty to Selected Profiles and save.
Include your builders. Opening Wisty and building are separate grants: builders need this access and Wisty Builder.
Salesforce doesn’t let a permission set from a managed package be selected here. Picking Wisty Builder fails with We couldn't save the external client app and state=MANAGED_INSTALLED. Don’t clone Wisty Builder to get around it. A clone carries Wisty: Build Apps, so everyone you give it to can build and spend credits.
Changing this policy doesn’t by itself remove earlier authorizations. To remove existing access, review and revoke the user’s authorization too. See Manage builders and viewers.