Give each developer their own login instead of sharing your ArkHost password or two-factor codes. First decide whether they need the ArkHost Client Area at all: editing website content may only require a separate user in your website's CMS.
Invite a Client Area user
Sign in as the account owner and select the correct account if you manage more than one. Open User Management from your account menu. If the option is missing, contact support; do not share your owner login as a workaround.
Under Invite New User, enter the developer's email address. Change the preselected All Permissions option to Choose Permissions. Read each permission's description and select only what the agreed work requires. Leave billing, ordering, domain changes and other unrelated access unselected. Then choose Send Invite.
The developer must open the invitation and accept it using their own login, or create a user if needed. Keep the invitation link private. After acceptance, return to User Management and verify the listed user and permissions: the login email used to accept an invitation can differ from the address you invited. Ask the developer to enable two-factor authentication on their own login.
Understand the access you are giving
These permissions control access to the ArkHost account; do not assume they restrict someone to one selected website, domain or support conversation. Service access may expose management actions or panel sign-in, so review its scope before granting it. If you need narrower access, ask support which approach fits the service.
An invitation does not transfer account ownership, change the domain registrant or hand over billing responsibility. You remain the account owner.
Client Area access is also distinct from a DirectAdmin account, a CMS role, a mailbox, or a VPS/SSH user. It does not automatically create a separate restricted identity inside those systems. For application-only work, use an appropriately limited application user; arrange panel or server access separately where needed.
Review and remove access
Use Manage Permissions to change an existing user's access and save the changes. For an unaccepted invitation, use Resend Invite if needed or Cancel Invite when it is no longer wanted.
When the work is finished, choose Remove Access for the developer and confirm. Check the user list afterwards. Separately revoke any CMS accounts, panel access, SSH keys or tokens supplied for the project. Removing Client Area access does not by itself revoke those credentials or guarantee that another system's sessions have ended.
