Link from content scope chapters

docs/docs/content-scope/content-website.md

@@ -53,4 +53,4 @@ You can then use `useContentScope()` to access the currently selected scope, whi
 
 COMET's user permission feature will automatically validate `scope` arguments of GraphQL operations and check if a user has access to the entity's scope. The column must be named `scope` for this to work.
 
-For nested entities or operations without a `scope` argument please refer to the documentation of the User Permissions system which describes how to decorate the resolvers/controllers properly.
+For nested entities or operations without a `scope` argument please refer to the [documentation of the User Permissions](/docs/user-permissions/access-control) system which describes how to decorate the resolvers/controllers properly.

docs/docs/content-scope/data-driven-application.md

@@ -44,13 +44,4 @@ const variables = {
 
 ### API: User permissions
 
-Data-driven applications don't benefit much from the COMET scope system. But for user permissions it has its value.
-
-First, an overview of user permissions:
-
--   Every user has permissions that give them access to resolvers (e.g., "products") - not covered here
--   Every user has access to scopes
-
-(Both are defined by rule in `AccessControlService` or can be overridden manually per user in the Admin)
-
-(The user permission feature checks for every request if the entity scope and the user's allowed scopes match.)
+In data-driven applications, the scope system is primarily used for controlling permissions. For additional information refer to the [User Permissions chapter](/docs/user-permissions/access-control).