Give Developers Only the Access They Need

Our earlier guide covers inviting a developer without sharing your hosting password. This post is the next layer: you choose what they can touch.

When you invite or approve access, pick capabilities such as files, FTP, databases, email accounts, DNS, SSL, backups, scheduled tasks, domain view, usage and logs, or applications tools. Start narrow. Add more only when the job needs it.

Some capabilities can change live traffic or read sensitive data: databases, email accounts, DNS, backups and applications tools. The invite screen marks those so you pause before enabling them for a short content tweak.

Billing, plan changes and cancellation stay with you as the account owner. Revoke the invite or grant when the project ends so access does not linger.

• Invite by email from the service Developers panel.
• Enable only the capabilities the job needs.
• Treat databases, DNS, email and backups as high risk.
• Revoke when the work is finished.

Sometimes a developer needs the site installer inside the control panel for a limited window. That path is broader than a single capability. You turn it on for a set number of days, confirm you understand it opens full panel access for that window, and it expires when the date passes.

Use timed installer access for setup bursts. Prefer scoped capabilities for day-to-day edits. Never email your own Client Area password as a shortcut.