romegasoftware/workos-teams

Extends Laravel WorkOS integration with team/organization functionality

v0.1.0 2025-03-31 23:41 UTC

Requires

• php: ^8.2
• illuminate/database: ^11.0|^12.0
• illuminate/http: ^11.0|^12.0
• illuminate/support: ^11.0|^12.0
• laravel/workos: ^0.2
• ramsey/uuid: ^4.0
• workos/workos-php: dev-main as 4.22.0

Requires (Dev)

• livewire/flux: ^2.0
• livewire/livewire: ^3.0
• livewire/volt: ^1.6.7
• orchestra/testbench: ^9.0|^10.0
• phpstan/phpstan: ^2.0
• phpunit/phpunit: ^11.0
• psalm/plugin-laravel: ^3.0
• vimeo/psalm: ^6.8

MIT

• RomegaSoftware

README

This package extends the Laravel WorkOS integration with team + organization functionality. It provides a migration path for users transitioning from Jetstream Teams to WorkOS Organizations.

Features

• Feature parity with Jetstream Teams
• Can be integrated into new or existing Laravel applications
• Integrates with WorkOS Organizations
• Team invitation and member management
• Organization and user synchronization with WorkOS
• Livewire components for team management (optional)
• Webhooks for WorkOS events
• Repository pattern for modular implementation

Docs

1. Installation and Configuration
2. Webhooks
3. Livewire Components
4. Customization
5. Coming soon: Console Commands

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

The MIT License (MIT). Please see License File for more information.

Jetstream Feature Parity

As Jetstream is being replaced by Starter Kits, and Laravel's documentation is encouraging developers to utilize WorkOS, I noticed a gap with developers wanting to use the Teams functionality they once had with Jetstream. My goal with building this package was to utilize the functionality WorkOS makes avaialable through Organizations, and pair it with the naming conventions we are used to with Jetstream. Therefore, we keep the "Teams" language in this package.

A few known differences with Jetstream:

• Permissions: We are only utilizing Roles currently. There is no Permissions implementation, though we do have plans to implement.
• Inertia: I would accept contributions providing an Inertia UI. I do not have a need for this myself right now, so I do not have active plans to implement.
• Features::profilePhotos: We do not have any current or planned implementation for profilePhotos at this time. This can easily be implemented directly on your User model while making the necessary UI adjustments to accommodate through the published components.
• Features::api: Jetstream provided an interface for managing Sanctum API tokens. I am of the mindset that this package should focus on Teams, and even to the extent that we provide Livewire components but do not require Livewire for implementation. Doing so, we are frontend agnostic. Since Jetstream just provided a UI wrapper for Sanctum, that could be managed in a separate package. No plans to implement.
• Profile Management: Profile Management is handled with the Laravel WorkOS starter kit.

If you notice any other differences that should be included, feel free to open an issue or a pull request.