-
Notifications
You must be signed in to change notification settings - Fork 169
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.
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
Add support for Teams to PermissionManager #310
Comments
Hello there! Thanks for opening your first issue on this repo! Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that. Backpack communication mediums:
Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch. Thank you! -- |
Hmmm... I didn't even know Spatie added Teams to this package, thanks @AkikiCharbel . https://spatie.be/docs/laravel-permission/v5/basic-usage/teams-permissions#breadcrumb We'll should add teams support, I agree. For now though, please roll your own solution. You should be able to use your own models, which extend the ones in this package - that will give you full control. |
@tabacitu hello, I didn't use spatie permission as it is because spatie doesn't let a user have the same roles or permissions in different teams, so I made some changes in the spatie package, but I will check again to see if I can help with it. |
It would be nice to have that feature. I'm just implementing on existing backpack project a multi company feature and It's part of the roadmap to have permissions set for each company. |
Same here; planning to build a multi-tenant/team based app and using Backpack for most of the features. Having Spatie permissions support would be great! @AkikiCharbel would be interested to see what changes you’ve implemented. I was’t aware of this limitation with the Spatie package… |
Totally agree we should do this. Thanks for the idea and feedback, guys! I've tagged so we do it in March 2023. Until then the team is super-busy working on Backpack v6 😱 |
Amazing |
I just ran into the same issue, is there any update on this? |
I added this to my setup in UserCrudController and got it to work:
|
any news on this update? |
Has anyone successfully integrated team support into Laravel-Backpack PermissionManager, akin to the functionalities seen in Spatie's permissions package? If you have navigated this challenge, could you kindly share your approach or provide a guide on your implementation process? |
The message I sent back in August is what I did, and it works for me. Just put it directly into your |
Thank you for fast response.
Thank you for this quick solution. Still hopes that this amazing backpack team will find time and resources to provide us full implementation solution as a guide or package upgrade. |
Can't find teams part to work with it
What I did:
created a team crud but forgot that team id will be user in model has permissions and model has roles
I expected when using setPermissionsTeamId(teamId) (spatie function) in my api to get all the permission of the user inside this team
but as i can't access model has permission and set my team id
so what's happening is that the logged in user have no permission in the team even that he was assigned to the team
i tried to create a crud for users that belongs to a team but it will be a long process to assign a permission to a user inside a team, any idea that can help or any team section in permissionManager that I don't know about it?
I'm using laravel 8 and 9, with backpack 4 and 5
The text was updated successfully, but these errors were encountered: