paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 33 Packages Projects Releases Wiki Activity

removes info block

Browse Source 
Signed-off-by: Peter Macdonald <macdonald.peter90@gmail.com>
This commit is contained in:
Peter Macdonald
2024-05-02 19:41:59 +02:00
parent 244b57722a
commit 0445f5309a
1 changed files with 0 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/permissions/getting-started.md
-4
View File
@@ -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: