When you're ready to share your work with others, you use the Share option to generate a URL for your application that you can share with your team and ask for feedback. Then when you're done making changes, you use the Publish option to deploy the application and make all your changes public.

The Share option, which you can find in the menu in the upper right corner, deploys a visual application to your environment's Visual Builder instance—but without pushing your code to the project’s Git repository. As project members, you and your teammates can directly access the shared visual application from the Deployments tab of the Environments page, but other users need the shared application URL to access the application. See Share a Visual Application.

After the application has been tested thoroughly and you're ready to make your changes public, you use the Publish option in the header to deploy your visual application. A successful publish merges your changes to the project's default branch (usually, main) and triggers the build and deploy jobs in the pipeline set up when your visual application's project was initially created. This pipeline deploys your visual application (with the applications it contains) to your environment's Visual Builder instance. See Deploy a Visual Application.

For deployment to be successful, your organization must have purchased a separate Visual Builder instance that your organization administrator has set up for you to deploy applications from your VB Studio instance. This includes entering authorization details in the Deploy step of your visual application's deployment job to permit access to the Visual Builder instance. See Configure the Deployment Job in Administering Visual Builder Studio.