Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The user should not be able to view the admin's leads if the user has individual permission. #732

Closed
Sanjaybhattwebkul opened this issue Nov 22, 2021 · 1 comment
Closed

The user should not be able to view the admin's leads if the user has individual permission. #732

Sanjaybhattwebkul opened this issue Nov 22, 2021 · 1 comment
Assignees
@shagun2405
Labels
Bug Fixed Bug
Milestone
v1.2.3

Comments

@Sanjaybhattwebkul
Copy link
Contributor

CRM Version: V1.2.1

Steps To reproduce--

1. Log in as Admin/User.
2. Click on link lead inside inbox and link a lead created by admin.
3. Create a new user and give individual permission.
4. log in as a new user.
5. Try to view the linked lead.

Actual result: Even if the user has individual permission, he can still see the admin's lead. Using Link Leads. Please find the screenshot Here.

Expected result: The user should not be able to view the admin's leads if the user has individual permission.
shagun2405 pushed a commit to shagun2405/laravel-crm that referenced this issue Aug 23, 2022
Issue krayin#732 fixed
7ce9522
@shagun2405 shagun2405 mentioned this issue Aug 23, 2022
Closed
shagun2405 pushed a commit to shagun2405/laravel-crm that referenced this issue Aug 23, 2022
Issue krayin#732 fixed
2b03007
@shagun2405 shagun2405 mentioned this issue Aug 23, 2022
Merged
@Sanjaybhattwebkul Sanjaybhattwebkul added this to the v1.2.3 milestone Aug 23, 2022
jitendra-webkul added a commit that referenced this issue Aug 25, 2022
@jitendra-webkul
Merge pull request #1045 from shagun2405/lead_permission_issue
53e4004 
Issue #732 fixed
@Sanjaybhattwebkul
Copy link
Contributor Author

@jitendra-webkul
Now, this issue is fixed. so I am closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shagun2405 shagun2405

Labels
Bug Fixed Bug
Projects
None yet
Milestone
v1.2.3
Development

No branches or pull requests
3 participants
@jitendra-webkul @Sanjaybhattwebkul @shagun2405