[FR] Inquiry Regarding Separate Customer Lists for Individual Users

[waghelapritesh]

Please verify that this feature request has NOT been suggested before.

• I checked and didn't find a similar feature request

Problem statement

I would like to bring to your attention an issue we are currently facing. At present, every user in the system has access to the entire customer list and all transaction details in the sales order and customer list sections. This means that User1 can see User2's customers and their respective transactions, and vice versa, which is causing a lack of privacy and confidentiality.

To address this, I would suggest implementing a system where each user has a separate customer list, ensuring that User1 only has access to their 100 customers and User2 only to their 150 customers. This way, users would not be able to view each other's customer data or transactions.

Could you please let me know if this can be achieved, and if so, the necessary steps to implement it?

Suggested solution

Hi,

I wanted to inquire if there is a possibility to set up separate customer lists for each individual user within the system. For example, User1 would have access to a list of 100 customers, and User2 would have access to a list of 150 customers. The key point is that each user should not be able to view or access the customer list or transaction details of the other user.

Could you kindly let me know if this functionality is available, or if there are any solutions or customizations that would allow us to implement this separation?

Looking forward to your response.

Describe alternatives you've considered

Not yet considered

Examples of other systems

No response

Do you want to develop this?

• I want to develop this.

[SchrodingersGat]

This level of separation is not possible. It would require a significant amount of refactoring to implement object level permission filtering across multiple database models and associated API endpoints.

While I would also not want to see this as a first class feature, it might make sense as a custom plugin. To achieve this with a plugin we would first need to expose the API permission system to plugins, allowing a custom plugin to determine which objects can be viewed / edited / etc by a given user. Then, the particular implementation requirements can be offloaded to a plugin.

However there would be a fair bit of work before a plugin can do this.

[matmair]

I think doing permissions piecemeal is not good for architecture, this should be part of #7466