Link a Salesforce org so people can build and use Wisty apps with their Salesforce login.
Open Host orgs, then Add host org, to let people build and use Wisty apps inside Salesforce. You need to be a Wisty team admin, and Wisty must be installed in that Salesforce org.A connected org is your personal Salesforce connection for building and using apps in the Wisty web app. A host org links a Salesforce org to your Wisty team. Its users can open shared apps and, with builder access, create projects and publish apps inside Salesforce. Connecting your own Salesforce login doesn’t create that team link.
In the Wisty web app, open Host orgs and click Add host org.If the package isn’t installed, use Install package in the dialog and complete installation.
2
Copy the activation code
Click Copy code. The activation code is single-use and expires after an hour.
The dialog waits while you paste the code in Salesforce, and shows how long the code remains valid.
3
Open Wisty in Salesforce
In Salesforce, open Wisty from the App Launcher. Complete Connect Wisty if Salesforce asks you to approve access.
4
Paste the code
On Connect this Salesforce org to Wisty, paste the code and click Connect.
The Wisty tab in Salesforce shows this one-time setup screen until the org is linked.
5
Check the link in Wisty
Return to Wisty. The dialog closes after the code is accepted, and the org appears under Host orgs.
Each host org shows its pinned apps and whether sharing is on.
If the code expires, click Generate new code and use the new one. If the Wisty tab is missing, check the package and tab visibility before generating another code.
Give the people who should build apps the Wisty Builder permission set. They can then open the Wisty tab, describe what they need, and generate, refine, and publish an app using their Salesforce login.Each project created this way stays tied to the Salesforce org where it was created. For example, a project created in ACME Prod always uses ACME Prod. You can’t switch it to another org, and its published app can be shared only within ACME Prod. Opening the app through a Salesforce Web link doesn’t change that association.Projects start private. Builders can generate and publish apps for their own use without enabling org-wide sharing.
Sharing is optional and starts off for a new host org. Leave it off if builders should generate and publish apps only for their own use.Turn on Sharing to let app owners share their published apps with other users in the same org. It also lets your Wisty team share apps created in the Wisty web app with this org. Turning it on doesn’t share apps automatically: each app owner chooses which published apps to share.To allow sharing:
In the Wisty web app, open the org under Host orgs.
Select the Sharing tab.
Turn on the switch. The status changes to Sharing on.
With sharing enabled, an app owner can share their published app with this host org. Have another user in the org open the Wisty tab in Salesforce to check the result. They can find the shared app under All apps and open it using their own Salesforce permissions.You can turn sharing off again without removing anyone’s builder access.
Salesforce Web lets people open shared apps from a link outside Salesforce. It’s off by default, and you can leave it off if everyone opens apps inside Salesforce.
Under Host orgs, open the org and select Salesforce Web.
Turn on the switch. The status changes to Salesforce Web on.
Viewers click Sign in with Salesforce and use a login from the linked org. Logins from other orgs are rejected.Turning this switch off immediately blocks Salesforce Web access, including existing sessions. Wisty then removes the stored Salesforce Web sessions and credentials. The in-Salesforce experience can keep running independently.
The host org’s Org knowledge tab holds instructions used when Wisty builds projects for that org. Use it for business definitions, naming conventions, and other context that applies across projects. See Add org knowledge for examples and how these instructions are used.
