refactor(console): remove redundant notification from m2m guide (#5954)

logto-io · May 31, 2024 · 9861b8a · 9861b8a
1 parent b8ea480
commit 9861b8a
Showing 1 changed file with 0 additions and 4 deletions.
diff --git a/packages/console/src/assets/docs/guides/m2m-general/README.mdx b/packages/console/src/assets/docs/guides/m2m-general/README.mdx
@@ -14,10 +14,6 @@ Machine-to-machine (M2M) is a common practice to authenticate if you have an app
 
 Since Logto uses RBAC as its access control policy, assigning M2M roles to M2M apps is necessary for protecting your API which needs direct service talk.
 
-<InlineNotification>
-To learn our current RBAC and the difference between user role and M2M role, see <a href="https://docs.logto.io/docs/recipes/rbac/manage-permissions-and-roles/">Manage permissions and roles</a> to learn more
-</InlineNotification>
-
 There are two common use cases of using machine-to-machine apps in Logto:
 
 1. **Accessing Logto Management API**: In this case, you need to assign a M2M role that include the `all` permission from the built-in Logto Management API to your M2M app.