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

fix(docs): Added note for code example.

Browse Source 
Signed-off-by: Valentin Grégoire <valentin.gregoire@gmail.com>
This commit is contained in:
Valentin Grégoire
2025-05-26 11:08:29 +02:00
parent 046d2177bc
commit 01bb34675d
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/permissions/frontend-integration.md
+4
View File
@@ -4,6 +4,10 @@ title: Frontend Integration
description: How to place your Backstage frontend components behind authorization
---
:::info
Starting with a [fresh Backstage installation](https://backstage.io/docs/getting-started/), the code example below is already implemented, so there are no code actual code changes required.
:::
Now that we understand how to [author a permission policy](./writing-a-policy.md), let's consider cases where we'll need to supplement our policy with authorization checks on the frontend.
In most cases, actual functionality that live within various plugins will already have been placed behind authorization by the plugin authors. The permission backend will use your permission policy to return an authorization result, and the plugin frontend will correspondingly show/hide/disable the relevant UI component.