Skip to Content
Accounts, teams and support

Accounts, teams and support

Signing in and completing your account

Sign in with your email or mobile number. Verify your email and complete your profile; some operations remain unavailable until your account has the required access level. Use the sign-in page to recover your password.

Account security

  • Use unique passwords for your account and mailboxes.
  • Treat your CLI token like a password; keep it out of Git and CI logs.
  • Revoke unused tokens in account settings.
  • Store secrets in Variables, not source code or a Dockerfile.
  • Check project notifications and audit records for unexpected changes.

Members, notifications and audit records

On the project page, you can invite members, change their roles or remove them. Treat the project as a trust boundary. Notifications show events requiring attention. Audit records track management operations and are separate from application process logs.

Getting support

Create a ticket

Select the relevant project or service and the correct department.

Help us reproduce the issue

Include the error time, the operation you performed, the build/server ID and the relevant log excerpt. Do not send passwords, tokens, private keys or secrets.

Continue in the same ticket

Replies and attachments remain in the same request thread. Close the ticket once the issue is resolved.

Support never needs your private key, full password, CLI token or one-time code. If one of these values is exposed, rotate it immediately.