Client Portal Laravel Package

Product Decisions This Supports

• Build vs. buy for a client-facing portal: Supports buying a Statamic-native client portal instead of building account management, client roles, portal views, and content-managed client-facing screens from scratch.
• Roadmap prioritization: v1.1.1 is a security-hardening release; teams should prioritize upgrading to at least v1.1.1 and auditing any custom portal templates or overrides for unescaped client-visible fields.
• Licensing and packaging decisions: The package now explicitly requires Statamic Pro, because client accounts and a client role are not available in Statamic Core. This changes total cost of ownership and should be factored into pricing, agency retainers, and product eligibility.
• Use cases: Appropriate for agencies or product teams running Statamic/Laravel sites that need a simple authenticated client portal for project status, phases, modules, descriptions, file names, and branded login content.
• Security/compliance gate: The XSS fix for portal titles and other plain-text client-visible fields supports a “minimum secure version” policy for any client-facing deployment.
• Adoption decision: Treat as a viable buy candidate where the stack is Statamic Pro and the portal needs are moderate; pause adoption where Statamic Pro licensing, enterprise IAM, or complex permissions are required.

When to Consider This Package

Consider this package when:

• The product is built on Statamic/Laravel and can use Statamic Pro.
• You need client accounts and a client role without building custom authentication and authorization.
• The portal requirements fit content-managed client-facing screens such as project status, phases, modules, descriptions, files, and login messaging.
• You want to avoid maintaining custom portal infrastructure and are comfortable with a third-party addon.
• You can enforce a minimum version of v1.1.1+ and have a process for promptly applying security patches.
• You can audit custom templates/overrides to ensure client-visible plain-text fields are escaped.

Look elsewhere when:

• You are on Statamic Core only or cannot license Statamic Pro.
• You need enterprise identity features such as SSO, SCIM, fine-grained permissions, complex approval workflows, or advanced audit logging.
• The application is not Laravel/Statamic or the portal must be deeply integrated into a separate customer platform.
• You cannot accept third-party addon dependency or cannot patch client-facing security issues promptly.
• The portal needs a fully custom UX or business logic beyond the package’s supported client portal model.

How to Pitch It (Stakeholders)

For executives: This package can accelerate delivery of an authenticated client portal on a Statamic/Laravel stack, reducing custom build effort for client accounts, roles, and content-managed portal screens. The latest release fixes a client-visible XSS issue, so adopting it requires upgrading to at least v1.1.1. The key commercial caveat is that it now explicitly requires Statamic Pro, so budget for that license and treat it as part of the total cost. Recommended position: approved for a pilot or limited rollout where Statamic Pro is already available; otherwise evaluate licensing before committing.

For engineering: v1.1.1 is a security patch and requirements clarification. Upgrade to at least v1.1.1, confirm Statamic Pro is installed and licensed, and regression-test /portal with client accounts and the client role. Audit custom templates and portal overrides for unescaped client-visible plain-text fields, especially names, titles, statuses, descriptions, button labels, file names, and login content. Pin the minimum secure version and include this package in routine dependency/security review.