From 5be3fc3ab01f43b39436eb527c21485f24819663 Mon Sep 17 00:00:00 2001
From: Ruslan Gaiazov <44463016+freeyoungstrong@users.noreply.github.com>
Date: Wed, 15 Jan 2025 17:30:11 +0100
Subject: [PATCH] Update 04-authorizing-access-to-paginated-data.md

added info section as other pages in this section have

Signed-off-by: Ruslan Gaiazov <44463016+freeyoungstrong@users.noreply.github.com>
---
 .../plugin-authors/04-authorizing-access-to-paginated-data.md   | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/permissions/plugin-authors/04-authorizing-access-to-paginated-data.md b/docs/permissions/plugin-authors/04-authorizing-access-to-paginated-data.md
index 3a0b358c85..10941e6305 100644
--- a/docs/permissions/plugin-authors/04-authorizing-access-to-paginated-data.md
+++ b/docs/permissions/plugin-authors/04-authorizing-access-to-paginated-data.md
@@ -4,7 +4,9 @@ title: 4. Authorizing access to paginated data
 description: Explains how to authorize access to paginated data in a Backstage plugin
 ---
 
+:::info
 This documentation is written for [the new backend system](../../backend-system/index.md) which is the default since Backstage [version 1.24](../../releases/v1.24.0.md). If you are still on the old backend system, you may want to read [its own article](./04-authorizing-access-to-paginated-data--old.md) instead, and [consider migrating](../../backend-system/building-backends/08-migrating.md)!
+:::
 
 Authorizing `GET /todos` is similar to the update endpoint, in that it should be possible to authorize access based on the characteristics of each resource. However, we'll need to authorize a list of resources for this endpoint.