From 0445f5309a3eaaf675275b981b68fcaeb439b959 Mon Sep 17 00:00:00 2001 From: Peter Macdonald Date: Thu, 2 May 2024 19:41:59 +0200 Subject: [PATCH] removes info block Signed-off-by: Peter Macdonald --- docs/permissions/getting-started.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/permissions/getting-started.md b/docs/permissions/getting-started.md index 33eea296d9..825fefe598 100644 --- a/docs/permissions/getting-started.md +++ b/docs/permissions/getting-started.md @@ -24,10 +24,6 @@ Like many other parts of Backstage, the permissions framework relies on informat ## Integrating the permission framework with your Backstage instance -:::info -If you created your backstage app using the [@backstage/create-app](https://backstage.io/docs/getting-started/#1-create-your-backstage-app), the permission framework will already be setup including the allow-all policy! -::: - ### 1. Set up the permission backend The permissions framework uses the `permission-backend` plugin to accept authorization requests from other plugins across your Backstage deployment. The default `@backstage/create-app` template includes the permission backend, but if you need to make the change manually, these are the steps: