Give a developer access without sharing your primary account password Print

  • developer, access, permissions, account
  • 0

Quick answer

Give each person the access needed for the task through a supported user, key, or integration credential. Keep your primary billing password private. A dedicated SSH key can be revoked separately, but it normally has the permissions of the cPanel account it logs in to.

Choose the access method

For WordPress content, create an individual user with a suitable CMS role. For a narrow reviewed integration, consider an appropriate application credential. For file/code work on hosting, a separate public SSH key can identify the person or device.

An SSH key does not automatically restrict access to one domain or folder inside a shared cPanel account. If the account contains unrelated sites or sensitive files, discuss the exposure and a suitable separation method before granting access.

Grant and record access

  1. Define the website, task, permitted changes, and access duration. Identify the account owner who can revoke it.
  2. Use the real service’s invitation/user interface or public-key authorization controls. Do not send a primary password, private key, or token in an ordinary message.
  3. Check what the identity can actually reach. Confirm that an advertised role or token scope fits the task before relying on it.
  4. Keep a record of the person/device, credential purpose, and expiration/review point. Keep the owner’s recovery access working.
  5. Review the completed work and revoke access that is no longer needed, including separate CMS/API credentials.

If narrow access is unavailable

Ask support about an isolated account, staging arrangement, or another supported approach. A written prompt telling an AI tool to stay in one folder is not a technical permission boundary.

Related help

Official references

Last content review: October 31, 2026. Check the version and features available in your own account.


Was this answer helpful?

« Back