Hello, thank you for your reply. We identified that the issue was caused by the developer's Chrome browser auto-saving the password settings. Accessing the studio in Safari resolved the issue. Nonetheless, this remains an interesting research topic for future reference.