Especially if you offer the creation of websites as a service, the question arises whether you a) develop the website under your own account and transfer it to the customer's account after completion or whether you b) work on the customer's account right away (of course with the customer's consent). Both is possible of course, but point a) is obviously the more favorable way for a service provider. And in "Cheetah" this is extremely easy! The condition is, of course, that the client of the website also has a Builderall account, which is uniquely identifiable by the e-mail address used for its registration. This e-mail address must be known to you. Let's assume you have completed a website on behalf of a customer and want to make it available to him. To do this, switch to the website view in "Cheetah" and open the 3-point menu there. There you will find the menu item "Transfer", which you now click on:
Now all you need to do here is enter your client's email address (i.e. the one they are registered with at Builderall) and select one of the two transfer options. In the first case ("Transfer only"), the entire website will be transferred and then deleted from your website view (usually the less favorable case, as you will then no longer have access to it). In the second case, on the other hand, only a current copy of the website is transferred. This method is also great for sending an intermediate status of your work to your client (or whoever).
Only when a website has been explicitly published in "Cheetah" can it be accessed anywhere in the world via its URL. Such a publication is therefore (test purposes once excluded) usually only meaningful when the web project has reached a certain state with which one can go to the public. However, you can work on your website at any time, even if it is not yet publicly accessible.
The functions for "Publish" or "Unpublish" can be found in the website view in the 3-point menu of the website or in its page view in the main menu of the editor (buttons "Publish", "Unpublish" and "Re-publish" depending on the respective context).
Note: If you are working on an already published website (which will usually be the case), then you have the option when saving your changes to decide whether the changes should only be saved for the time being (i.e. without the changes having any effect on the already published website) or should also be published immediately. Especially to avoid bugs or "optical effects" that could possibly unsettle your website visitors, you should only publish your changes when they are functionally and visually error-free (don't forget the mobile version!).