During the initial deployment of a Pure Storage FlashArray, the Implementation Engineer relies heavily on the puresetup account. This restricted, low-level shell is specifically engineered to handle local KVM tasks like installing the Purity operating system (pureinstall) and defining the baseline network configurations (puresetup newarray).
However, once the initialization script finishes successfully and the controllers reboot, the array transitions from an unconfigured piece of hardware into a fully functional, highly available clustered storage system. At this stage, the puresetup account has served its primary purpose.
To log back into the array via SSH or the web GUI to run final health validations (such as verifying cluster status with pureadm list or checking drive health with puredrive list), the Implementation Engineer must authenticate using the default administrative account: pureuser .
The pureuser account possesses full array administrator privileges and provides unrestricted access to the standard Purity//FA command-line interface. Using pureuser validates that the cluster's internal database is actively authenticating administrative sessions and confirms the array is ready to be handed over to the customer for production workload provisioning. (Note: After logging in as pureuser with the factory default password, a critical post-installation step is immediately changing that password to comply with the customer's security policies). The pureeng account (Option C) is a protected internal account reserved strictly for Pure Storage Support and Escalation Engineering.