bruno-andrade-azion · Nov 5, 2026
@@ -32,7 +32,11 @@ To turn on Image Processor and Application Accelerator:
   Access [Azion Console](https://console.azion.com/) > **Applications** > **your application**.
 
   </DocStep>
-  <DocStep title="Go to Main Settings > Modules > Default Modules" />
+  <DocStep title="Open Default Modules">
+
+  Go to **Main Settings** > **Modules** > **Default Modules**.
+
+  </DocStep>
   <DocStep title="Turn on Image Processor" />
   <DocStep title="Turn on Application Accelerator" />
   <DocStep title="Select Save" />

@@ -21,7 +21,7 @@ A cache files each stored response under a key built from the request. When that
 
 ## Cache setting structure
 
-Application Accelerator acts through the `modules.application_accelerator` object of a cache setting, which [Azion Console](https://console.azion.com) shows as the **Application Accelerator** section of the setting. This cache setting keeps a product listing for 30 seconds and gives each value of its `category` argument a copy of its own, sent as the body of `POST /v4/workspace/applications/<application-id>/cache_settings`:
+Application Accelerator acts through the `modules.application_accelerator` object of a cache setting, which [Azion Console](https://console.azion.com/) shows as the **Application Accelerator** section of the setting. This cache setting keeps a product listing for 30 seconds and gives each value of its `category` argument a copy of its own, sent as the body of `POST /v4/workspace/applications/<application-id>/cache_settings`:
 
 ```json
 {

@@ -42,7 +42,7 @@ Cache acts through a cache setting, which holds how long Azion and the browser k
 - `browser_cache` decides what a visitor's browser keeps. `honor` forwards the `Cache-Control` and `Expires` headers the origin sends, `override` replaces them with `max_age`, in seconds, and `no-cache` turns browser caching off.
 - `modules.cache` decides what Azion keeps. With `behavior` set to `override`, `max_age` replaces the headers of the origin. Under `honor`, Azion keeps those headers, and it keeps a response whose origin sends no TTL for a default TTL.
 - `stale_cache`, `large_file_cache`, and `tiered_cache` turn on stale cache, fragments of 1,024 kB, and a second cache layer in the region that `topology` names. A body that leaves one out gets it off, and `tiered_cache` requires the `override` behavior.
-- A cache setting caches nothing on its own: a Request Phase rule applies it with `{ "type": "set_cache_policy", "attributes": { "value": <cache-setting-id> } }`. [Azion Console](https://console.azion.com) builds the same setting from **+ Cache** on the **Cache Settings** tab of an application.
+- A cache setting caches nothing on its own: a Request Phase rule applies it with `{ "type": "set_cache_policy", "attributes": { "value": <cache-setting-id> } }`. [Azion Console](https://console.azion.com/) builds the same setting from **+ Cache** on the **Cache Settings** tab of an application.
 
 If you set `Cache-Control` headers at your origin, the model transfers: `honor` keeps them, and `override` replaces them.
 

@@ -94,7 +94,7 @@ To create the function in Azion Console:
 <DocSteps>
   <DocStep title="Open the Functions page">
 
-  Access [Azion Console](https://console.azion.com/) > **Products Menu** > **Libraries** > **Functions**.
+  Access [Azion Console](https://console.azion.com/) > **Functions**.
 
   </DocStep>
   <DocStep title="Select + Function" />
@@ -244,7 +244,11 @@ Computing time and invocations for functions generate usage-related costs. For t
 To bind the function to an application in Azion Console:
 
 <DocSteps>
-  <DocStep title="Still in Azion Console, go to Products Menu > Build > Applications" />
+  <DocStep title="Access Azion Console">
+
+  Access [Azion Console](https://console.azion.com/) > **Applications**.
+
+  </DocStep>
   <DocStep title="Select the application that runs the function" />
   <DocStep title="In the Main Settings tab, turn on the Functions module" />
   <DocStep title="Select Save" />

@@ -92,7 +92,7 @@ For how the delivered format is chosen, how the cache tells derived images apart
 - **Cache**: once `ims` is in the allowlist of the cache setting, each distinct `ims` string is a separate stored object. A page that asks for four fixed widths stores four objects, while a page that asks for arbitrary widths stores one per width. Once a derived image is in cache, it is delivered without processing. For the practices, refer to [Applications best practices](/en/documentation/platform/applications/best-practices/#image-processor).
 - **Storage**: Image Processor stores no images and accepts no uploads. The source stays where it already lives, and no derived image becomes an asset of the account. A workflow that needs to keep a transformed file saves the response itself.
 - **Neighbors**: [WASM Image Processor](/en/documentation/devtools/azion-lib/wasm-image-processor/) is a WebAssembly library that processes images inside a function on [Functions](/en/documentation/platform/functions/). It is a different surface with a different interface, and no setting of Image Processor configures it.
-- **Interfaces**: you turn on Image Processor on the **Main Settings** tab of an application in [Azion Console](https://console.azion.com), and through [Azion API](https://api.azion.com/) at `/v4/workspace/applications/<application-id>`. [Azion CLI](/en/documentation/devtools/cli/) sets it with `--image-processor` on `azion create application` or `azion update application`. [`azion.config.js`](/en/documentation/devtools/cli/azion-config-js/) and [Azion Lib](/en/documentation/devtools/azion-lib/) set it with `imageProcessorEnabled`. For each field, flag, behavior, and header, refer to [Image Processor settings](/en/documentation/platform/applications/image-processor/settings/).
+- **Interfaces**: you turn on Image Processor on the **Main Settings** tab of an application in [Azion Console](https://console.azion.com/), and through [Azion API](https://api.azion.com/) at `/v4/workspace/applications/<application-id>`. [Azion CLI](/en/documentation/devtools/cli/) sets it with `--image-processor` on `azion create application` or `azion update application`. [`azion.config.js`](/en/documentation/devtools/cli/azion-config-js/) and [Azion Lib](/en/documentation/devtools/azion-lib/) set it with `imageProcessorEnabled`. For each field, flag, behavior, and header, refer to [Image Processor settings](/en/documentation/platform/applications/image-processor/settings/).
 - **Observability**: [Real-Time Metrics](/en/documentation/platform/real-time-metrics/) has an **Image Processor** tab with request charts, and [Real-Time Events](/en/documentation/platform/real-time-events/) has an **Image Processor** dataset, which requires Image Processor on.
 - **Limits**: one image takes up to 150 MB, 3840 pixels of width, and 2160 pixels of height. For every bound and what each plan includes, refer to [Applications limits](/en/documentation/platform/applications/limits/#image-processor), and for the rates, to [Pricing](/en/documentation/fundamentals/pricing/#image-processor).
 - **Terms**: the [Applications glossary](/en/documentation/platform/applications/glossary/) defines the words the Image Processor pages give a specific meaning, such as derived image, source image, autocrop, and `fit-in`.

@@ -72,13 +72,12 @@ You can find the download links to the respective architectures on [Azion CLI's
 
 ### Console
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the upper-left corner of the page, open the **Products menu**, represented by three horizontal lines, and then select **Edge Services**.
-3. Click on the **+ Service** button.
-4. Name this service `Azion CLI Installation`.
-5. Enter the variables and values for the resource, if necessary.
-6. Set the status as **Active**.
-7. Click the **Save** button.
+1. Access [Azion Console](https://console.azion.com/) > **Edge Services**.
+2. Select **+ Service**.
+3. Name this service `Azion CLI Installation`.
+4. Enter the variables and values for the resource, if necessary.
+5. Set the status as **Active**.
+6. Select **Save**.
 </Fragment>
 
 <Fragment slot="panel.api">
@@ -224,7 +223,7 @@ Replace `[TOKEN VALUE]` with your [personal token](/en/documentation/guides/plat
 
 ### Console
 
-1. On the upper-left corner of the page, open the **Products menu**, represented by three horizontal lines, and then select **Edge Nodes**.
+1. Go to **Edge Nodes**.
 2. Select the edge node to which you want to bind a service.
 3. Go to the **Services** tab and click the **+ Service** button.
 4. Choose the service `Azion CLI Installation` you've created.

@@ -54,11 +54,10 @@ Once an edge node is deleted, it can't be recovered.
 
 ### Console
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the upper-left corner of the page, open the **Products menu**, represented by three horizontal lines, and then select **Edge Nodes**.
-3. Find the edge node you wish to remove.
-4. Click on the three dots icon and click on **Delete**. 
-5. Confirm the deletion.
+1. Access [Azion Console](https://console.azion.com/) > **Edge Nodes**.
+2. Find the edge node you wish to remove.
+3. Select the three dots icon and select **Delete**.
+4. Confirm the deletion.
 </Fragment>
 
 <Fragment slot="panel.api">

@@ -29,11 +29,10 @@ If you've already installed [Azion Orchestrator Agent](/en/documentation/guides/
 
 ### Console
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the upper-left corner of the page, open the **Products menu**, represented by three horizontal lines, and then select **Edge Nodes**.
-3. Find the edge node you wish to authorize, which will have the status `Waiting Authorization`.
-4. Click on the three dots button and then click **Authorize**.
-5. Confirm the authorization. 
+1. Access [Azion Console](https://console.azion.com/) > **Edge Nodes**.
+2. Find the edge node you wish to authorize, which will have the status `Waiting Authorization`.
+3. Select the three dots button and then select **Authorize**.
+4. Confirm the authorization. 
 </Fragment>
 
 <Fragment slot="panel.api">

@@ -31,13 +31,12 @@ You can create a relation between an edge node and an edge service in Azion Cons
 
 ### Console
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the upper-left corner of the page, open the **Products menu**, represented by three horizontal lines, and then select **Edge Nodes**.
-3. Select the edge node you want to bind to a service.
-4. In the **Main Settings** tab, look for the option **Add-On Services** under **Orchestration Modules** and activate it.
-5. Go to the **Services** tab and click the **+ Service** button.
-6. Choose the service you want to bind and add the variables if needed.
-7. Click the **Save** button.
+1. Access [Azion Console](https://console.azion.com/) > **Edge Nodes**.
+2. Select the edge node you want to bind to a service.
+3. In the **Main Settings** tab, look for the option **Add-On Services** under **Orchestration Modules** and activate it.
+4. Go to the **Services** tab and select **+ Service**.
+5. Choose the service you want to bind and add the variables if needed.
+6. Select **Save**.
 </Fragment>
 
 <Fragment slot="panel.api">

@@ -33,13 +33,12 @@ You can create a resource in Azion Console or with the Azion API.
 
 ### Console
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the top-left corner, select the **Products menu**, represented by three horizontal lines, and then **Edge Services**.
-3. Select the edge service to which you want to add a resource.
-4. Go to the **Resources** tab and click on the **+ Resource** button.
-5. Enter the **Path** of the resource.
-6. Choose the type **Text**.
-7. Add the following content to the content block: 
+1. Access [Azion Console](https://console.azion.com/) > **Edge Services**.
+2. Select the edge service to which you want to add a resource.
+3. Go to the **Resources** tab and select **+ Resource**.
+4. Enter the **Path** of the resource.
+5. Choose the type **Text**.
+6. Add the following content to the content block: 
 
 ```bash
 My name is {{name}}, and this is my first added resource
@@ -49,7 +48,7 @@ My name is {{name}}, and this is my first added resource
 The tag `{{name}}` will be replaced by the environment configured for the service or the variable configured on the node. The edge node variable will override the variable configure on the edge service.
 :::
 
-8. Click the **Save** button.
+7. Select **Save**.
 </Fragment>
 
 <Fragment slot="panel.api">

@@ -27,12 +27,11 @@ You can unbind an edge service from an edge node in Azion Console or with the Az
 
 ### Console
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the upper-left corner of the page, open the **Products menu**, represented by three horizontal lines, and then select **Edge Nodes**.
-3. Select the edge node from which you want to unbind a service.
-4. Go to the **Services** tab.
-5. Find the service you wish to unbind and click the trash can icon. 
-6. Confirm the unbinding.
+1. Access [Azion Console](https://console.azion.com/) > **Edge Nodes**.
+2. Select the edge node from which you want to unbind a service.
+3. Go to the **Services** tab.
+4. Find the service you wish to unbind and select the trash can icon. 
+5. Confirm the unbinding.
 </Fragment>
 
 <Fragment slot="panel.api">

@@ -36,14 +36,13 @@ The priority is always the edge node variable. So, if you have a variable config
 
 ### Console
 
-1. Go to [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the top-left corner, select the **Products menu**, represented by three horizontal lines, and then **Edge Services**.
-3. Select the [edge service](/en/documentation/guides/application-development/automation/create-edge-service/) to which you want to add a variable.
-4. In the **Variables** section, add the following variable:
+1. Access [Azion Console](https://console.azion.com/) > **Edge Services**.
+2. Select the [edge service](/en/documentation/guides/application-development/automation/create-edge-service/) to which you want to add a variable.
+3. In the **Variables** section, add the following variable:
 
 <Code client:visible lang="bash" code="name=azion" />
 
-5. Click the **Save** button.
+4. Select **Save**.
 
 Now, you've created a variable related to a specific service. You need to access this variable through a resource.
 
@@ -132,22 +131,21 @@ Check the [Azion API documentation](https://api.azion.com/) and the [OpenAPI spe
 
 ### Console
 
-1. Go to [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. On the top-left corner, select the **Products menu**, represented by three horizontal lines, and then **Edge Nodes**.
-3. Select the edge node to which you want to add a variable.
-4. Go to the **Services** tab.
-5. Choose the [service](/en/documentation/guides/application-development/automation/create-edge-service/) to which you want to apply the variable.
-6. Add the following content to the variables block: 
+1. Access [Azion Console](https://console.azion.com/) > **Edge Nodes**.
+2. Select the edge node to which you want to add a variable.
+3. Go to the **Services** tab.
+4. Choose the [service](/en/documentation/guides/application-development/automation/create-edge-service/) to which you want to apply the variable.
+5. Add the following content to the variables block: 
 
 ```bash 
 name=azion2
 ```
 
-7. Click the **Save** button.
+6. Select **Save**.
 
 Now, you've created a variable related to a specific node. You need to access this variable through a resource.
 
-1. Go to [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/) > **Edge Services**.
+1. Go to **Edge Services**.
 2. Select the service related to the resource. 
 3. Click on **+ Resource** or select the resource where you wish to use the variable.
 4. Enter the **Path** of the resource.

@@ -69,7 +69,7 @@ To create a personal token in Azion Console:
 <DocSteps>
   <DocStep title="Open the Personal Tokens page">
 
-  Access [Azion Console](https://console.azion.com/) > **Account** > **Personal Token**.
+  Access [Azion Console](https://console.azion.com/) and, in the account menu, select **Personal Token**.
 
   </DocStep>
   <DocStep title="Select + Personal Token" />

@@ -48,7 +48,7 @@ The servers accept an Azion personal token as their credential. To create the to
 <DocSteps>
   <DocStep title="Open the personal tokens page">
 
-  Access [Azion Console](https://console.azion.com/) > **Account** > **Personal Token**. **Account** is the avatar menu.
+  Access [Azion Console](https://console.azion.com/) and, in the account menu, select **Personal Token**.
 
   </DocStep>
   <DocStep title="Select + Personal Token" />

@@ -12,7 +12,7 @@ import DocCard from '@aziontech/webkit/doc-card'
 import DocSteps from '@aziontech/webkit/doc-steps'
 import DocStep from '@aziontech/webkit/doc-step'
 
-You can create an Azion account, sign in to [Azion Console](https://console.azion.com/), and reach the account pages from the account menu. For what each area of the Console holds once you are in, such as the products menu and the homepage shortcuts, refer to [About Azion Console](/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/).
+You can create an Azion account, sign in to [Azion Console](https://console.azion.com/), and reach the account pages from the account menu. For what each area of the Console holds once you are in, such as the Console menu and the homepage shortcuts, refer to [About Azion Console](/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/).
 
 ---
 
@@ -129,7 +129,7 @@ The session ends. To use the Console again, sign in.
 ## Next steps
 
 <DocCardGroup cols={2}>
-  <DocCard title="About Azion Console" href="/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/" label="Find the products menu, the homepage shortcuts, and every account menu entry." />
+  <DocCard title="About Azion Console" href="/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/" label="Find the Console menu, the homepage shortcuts, and every account menu entry." />
   <DocCard title="Use the + Create button" href="/en/documentation/guides/platform/account-and-billing/create-button/" label="Start an application from a template, a resource, or a GitHub repository." />
   <DocCard title="Enable multi-factor authentication" href="/en/documentation/guides/platform/account-and-billing/multi-factor-authentication/" label="Require a code from a phone at each sign-in." />
   <DocCard title="Configure account settings" href="/en/documentation/guides/platform/account-and-billing/account-settings/" label="Edit the name, company, address, and sign-in options of the account." />

@@ -10,8 +10,8 @@ permalink: /documentation/guides/application-security/access-and-compliance/veri
 
 During the [Transition to API v4](/en/documentation/fundamentals/api-v4-migration/) you might see some pages with different versions for v3 and v4. This guide helps you verify if your account has already been migrated to v4.
 
-1. Access [Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/).
-2. Open the **Products menu**.
+1. Access [Azion Console](https://console.azion.com/).
+2. Open the Console menu.
 
 If you see options such as **Workloads**, **Connectors** or **Custom Pages** your account has been migrated to v4 and you can use those products.
-Original file line number
+Diff line change
@@ Expand Up @@
     ## Cache setting structure
-    Application Accelerator acts through the `modules.application_accelerator` object of a cache setting, which [Azion Console](https://console.azion.com) shows as the **Application Accelerator** section of the setting. This cache setting keeps a product listing for 30 seconds and gives each value of its `category` argument a copy of its own, sent as the body of `POST /v4/workspace/applications/<application-id>/cache_settings`:
+    Application Accelerator acts through the `modules.application_accelerator` object of a cache setting, which [Azion Console](https://console.azion.com/) shows as the **Application Accelerator** section of the setting. This cache setting keeps a product listing for 30 seconds and gives each value of its `category` argument a copy of its own, sent as the body of `POST /v4/workspace/applications/<application-id>/cache_settings`:
     ```json
     {
@@ Expand Down @@