Settings and security
Tiden separates personal security, organization security, workspace secrets, and product settings.
Profile
Profile settings include:
- Name and avatar.
- Password changes.
- API tokens.
- Two-factor authentication.
- Passkeys.
- Recovery codes.
API tokens
API tokens are shown once, start with tfy_, and are intended for CLI, CI, MCP,
and public REST API use. There are two kinds.
Account tokens live in Settings > API tokens. An account token acts as you and always has full access to every product you can reach. Use it for the CLI and the MCP server on your own machine.
Product tokens live in Product settings > API tokens. A product token belongs to the product and is refused on every other product. Use product tokens for CI. When you create one, Access is either Full access to this product or Publish test runs only. A publish-only token cannot change specs or branches, but its completed runs update the test cases on the branch each run resolves to. Add Only intent branches for a token that workflows on pull request code can read, such as a merge queue: its results count only for intent branches.
Workspace owners and admins create and revoke product tokens. Every member of the product sees the list. Publish-only tokens created before product tokens existed are already in Product settings > API tokens, with the same value. See API authentication.
Store tokens in a secret manager. Revoke unused tokens where they live: account tokens in Settings > API tokens, product tokens in Product settings > API tokens.
Two-factor authentication
Users can enroll TOTP, register passkeys, and regenerate recovery codes. Organizations can require two-factor authentication for members.
If a member loses access, an organization admin can reset that member's two-factor setup.
Workspace credentials
Workspace credentials store external secrets for automation, especially LLM providers. Credentials are write-only after creation. Use the test action to verify that a credential is usable.
Product settings
Product settings manage product metadata and the product's API tokens. Product deletion should be treated as destructive and reserved for retired or test products.