Open rkroy39 opened 1 month ago
Instead of binding the user with Employee doctype, bind it with Employment Type doctype in User Permission see here
Actually, employment type is not a doctype. It is attribute in Employee doctype
On Sun, 21 Jul, 2024, 1:24 am systonium, @.***> wrote:
Instead of binding the user with Employee doctype, bind it with Employment Type doctype in User Permission see here https://frappeframework.com/docs/user/en/basics/users-and-permissions#user-permissions
— Reply to this email directly, view it on GitHub https://github.com/frappe/frappe/issues/27168#issuecomment-2241277799, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYM4WH4O3NU6UJMOACRQMGTZNK55XAVCNFSM6AAAAABLEADZHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGI3TONZZHE . You are receiving this because you authored the thread.Message ID: @.***>
Is your feature request related to a problem? Please describe. I have to create a custom user who can access a limited number of employees based on employment type, such as regular/contractual. However, when giving access to the Employee doctype, all employees are visible to the user. How to give limited control of data from the database? It is like views in database Describe the solution you'd like I want to give that user the access to Same Doctype but with filtered data based on its attribute.
Describe alternatives you've considered I thought of making filtered data view to that user role from backend and always check its role while accessing the doctype.
Additional context