From 244b57722ac91d28562f202dc1dabcbeb21308fc Mon Sep 17 00:00:00 2001 From: Peter Macdonald Date: Thu, 2 May 2024 16:35:04 +0200 Subject: [PATCH] added info block as suggested to inform permissions are setup when using create-app, reworded section Signed-off-by: Peter Macdonald --- docs/permissions/getting-started.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/permissions/getting-started.md b/docs/permissions/getting-started.md index 33e2f95041..33eea296d9 100644 --- a/docs/permissions/getting-started.md +++ b/docs/permissions/getting-started.md @@ -24,9 +24,13 @@ 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 a new `permission-backend` plugin to accept authorization requests from other plugins across your Backstage instance. The Backstage backend does not include this permission backend by default, so you will need to add it: +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: 1. Add `@backstage/plugin-permission-backend` and `@backstage/plugin-permission-backend-module-allow-all-policy` to your backend dependencies, this will add the permission backend and a policy that allows all permissions: