Hi Cloudways team,

I'd like to report what I believe is a bug in the application SSH/SFTP user management UI.

When an admin creates an additional SSH/SFTP user under Application Settings, that user is only visible to the admin who created them. Other team admins cannot see the user in their control panel at all.

This is a problem because SSH/SFTP users are system-level accounts, they exist on the server and are shared infrastructure, not personal preferences tied to a specific Cloudways admin. In a team environment:

• Other admins have no visibility into what system users exist
• There's no way to audit credentials or identify who has server access
• If another team member needs SSH/SFTP access, they cannot see the existing user and may attempt to create a duplicate, causing silent failures or conflicts
• CI/CD pipelines that rely on a shared SSH user become opaque to anyone who didn't create it

We hit this directly when our CI/CD pipeline SSH user was created by one admin and a colleague couldn't see it when they needed to troubleshoot a deployment.

I raised this with support and was told it's "obvious" behaviour, but I'd respectfully push back on that. It's intuitive for personal SSH keys or per-user preferences to be scoped to an individual, but a system user that grants server-level access should be visible to all admins managing that application. Hiding it is a security and operational risk.

Requested fix: SSH/SFTP users created under Application Settings should be visible to all admins with access to that application, consistent with how other shared application resources are displayed.

Thanks for considering this, happy to provide further detail if helpful.