Unity Cloud Loops: setup without surprise charges

You do not need Unity Build Automation for Local Loops. Connect it only if you want Unity validation while your computer and Unity Editor are off. Avori's Check Connection action is read-only: it does not start a build or consume Unity build minutes.

1. Prepare source control. Connect the Unity project to a GitHub repository available to both Avori and Unity Build Automation. Confirm that ProjectSettings/ProjectVersion.txt exists and that generated folders such as Library, Temp, Logs, and Builds are ignored. Avori packages the exact approved local snapshot—including eligible uncommitted edits—into an isolated validation branch; it never asks Unity to validate an older base commit.
2. Create a dedicated build configuration. In Unity Cloud, open the correct organization and project, then open DevOps → Build Automation → Configurations. Connect the repository and create a configuration named Avori Validation. Select the repository branch, Unity project subfolder, target platform, and the same Unity version shown in ProjectVersion.txt. Disable automatic source-control builds so one Avori request does not create a duplicate build.
3. Create limited access. Create a dedicated Unity service account with only the project-level access needed to read and run the selected Build Automation configuration. Create its supported long-lived bearer token. Never enter a Unity password, payment method, organization-owner credential, or signing secret into Avori.
4. Set Unity's spending boundary. In Unity Build Automation, open Settings → Build Consumption, review the organization's current included allocation, and set the spending cap you are comfortable with. Avori cannot create, raise, or bypass this cap. Check Unity's current consumption documentation because allocation and pricing can change.
5. Connect Avori. In Avori, choose the Unity project, then open Settings → Cloud → Unity Cloud Connection. Enter the Unity organization ID, Unity project ID, the Avori Validation configuration ID, and the dedicated service-account token. Select Save Connection. Connect the matching GitHub repository when prompted in the Dashboard. Avori encrypts credentials in tenant-scoped secret storage and never displays them again.
6. Check access safely. Select Check Connection. A successful check confirms access to the selected configuration and says No build was started. If it fails, verify the three IDs, token status, project-level role, and configuration access. Do not paste the token into a support ticket.
7. Choose the execution location. Start the Loop from the same Avori chat. Leave Continue when this device is off unchecked for local execution. Enable it for an Avori Pro Cloud Loop. If Unity validation is unavailable or has not been explicitly authorized, Avori returns a reviewable change bundle labeled Unity validation pending; it must not claim the project compiled, imported, tested, or built.

If you do not have Unity Build Automation, keep the Loop local or accept a cloud-edited change bundle marked Unity validation pending and validate it after reopening the project locally. Avori never requires you to buy or enable a Unity subscription merely to connect your Avori account.