remove IP allowlist info for tokens

docs/platform/concepts/application-users.md

@@ -38,15 +38,6 @@ the description field for each user to clearly indicate what it's used for.
 This helps you manage the lifecycle of the users and ensure the access permissions are
 correct for each use case.
 
-### Restrict access to trusted networks
-
-Specify allowed IP address ranges for each token. This prevents tokens from being used
-outside of your trusted networks, reducing the risk of breaches. You can also specify
-these ranges in your organization's
-[authentication policy](/docs/platform/howto/set-authentication-policies), limiting
-all access to the Aiven Platform to these IP addresses, including
-through application tokens.
-
 ### Keep tokens secure and rotate them regularly
 
 Make sure tokens are securely stored and only accessible by people who need them. Tokens

docs/platform/concepts/authentication-tokens.md

@@ -7,13 +7,13 @@ There are 3 types of tokens used to access the Aiven platform: session tokens, p
 Session tokens are created when you log in or make an API call. These tokens are revoked
 when you log out of the Aiven Console or the CLI.
 
-You can [create personal tokens](/docs/platform/howto/create_authentication_token) to access resources instead of using your password.
+You can [create personal tokens](/docs/platform/howto/create_authentication_token) to
+access resources instead of using your password.
 Application tokens are linked to
 [application users](/docs/platform/concepts/application-users). Application users and
 tokens are a more secure option for non-human users like external applications. You can
 create multiple personal or application tokens for different use cases.
 
-
 ## Token limits
 
 The maximum number of personal tokens that you can create is 10. Personal tokens are
@@ -31,7 +31,6 @@ To keep your personal and application tokens secure:
 - Set a session duration to limit the impact of exposure
 - Refrain from letting users share tokens
 - Rotation your tokens regularly
-- Restrict usage from trusted networks by specifying an allowed IP address range
 - Use application users for non-human users and follow
   [security best practices](/docs/platform/concepts/application-users) for their tokens
 - Control access to your organzation's resources with the