Map the accounts that control access
Begin with an inventory of the accounts needed to reach your creator platform: the platform login, its recovery email, and any password manager or authentication method you depend on. A recovery plan is only as strong as its weakest linked account. If someone can access your email, they may be able to reset other credentials, so protect it as carefully as the creator account.
Record the purpose of each account and the recovery route, not the passwords themselves. Keep this inventory in a secure place you can reach if your usual phone or computer is unavailable. Avoid putting recovery details in a public document, shared production folder or ordinary message thread. The goal is to make the sequence understandable without creating a second copy of your keys.
- List the platform login and recovery email.
- Identify the device or app used for authentication.
- Note where backup codes are stored without writing the codes in the inventory.
- Record official support and recovery links from the platform.
Strengthen the recovery email first
Use a unique password for the email account connected to the creator platform. Where available, enable multi-factor authentication and review the recovery phone number, backup email and active sessions. Remove recovery routes you no longer control. These steps reduce the chance that an old device, shared mailbox or outdated address becomes the easiest path into business accounts.
Consider whether your email address reveals personal details you do not want associated with a public creator identity. Separate business and personal accounts where practical, but ensure the business address remains accessible to you. Keep recovery contact information current and do not use an address you may lose when changing a domain, employer or service.
| Access layer | Plan to document |
|---|---|
| Creator platform | Login email, official recovery route and account identifier |
| Recovery email | Authentication status, current recovery options and trusted access owner |
| Authenticator | Device or method used and backup-code storage location |
| Collaborators | Named authorized users and how access is granted or removed |
| Business records | Secure storage location and backup schedule |
| Recovery event | Order of steps and official support channel |
Use recovery methods you can actually retrieve
A continuity plan should explain what to do if the primary device is unavailable, not invite repeated experiments with account security. If you need to replace a phone, follow official instructions and confirm access before wiping the old device. Keep a record of the steps completed, but never include one-time codes in that record.
Manage collaborator access without shared passwords
If an editor, assistant or business partner needs access, first check whether the platform offers individual roles or other authorized access controls. Named access is easier to review and revoke than a common password, and it can help distinguish who is responsible for a task. Grant the narrowest access that supports the work and remove it when the relationship ends.
If separate accounts are not available, consider whether the task can be completed through a safer workflow, such as transferring approved files or having the account owner complete the final action. Do not assume a platform permits account sharing. Review its terms and use the controls it documents. Agree in writing on who can change recovery details, publish material or respond to account security notices.
- Use individual accounts or roles when officially supported.
- Limit access to the tasks a collaborator needs.
- Agree on a process for ending access promptly.
- Never share one-time authentication codes through routine chat.
Keep records and recovery evidence organized
Keep a concise incident log if access changes unexpectedly: date, messages received, recovery steps attempted and support reference details. Use official support channels and avoid sending passwords, full payment details or authentication codes. This log can help you explain the sequence accurately without collecting more personal information than necessary.
Write a calm account recovery sequence
Create a short sequence for a lost device, suspected unauthorized access or a locked account. Start by securing the recovery email from a trusted device, then use the platform’s official recovery route, review active sessions if access is restored, update credentials and check account contact details. The exact order can depend on the platform’s instructions, so treat its official guidance as controlling.
Decide in advance who can take each step and how you will verify that a support message is genuine. Beware of unsolicited messages asking for credentials or codes. If an account may be compromised, do not announce private recovery details publicly. After recovery, review connected devices, collaborator access and any account changes, then revise the continuity plan to address the gap that caused the incident.
Common questions
Should I store backup codes on the same phone as my authenticator?
That can leave you without both if the device is lost or inaccessible. Follow the platform’s instructions and keep recovery information in a secure, separate location you can reach when the primary device is unavailable.
Can I share my platform password with a trusted assistant?
Check the platform’s terms and access controls first. Individual authorized access is preferable where available; if it is not, consider whether the task can be handled without sharing credentials.
What information should I give platform support during recovery?
Use the official recovery process and provide only the information it requests through that channel. Do not send passwords, full card numbers or one-time authentication codes in ordinary messages.
How often should I review the continuity plan?
Review it when you change devices, recovery email, collaborators or account security settings, and periodically enough to catch outdated contacts. Confirm the plan remains accessible without placing secrets in the document.