Registered public OAuth clients can authenticate using their client ID without sending a client secret. Use this client type for software that cannot keep a distributed secret, such as browser or native applications.

OAuth authorization can now limit an access token to a selected team. Integrations can use this team context instead of treating every token as access to all of the user's teams.

You can now register a passkey and use it to sign in to your Chief Tools account. Choose passkey sign-in on the login page and confirm with your device or password manager.

Newly created personal access tokens now include a Save in 1Password button. Save the token while it is visible, together with its name, expiration, and allowed applications; the token value is shown only once.

You can now register a security key from the two-factor settings and use it as your second factor when signing in. Choose Use security key after entering your password and confirm with your registered key in a compatible browser.

You can now create a team from the Teams page and invite other users by email. Team settings let you manage members, choose a timezone, and set your default team, so you can work together on resources in supported Chief Tools apps.

You can now set an expiration date and choose Allowed applications when creating a personal access token. Use these controls to limit how long a token works and which supported product APIs it can access.

Changing your account email now requires confirmation through your current address and verification of the new address. Start from your profile and follow the confirmation emails to complete the change.

The app dashboard now shows Last accessed for each connected application. You can see when you last signed in to an app, or whether you have never accessed it.

You can now connect your Bitbucket account in the social-account settings and use it to sign in. Link it while signed in to your existing Chief Tools account, then choose Bitbucket on the sign-in page.