Getting Started

Install the package from Packagist:
```
composer require goldnead/statamic-teams
```
v0.1.1 is the first release that can be installed normally from Packagist; earlier versions were blocked by minimum-stability: dev and a dev-branch requirement in the package’s composer.json.
After install, check the package README and config/statamic-teams.php (publish it if the package provides a publish tag) for team model, migration, and route registration details.
Look first at how teams relate to Statamic users: the package is likely to expose a Team model, a user-to-team relationship, and role/permission handling. Start by creating a team, attaching a user, and assigning a role in a test environment.
First practical use case: add team-scoped access to an existing Statamic site by creating a team, attaching users, and protecting a route or control-panel area with the package’s middleware/policy integration.

Implementation Patterns

Treat teams as a tenancy boundary. Scope Eloquent queries and Statamic content access by the current team, and resolve the active team early in the request lifecycle (middleware, session, or user preference).
Integrate with Statamic’s user model through the package’s relationship methods rather than duplicating pivot logic. Use the package’s role/permission checks in policies and gates.
Use a team-context middleware for routes that require team membership, and fall back to a clear 403/404 when no active team is resolved.
For control-panel usage, verify whether the package registers navigation, permissions, or widgets; if not, wire team management into your own CP pages using the package models.
Keep root composer.json stability settings clean. With v0.1.1 you should not need minimum-stability: dev or a dev-branch constraint for this package.
Pin to a stable constraint such as ^0.1 while the package is pre-1.0, and run composer update goldnead/statamic-teams --with-dependencies deliberately rather than floating.

If installation still fails after upgrading, clear Composer’s cache and lock file state:
```
composer clear-cache
composer update goldnead/statamic-teams --with-dependencies
```
Remove any leftover minimum-stability: dev or prefer-stable: false settings in your root composer.json that were added to work around the old package metadata.
Check dependency compatibility carefully. v0.1.1 changes the package to require ^0.4 and stable; confirm that constraint is compatible with your Statamic/Laravel versions before deploying.
This is still a very early release (0.1.x). Expect API and schema changes; read the changelog before every minor bump and avoid relying on undocumented internals.
Debug team resolution by logging the active team ID and the user’s team memberships at the middleware boundary. Most authorization failures in team packages come from a missing or stale active-team context.
Extension points to inspect: published config, policy/gate registration, model swap support, and any events fired on team membership or role changes. Prefer these over modifying vendor code.