Step 1
Keep sign-in and recovery information current
Use the official application link and a sign-in method you control. Store passwords securely where password sign-in is used. Check the recovery options offered by your provider and keep the associated email address accessible.
- Use the official app URL rather than a saved unfamiliar link.
- Keep your sign-in email and available recovery methods current.
- Never share passwords, verification codes or recovery secrets with support.
Step 2
Review team responsibilities and available permissions
Give each person access appropriate to their role using the controls available in your account. Separate daily billing or receiving work from account administration where the available permissions allow it. Review access when someone joins, changes roles or leaves.
- List the people who need access and the work they perform.
- Review the permission controls your account provides.
- Remove access that is no longer needed and document ownership changes.
Step 3
Troubleshoot access with useful context
Confirm that you are using the intended account and official application URL. Note the error message, time and action that failed. If the issue continues, send non-sensitive details through the contact page so support can identify the problem.
- Check the sign-in method and account email.
- Record the exact error and steps leading to it.
- Contact support with relevant context while keeping credentials private.
Worked example
Example: a useful support request
“I can sign in, but I cannot access the location records. This started after my team role changed. The message says access denied.” Include the account context and time, without including a password or verification code.
Illustrative example; use your own transaction data.
Frequently asked questions
Should everyone share one login?
Use individual access when your account supports it so responsibilities and access can be managed separately. Shared credentials make access changes and accountability harder.
Where can I get help with account access?
Use the contact page and describe the sign-in method, error and affected workflow. Do not include passwords, authentication codes or sensitive recovery information.