Starts in:
2 DAYS
4 HRS
11 MIN
4 SEC
Starts in:
2 D
4 H
11 M
4 S
Open Closed

Permissions Management for Docs Module and their documents for specific users and also for host and different tenants #5556


User avatar
0
Sraman created
  • ABP Framework version: v7.3.1
  • UI Type: MVC
  • Database System: EF Core (SQL Server)
  • **Tiered (for MVC) **: no
  • Exception message and full stack trace:
  • Steps to reproduce the issue:
  1. How to set permissions for Docs modules on the main menu similar to other modules?
  2. How to list specific documents to each user instead of showing all?
  3. And also how to use Docs module with Multi tenant ?

1 Answer(s)
  • User Avatar
    0
    jfistelmann created

    Hey,

    the docs module is not designed for that. It is meant to host documentation for everyone.

    Has you can see here: https://github.com/abpframework/abp/blob/dev/modules/docs/src/Volo.Docs.Admin.Application.Contracts/Volo/Docs/Admin/DocsAdminPermissions.cs

    There is no permission definition on a document level.

    Also, it's not designed for multitenancy: https://github.com/abpframework/abp/tree/dev/modules/docs/src/Volo.Docs.Domain/Volo/Docs

    Based on that information, you can either make a feature request here: https://github.com/abpframework/abp/issues OR: do something like this:

    1. Implement your own Application and UI Layer with your specific needs, with permission and multitenancy logic matching your needs. Note that you have to come up with a different solution for matching the data to a tenant as the Entities do not implement IMultiTenancy
    2. Override the default Application service implementations and (for example) just throw NotImplementedException's to prevent that someone gains access through the default logic
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06