Appearance

Powered by Platform One

Employee or Contractor Transfers ​

Overview ​

Use this guide when a P1 user transfers to a different organization, contractor, company, team, or role but still needs P1 access.

A transfer is different from a complete offboarding. If the user still needs P1 access, review and update the existing account rather than creating a new one.

Follow the process below to help prevent duplicate accounts and unnecessary loss of access.

When to request a transfer ​

A transfer may be appropriate when a user:

  • Moves to a different contractor or company.
  • Changes organizations but continues to support a P1 customer or mission.
  • Changes roles and still requires P1 access.
  • Moves to a different team or project.
  • Needs their existing account information or access updated because of an organizational change.

TIP

If the user no longer requires any P1 access, use the Offboarding Guide instead.

Before you begin ​

Have the following information available:

  • User's full name
  • Current email address: The email address associated with the user's existing P1 account.
  • P1 username: If known.
  • New email address: If the user's email address is changing.
  • New organization or company: If applicable.
  • New role or position: If applicable.
  • Access that should be retained: Identify the P1 applications, teams, or services the user still needs.
  • Access that should be removed: Identify any access the user no longer requires.
  • Effective date: When the organizational or role change takes effect.
  • Existing request or ticket number: If the transfer is related to an existing request.

WARNING

Verify the user's existing account information before submitting a request. Do not create a second P1 account because the user's organization, company, email address, or role has changed.

Submit a transfer request ​

Submit the approved transfer or account-update request through the Help Desk.

Provide the user's current account information and clearly describe the changes needed.

If the user's email address, organization, company, role, or required application access is changing, include both the current and new information when applicable.


What happens after you submit a request ​

The Help Desk will review the transfer request and determine which account and access changes are required.

Depending on the transfer, the process may include:

  • Updating account information.
  • Updating the user's organization or company information.
  • Updating the user's email address, when applicable.
  • Removing access that is no longer required.
  • Requesting or assigning new application access.
  • Updating team or project access.
  • Verifying that the existing P1 account remains associated with the user.

The exact changes depend on the user's new organization, role, and required access.

We may contact you if we need additional information or verification.


Do not create a new account ​

If the user already has a P1 account, do not create another account simply because:

  • The user has a new work email address.
  • The user changed companies or contractors.
  • The user changed roles.
  • The user moved to a different team.
  • The user's existing account needs information updated.

Creating another account can result in duplicate accounts, missing access, or account-management issues.

If you are unsure whether an existing account can be updated, contact the Help Desk before creating a new account.


Review application access ​

A transfer does not necessarily mean the user should retain all previous application access.

Review the user's current access and identify:

  • Applications the user still needs.
  • Applications the user no longer needs.
  • New applications required for the user's new role.
  • Teams or projects the user needs to join.
  • Teams or projects the user should leave.

For application-specific requests, see our Request Application Access Guide.

If the user's email address is changing ​

If the user's organization or contractor changes and their email address also changes, include both the old and new email addresses in the transfer request.

Do not create a new P1 account using the new email address unless the Help Desk specifically instructs you to do so.

The Help Desk will determine the appropriate process for updating or associating the account.

If the user needs new application access ​

A transfer may require the user to receive access to applications, teams, or projects that were not part of their previous role.

After the account transfer is processed, submit the appropriate application-access requests for any additional services the user requires.

INFO

Access to one P1 application does not automatically provide access to every other P1 application.

If access needs to be removed ​

If the user no longer needs a specific application, team, or project, identify that access in the transfer request or submit the appropriate access-removal request.

If the user will still need some P1 access, do not request complete offboarding just because specific access needs to be removed.

Verify the transfer ​

After the transfer request has been processed:

  1. Confirm that the user's existing P1 account remains available.
  2. Confirm that the user's account information reflects the approved changes.
  3. Confirm that required application access has been requested or provided.
  4. Confirm that access no longer required has been removed.
  5. Report any unexpected account or access issues to the Help Desk.

Changes to account information or application access may not appear immediately in every connected service.

If the user cannot access the account after the transfer ​

If the user cannot sign in after a transfer:

  • Do not create a new P1 account.
  • Record the exact error message.
  • Confirm which account and email address the user is attempting to use.
  • Contact the Help Desk.
  • Include the transfer request or ticket number, if available.

For authentication-specific problems, see MFA & Authentication Troubleshooting.

If a duplicate account was created ​

If a second P1 account was accidentally created during a transfer, do not continue registering additional accounts.

Contact the Help Desk and explain that a duplicate account may have been created.

Provide:

  • The user's name.
  • The email address associated with the original account.
  • The email address associated with the new account, if different.
  • The usernames of the accounts, if known.
  • The transfer request or ticket number.
  • Any relevant error messages.

See Resolve Duplicate Account Issues for additional guidance.

Contact the Help Desk ​

Contact the Help Desk if you are unsure how to handle a transfer or if the user's account or access does not reflect the approved changes.

When requesting assistance, provide:

  • User's name.
  • Current P1 username, if known.
  • Current email address.
  • New email address, if applicable.
  • Current and new organization or company.
  • Current and new role, if applicable.
  • Applications or services the user needs.
  • Applications or services the user no longer needs.
  • Effective date of the transfer.
  • Existing request or ticket number.
  • Exact error message, if applicable.
  • Screenshot, when available.

Protect user information ​

Only provide account information through approved Help Desk or P1 request channels.

Never include the following in a support request:

  • Passwords
  • MFA/OTP codes
  • MFA QR codes
  • Recovery codes
  • YubiKey PINs
  • Other authentication secrets

Need more help? ​

If you are unsure whether a user should be transferred, fully offboarded, or have only specific application access changed, contact the Help Desk before submitting the request.

Powered By Platform One