CLion CMake Profile Build Directory Permission Boundary for Shared Locations

When working with multiple CMake profiles in CLion, each profile can be associated with a distinct toolchain and a build directory.

The IDE caches the CMake project model and may reuse an existing build directory when switching profiles, but it is unclear whether CLion prompts for confirmation before writing to that directory, especially if the directory is shared, read‑only, or intended for another toolchain.

This uncertainty leaves the permission boundary between profiles dependent on the operating system rather than an IDE‑enforced guardrail.

Does CLion ask the user before reusing an existing build directory when the target profile uses a different toolchain?
Is there a configuration option to force a prompt or to isolate build directories per profile?
How does CLion decide whether to reuse or create a new build directory when profiles differ in toolchain or generator?