Nova Impersonating Banner Laravel Package

Product Decisions This Supports

• Admin/support tooling safety: This package exists to prevent a real operational failure mode — a support agent impersonating a customer, forgetting, and taking destructive action as that customer. A persistent banner is a cheap guardrail on top of an impersonation workflow.
• Roadmap: Laravel 12 upgrade. v3.2.0 adds Laravel 12 support, which removes this package as a blocker in a framework upgrade. If we are planning a Laravel 11 → 12 migration, this release means the dependency can stay in the tree rather than be forked, patched, or dropped.
• Build vs. buy: The functionality is small enough to approximate in-house (a Nova custom tool or a Blade partial that reads the impersonation session flag). Buying/installing wins only if it is genuinely zero-config and we want to avoid owning another internal snippet; build wins if we need custom behavior (e.g., logging impersonation events, restricting which roles can impersonate).
• Feature scope for impersonation: If impersonation is a supported customer-support workflow, this is a candidate for inclusion in the standard Nova toolset alongside audit logging. It does not enable impersonation itself — it is a presentation-layer add-on to whatever impersonation mechanism we already run.
• Use cases: customer-support "view as customer" debugging, sales demo environments, QA verifying role-based permissions, internal admin troubleshooting of account-specific issues.

When to Consider This Package

Adopt when all of the following hold:

• We run Laravel Nova for internal admin (this package is Nova-specific — no plain Laravel or Filament equivalent).
• Impersonation is already implemented via another package or custom code; this banner is a complementary UI layer, not a standalone feature.
• We want a minimal, low-maintenance dependency rather than maintaining our own Nova asset/tool for the same banner.
• Our Nova version is compatible with Laravel 12 (verify Nova's own Laravel 12 support before relying on this release during upgrade).

Look elsewhere or build in-house when:

• We are not on Nova, or are evaluating a move off Nova — the package has no value outside that ecosystem.
• We need auditability (who impersonated whom, when, what actions were taken). A banner is a visual reminder, not an audit trail; pair it with server-side logging or a dedicated impersonation package.
• We need hard controls (blocking sensitive actions while impersonating, read-only impersonation). That is authorization logic, not a banner.
• The package's maintenance cadence is a concern for a critical admin path — it is a single-maintainer community package, and this release is compatibility-only, which is a signal the feature surface is stable but also that the project is in low-activity maintenance mode.

How to Pitch It (Stakeholders)

For executives: A small, free add-on for our internal admin panel that displays a visible warning whenever a staff member is viewing the system as a customer. It reduces the risk of support staff accidentally making changes to the wrong account, and its latest release keeps it compatible with our planned Laravel 12 upgrade at effectively zero cost.

For engineering: v3.2.0 is a compatibility-only release — Laravel 12 support, no new APIs, no breaking changes, no deprecations. It is a thin Nova front-end that renders a banner when an impersonation session is active; it does not implement impersonation, authorization, or logging, so it must sit alongside our existing impersonation mechanism and any audit logging we require. Integration is minimal (install, register, configure banner text/behavior), but it does add a single-maintainer community dependency to the admin path — worth a quick check that our Nova version supports Laravel 12 before we treat the upgrade path as unblocked. Recommended action: low-risk trial in staging alongside our impersonation flow; if we need logging or restriction of impersonated actions, scope that separately rather than expecting it here.