- What is goldnead/statamic-teams used for?
- goldnead/statamic-teams is a Statamic addon for Laravel applications that organizes users into teams. It provides memberships, roles, and team-aware access control so you can scope content or permissions per team. Teams are managed from the Statamic control panel.
- How do I install goldnead/statamic-teams in a Laravel Statamic app?
- Install it with Composer using composer require goldnead/statamic-teams, then register the addon following the standard Statamic addon registration for your version. This release adds no migration and no new config key, so there is no schema step or settings re-entry for existing installs. Check the repository README for the exact registration snippet for your Statamic version.
- Does this addon require database migrations or new configuration?
- No. The v0.4.2 release explicitly states there is no migration and no new config key. Existing configuration persists unchanged, and only the control panel mount point for the settings screen changes.
- Which Laravel and Statamic versions does goldnead/statamic-teams support?
- The package is built for Laravel and Statamic, but the provided release notes do not declare specific Laravel or Statamic version constraints. Check the composer.json in the goldnead/statamic-teams repository for the authoritative requirement. v0.4.2 does not change installation or runtime requirements.
- What changed in the control panel navigation in v0.4.2?
- v0.4.2 adds settingsNavParent(), which returns a [section, name] tuple identifying the addon's own control panel navigation entry. When statamic-brand-context 1.16 or newer is installed, the addon's settings render as the sub-item Einstellungen beneath that nav entry. On older brand-context versions the method is ignored and the previous layout persists.
- Is statamic-brand-context required for goldnead/statamic-teams?
- No. It is an optional integration, not a hard Composer dependency. With brand-context older than 1.16 the method is ignored and the previous layout persists; confirm the absent-package case in staging, because the release notes focus on version gating rather than complete absence.
- Why does my control panel show a different settings layout than another install?
- Because the new settings placement is version-gated on statamic-brand-context 1.16 or newer. Installs with 1.16+ show the settings as Einstellungen beneath the addon nav entry, while installs with an older version keep the legacy layout with no warning. That silent divergence is expected and should be documented for support.
- Can I translate the Einstellungen label used in the control panel?
- The release uses the literal sub-item label Einstellungen, and the provided notes do not confirm a translation key. If your control panel is not German, verify the rendered label and check whether the addon publishes language files you can override. Treat translation as a configuration and documentation question until confirmed in the repository.
- Will multiple addons using a shared Addon-Suite page cause navigation collisions?
- There is a real risk when several addons declare settings under a shared Addon-Suite page, because Einstellungen is a generic sub-item name. The [section, name] tuple also appears unvalidated at the contract boundary. Test the combined control panel navigation in staging and confirm label uniqueness and ordering with the other addon vendors.
- Is upgrading to v0.4.2 safe for production team management?
- For existing installs, upgrading to v0.4.2 is low risk: there is no migration, no new config key, and no new service to boot. The main production concern is the optional brand-context gating, which can produce two different control panel layouts across environments. Test the CP navigation and team-aware permissions in staging before rolling out fleet-wide.