Replacing Jetstream teams roles and permissions with Spatie permission team feauture

[kaspernowak]

Hello All,
I originally implemented the teams feature from laravel jetstream into my laravel breeze app, including the role and permissions approach used by jetstream. Now I need to implement global roles and permissions, where I found Spatie Permissions useful. Then I found out that Spatie Permissions can be installed with a teams feature as well, which made me pivot towards using Spatie Permissions for my Team roles and permissions as well.

Now it seems like I have hit a wall, where I am not sure that the Spatie Permissions teams feature can replace the Jetstream teams feature, in the way that Jetstream sets the team roles and permissions in a serviceprovider, where roles can be added or removed and permissions can be changed dynamically, affecting all existing and future teams.
Where in what seems to be the case for Spatie Permission teams, roles should be created for each team, even though all teams need the same roles and permissions, making it difficult to manage team roles from, say, something like one centralized service providers boot method.

I am not sure I understand the Spatie Permission teams feauture correctly, but if I understand it correctly, I don't see the point of why anyone would want to use it?

Maybe it is best to keep using the implemented role and permission setup from jetstream for my teams, and use spatie for global roles and permissions?

Does anyone have experience with using both jetstream teams and spatie permission teams, and know if I could successfully pivot to spatie permission with teams, or if I should stick with my existing implementation and live with having to manage roles from 2 different methods in my app?