Choose a recognizable name
Use a name maintainers can identify later and a short description of the purpose. Distinguish development from production where both exist. A useful name explains the service rather than the temporary machine running it. Record who is responsible for the integration.
Keep contact and access details current
Choose a contact address that will remain available for important product notices. Review permissions against the connected service’s documentation. Request only access the application uses. Credentials belong in the deployment environment, not description or contact fields.
Continue through the account
Creating an application requires an authenticated workspace. This public page is a preparation guide and does not create records. Return to the sign-in area when ready. Read the API authorization reference and keep non-secret configuration in the project documentation.