The SAP Build Work Zone mobile app passcode policy can be configured in the SAP BTP subaccount mobile service. This is the SAP Mobile Services instance that is used by the SAP Mobile Start app as an https endpoint for authentication and routing. It provides an Admin Cockpit that allows administrators to access logs and configure specific settings for the app, such as the passcode policy. The passcode policy determines the minimum length, complexity, and expiration time of the passcode that users must create to access the app. By default, the passcode should have a minimum length of 8 digits/characters and it is possible to allow biometric authentication (for example, face ID, fingerprint) upon successful passcode creation. To access the SAP BTP subaccount mobile service, administrators need to have the MobileAdmin role assigned to them and construct the URL for the SAP Mobile Services Admin Cockpit. Reference:
Accessing SAP Mobile Services Settings
About the SAP Build Work Zone Advanced Mobile App

Workspace types are the categories that define the visibility and accessibility of workspaces in SAP Build Work Zone. There are three types of workspaces: public, private, and external. Public workspaces are open to all users of the system and can be discovered and joined by anyone. Private workspaces are restricted to invited members only and cannot be searched or accessed by others. External workspaces are created for external users who are not part of the system and can only access the workspace through a unique URL. Hidden and recommended are not workspace types, but workspace attributes. Hidden workspaces are those that are marked as hidden by the workspace owner or administrator and do not appear in the workspace list or recommendations. Recommended workspaces are those that are suggested to the user based on their profile, preferences, or activities. Reference:
What are SAP Build Work Zone workspaces? |Summer Tutorial Series |Lesson 3: Workspaces, section "Step 1 - Creating a new workspace"
[SAP Build Work Zone Administrator Guide], section "Workspaces"

The tasks of the cutover plan are executed in the Deploy phase of SAP Activate. The Deploy phase covers the implementation of the target SAP solution into a Productive (Go Live) state for use by the target business users; this is referred to as the Project Cutover1. The cutover plan describes all required tasks that must be performed before the go-live and needs to cover the following tracks: Infrastructure, System Design, Security, Data, and Training2. The cutover plan is refined and updated during or after the cutover simulation, which is also part of the Deploy phase1. The Deploy phase ends with the successful go-live of the SAP solution and the transition to the Run phase3. Reference: 1: SAP Project Manager's Guide to SAP Project Cutover 2: Cutover highlights for SAP S/4HANA New implementation 3: SAP Activate Elements and Phases

To implement SAP Build Work Zone, advanced edition in a multi-tier landscape, you need to create subscriptions in separate SAP BTP subaccounts. This is because SAP Build Work Zone, advanced edition is a subscription-based service that requires a dedicated subaccount for each tenant. You cannot create multiple subscriptions or service instances in the same subaccount, nor can you create multiple sites within a single subscription. Each subscription represents a separate site with its own content, configuration, and users. By creating subscriptions in separate subaccounts, you can align your SAP Build Work Zone landscape with your core business system landscape and enable content transport across different tiers. Reference:
Explaining the Planning Landscape for SAP Build Work Zone
Getting Started With SAP Build Work Zone