Credential Good for Watch for
Integration (System › Extensions › Integrations) A standing link from an ERP, WMS or CRM. It only reaches the resources you tick when you create it. From 2.4.4 its access token can't be sent as a plain bearer token unless an admin allows it. Signing each request with OAuth 1.0a is the route Adobe prefers.
Admin token A script someone runs by hand, or a quick test against staging. It acts as that admin user, with that user's permissions, and expires after four hours by default. With admin two-factor authentication on, a plain username-and-password request won't get one; the 2FA module has its own token endpoints.
Customer token Calls made as one shopper: their orders, cart and addresses. GraphQL's generateCustomerToken mutation issues one too. It only reaches resources marked self or anonymous, and lasts an hour by default.
No token (guest) Public catalog reads and guest carts. Only resources marked anonymous. Anything naming a customer or an order needs a credential.
Adobe IMS (Cloud Service only) Stores on Adobe Commerce as a Cloud Service, where the older token types aren't supported. Credentials come from an Adobe Developer Console project, not the Commerce Admin, and an admin's access follows their Commerce role.