Review Pilot Guide
Protect account access
Use the controls appropriate to Google sign-in or the configured local authentication method.
Complete the task
Follow the steps in order. Each change remains under your control.
- 1
Open account security settings and confirm the sign-in method.
- 2
For Google users, continue to authenticate through Google instead of guessing a local password.
- 3
Review available sessions, protection options and the panel language selection.
Successful result
The correct authentication route is clear and available security and language controls are reviewed.
If the result is different
Run these checks before sending a support request.
Never send passwords, card details or secret keys to support.
Use the account email when requesting account-specific assistance.
Related questions
Short answers that clarify rules and expected behaviour.
What password do I use after signing in with Google?
Google-authenticated users sign in through Google and should not guess a local password they never created. Use the available Google sign-in and account security controls.
Where can I manage account security?
Open the customer account security area to review the controls available for the sign-in method. Admin users can select their panel language in the account security settings.
What information should I send to support?
Use the email address linked to the account and include the organisation, product code or order number, the exact step, time and visible error. Never send passwords, card details or secret keys.
How can I ask about my personal data?
Read the Privacy page and contact the published privacy address with enough information to identify the account and request. Identity verification may be required before account data is disclosed or changed.
Still need account-specific help?
Tell us the account email, product or order number and the exact step that failed. Do not send passwords, card data or secret keys.