Remove builds from players
Overview
The Remove builds from players feature provides Administrators with the ability to remotely uninstall specific game builds from a user's machine. This tool is primarily used when revoking access to Private Channels, ensuring that sensitive or outdated builds are removed from local storage once a user's permission to access that content has ended.
Functional Scope
To ensure security and optimize local storage, the Remove builds from players feature enables an automated, silent cleanup of local build files.
-
Access: This capability is restricted to Administrators managing Private Distribution or Playtest channels.
-
Automatic Cleanup: When you revoke a user’s access, the system is configured by default to trigger a remote uninstallation of the associated build.
-
Administrative Control: You maintain full flexibility to revoke access without deleting files by simply unticking the "Remote uninstall the build from user’s machine" option during the confirmation process.
-
Connectivity Requirement: For the remote uninstallation to execute, the target user must be online and logged in to the ADT Hub.
Administrator Guide: How to Remove Builds
Follow these steps to revoke access and trigger a remote uninstallation:
-
Access the Channel: Log in to the ADT Hub as an Administrator and navigate to your desired Game.
-
Open Settings: Select the specific Private Channel (Distribution or Playtest) and click the Channel Settings (gear icon).
-
Manage Access: Switch to the Access tab to view the list of authorized users.
-
Revoke Access: Identify the user or user group and click the Trashcan Icon.
-
Confirm Uninstallation: A confirmation pop-up will appear with the checkbox: "Remote uninstall the build from user’s machine".
-
To Delete Files: Leave the box ticked (default) and click Delete.
-
To Keep Files: Untick the box if you only wish to remove their access to future updates without deleting their current local build.
-
User Experience & FAQ
Q: Does the user receive a notification when a build is remotely deleted?
A: No. The uninstallation occurs silently in the background. The process triggers once the user logs into the ADT Hub and opens the relevant namespace. The only visible change for the user is the removal of that private channel.
Q: Does the user need to be online for the remote delete to work?
A: Yes. The user must be connected to the internet and logged in to the Hub for the system to detect and trigger the file deletion.
Q: What if a user needs to redownload a deleted build?
A: Because their access was revoked during the deletion process, the user must contact the Channel Administrator to have their access granted again before they can view or download the build.
Q: Is this feature applicable to Public Channels?
A: No. This feature is currently limited to Private Distribution and Playtest channels to protect confidential project builds.