> ## 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. # Key concepts > How projects, apps, and Salesforce connections fit together in Wisty. You build in a project connected to your Salesforce org. When it's ready, you publish a version as an app and choose who can open it. ## Build and publish | Term | What it means | Learn more | | ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | | **Project** | The work you edit: your conversation, source files, live preview, and saved versions. Open a project to keep building or change an existing app. | [Work on a project](/docs/building/projects) | | **App** | The published result people can open and use. To update it, edit its project and publish another version. | [Share and open apps](/docs/publishing/share-apps) | | **Version** | A saved snapshot of your project. Restoring a version changes your working project; publishing a version changes the live app. | [Restore an earlier version](/docs/building/projects#restore-an-earlier-version) | | **Publish** | Make a version of your project available as the live app. Publishing determines what viewers run, while [sharing](#sharing) determines who can open it. | [Publish and update an app](/docs/publishing/publish) | | **Sharing** | The audiences you allow to open an app, such as your Wisty team or users in a host org. Each viewer's Salesforce permissions still control the records they can access. | [Choose who can open an app](/docs/publishing/share-apps#change-who-can-open-an-app) | | **Template** | A ready-made layout you can use to start a project. Its demo uses sample data; Wisty adapts your project to your Salesforce org when you describe what you need. | [Start from a template](/docs/getting-started/templates) | ## Connect Salesforce | Term | What it means | Learn more | | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | | **Connected org** | Your personal Salesforce connection for building and using apps in one Wisty workspace. Wisty accesses Salesforce through it using your Salesforce login's permissions. | [Connect Salesforce](/docs/getting-started/connect-salesforce) | | **Host org** | A Salesforce org linked to your Wisty team where users build and use Wisty apps with their Salesforce login. Users with builder access can create projects and publish apps directly inside Salesforce. | [Connect a host org](/docs/salesforce-setup/connect-host-org) | | **Org knowledge** | Saved guidance Wisty uses when building, such as custom field conventions or business rules. Save it on the connected org or host org your builders use. | [Add org knowledge](/docs/building/org-knowledge) | The same Salesforce org can be both a connected org and a host org. Your connected org is your personal connection; the host org is the team link that makes Wisty available to that org's users. Projects created inside Salesforce stay tied to that Salesforce org. You can't switch them to another org, and their published apps can be shared only within that org. When you build from your Wisty account, you can switch between connected orgs and share apps with your team or its host orgs. ## Workspaces A workspace is your Wisty team. Its projects, connected orgs, credits, and subscription stay inside it. If you belong to more than one, open the account menu at the bottom of the sidebar and choose **Switch workspace**. Wisty reloads into the workspace you choose. Connected orgs don't carry over between workspaces. To use the same Salesforce login in a second workspace, connect it there too. Salesforce then issues a separate authorization for that workspace. Open **Manage team** from the account menu to see members or leave; admins can also invite people and delete the workspace. Deleting a workspace removes its projects, published apps, and connected orgs. Your other workspaces aren't affected. ## Open and use apps | Term | What it means | Learn more | | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | **Builder** | A person who creates and edits projects and publishes apps. Building access comes from Wisty team membership or Salesforce permissions, depending on where they work. | [Manage building access](/docs/salesforce-setup/control-access#choose-the-right-access-control) | | **Viewer** | A person who opens and uses a published app. The app uses that viewer's Salesforce permissions when accessing records. | [Help viewers open an app](/docs/publishing/share-apps) | | **Salesforce Web** | A way to open shared apps outside Salesforce using **Sign in with Salesforce**. An admin enables it on the host org before people can use these links. | [Turn on Salesforce Web links](/docs/salesforce-setup/connect-host-org#turn-on-salesforce-web-links) | | **Embed ID** | The ID that identifies your published app when you place it in Salesforce's **Wisty App** component. It stays the same when you publish updates. | [Copy the Embed ID](/docs/publishing/embed-in-salesforce#copy-the-embed-id) | | **Record ID** | The Salesforce ID for one record, such as an Account or Opportunity. An Embed ID chooses the app to display; a record ID tells a record-specific app which record to use. | [Build for a specific record](/docs/publishing/embed-in-salesforce#build-for-a-specific-record) | | **Preview record** | A record ID you paste into the builder to test a record-specific app. The published app receives the current record's ID from its Salesforce record page, independently of your test record. | [Set a preview record](/docs/publishing/embed-in-salesforce#set-a-preview-record) |