Identify the person, required tasks, subscription and access end date. Decide whether a restricted FTP account is sufficient or panel access is necessary. Prepare an independent recovery email and avoid granting user-management authority to someone who should not change their own privileges.

1. Open Users > User Roles and review an existing role or create a purpose-specific role. Grant only the functions required for the assignment.
2. Open User Accounts and create the user with accurate contact information and a unique login.
3. Select the role and restrict access to the intended subscription. Avoid the all-subscriptions option unless that breadth is justified.
4. Use the available secure account-activation or password setup workflow. Provide the verified panel address separately from any secret and require the user to protect their own account.
5. Test the account in a separate session. Check both an allowed task and a task it must not perform, including available extensions. Record the account owner and review date.

Confirm the user sees only the intended subscription and can complete the approved workflow. Review extension access separately because a panel role is not proof of every third-party extension restriction. Keep the main owner account for ownership and recovery.

If essential tools are absent, compare role and subscription permissions instead of granting every permission. If access is too broad, deactivate the account while correcting the role. When the assignment ends, deactivate or remove the user and review separate FTP users, SSH keys, database credentials and tokens granted during the work.

• Protecting a Plesk account with two-factor authentication
• Creating a restricted FTP account in Plesk
• Changing your Plesk customer-account password
• Adding supported Apache and nginx directives in Plesk

• Plesk: Managing Additional User Accounts
• Plesk: Additional User Accounts