Confirm the person’s authorised responsibilities and a unique email address for their login. Separate panel administration from a simple restricted file-upload requirement.

1. Open Administration > User Accounts as the master user and choose Add SiteWorx User.
2. Enter a recognisable nickname, unique login email and strong temporary password. Use the first-login password-change option where appropriate.
3. Select only the required user permissions. Review Locked Domains carefully if access should be limited to particular domains.
4. Leave SSH disabled unless separately authorised and included in the service. Save the new user.
5. Have the person test a fresh login and the approved task, then confirm restricted domains and unrelated tools are not available.

The secondary identity should complete its authorised work without sharing the master password. Record who owns the account and when temporary access should expire or be reviewed.

If a needed tool is absent, compare the specific permission and domain restriction before enabling every permission. If the email is already used by another SiteWorx user, choose the correct distinct identity rather than modifying an unrelated person’s account.

Before adding a secondary user, write down the tasks they should complete. For example, a colleague managing mailboxes for one domain should not automatically receive access to all websites, billing information or unrelated account settings.

Use the role and domain restrictions available in your SiteWorx installation. Choose a reachable address for the correct person, then deliver initial access through an approved private process. Do not use the same login for a whole team when individual access is available.

How should I test the new role?

Use a separate browser session signed in as that user. Verify one allowed task and one task that should remain unavailable. Seeing the expected menu is not enough; confirm that the permitted action works and that the restriction is enforced.

Record who approved the access and review it when responsibilities change. A missing feature may be a permission issue rather than a fault in the hosting service. Send us the intended task, account role and relevant page when you need guidance. Do not widen every permission just to make a single button appear, and do not include the user's password in a support ticket.

No. The user works within the existing SiteWorx account and its permitted scope. Independent customers requiring separate ownership and resource boundaries should use appropriately separate hosting accounts.

• Deactivating a SiteWorx user while preserving the account
• Enabling SiteWorx two-factor authentication
• Reviewing and ending an unexpected SiteWorx FTP session
• Protecting a SiteWorx preview directory with a browser password

• InterWorx: Add Edit Delete Secondary Users Siteworx