README

A native Filament plugin for venturedrake/laravel-crm. Wraps the existing CRM domain layer (models, services, observers, policies, encryption, audit) in Filament Resources, Clusters, Pages, and Widgets so the same database can be administered via Filament alongside (or instead of) the legacy /crm MaryUI/Livewire interface.

Requirements

PHP ^8.2
Laravel ^11.0 | ^12.0 | ^13.0
Filament ^4.0 | ^5.0
venturedrake/laravel-crm ^2.4

Installation

composer require venturedrake/laravel-crm-filament
php artisan laravelcrm:filament-install

The install command first checks whether venturedrake/laravel-crm itself has been installed (by looking for config/laravel-crm.php). If it hasn't, you'll be asked whether to run php artisan laravelcrm:install first — say yes and the underlying CRM package's config, migrations, seed data, and owner user will be set up before the Filament panel is wired up. Pass --skip-crm-install to bypass this check.

Once the CRM package is confirmed installed, the command inspects the host app for existing Filament panels and drives an interactive prompt:

No panels detected → publishes a standalone CRM panel automatically.
Only the plugin's own crm panel already installed → re-runs the standalone publish (use --force to overwrite).
One or more other panels detected → asks whether to publish a standalone /crm panel or inject the plugin into an existing panel.

Either way it publishes and runs the plugin's own migration, records the panel database version it has just brought the schema up to (so a fresh install does not report an update it has already applied), and appends @php artisan laravelcrm:filament-upgrade --ansi to your composer.json post-autoload-dump scripts, so future composer install runs clear the cached Filament panel components for you — see Updating. Pass --no-composer-hook to skip that. If your composer.json cannot be parsed it is left untouched and the line to add is printed instead.

Branch A — standalone `/crm` panel

Publishes app/Providers/Filament/CrmPanelProvider.php (id crm, path /crm) and registers it in bootstrap/providers.php. This is the default when no other panels exist.

Because the core CRM ships a Livewire UI that also lives at /crm, the command then prompts:

Add LARAVEL_CRM_USER_INTERFACE=false to your .env now (disables the legacy /crm Livewire UI so the Filament CRM panel can take over /crm)?

Answer yes to have the command append the line for you. Answer no to keep both UIs — you'll need to either set LARAVEL_CRM_USER_INTERFACE=false manually later or change the panel path in the published CrmPanelProvider. If the config is already false (via env or config edit), the prompt is skipped.

Branch B — inject into an existing panel

Adds ->plugin(LaravelCrmPlugin::make()) (plus the matching use import) directly to the target panel's PanelProvider file. Nothing is published — the plugin becomes part of the host's existing panel.

Before injecting, the command builds a slug map from the target panel's registered resources and the plugin's own resources. If any slugs collide, the injection is aborted with a table of colliding slugs; re-run with --mode=crm (standalone panel) or resolve the collision in your host app. Pass --force to inject anyway.

Scripting the install (CI / provisioning)

The prompts can be bypassed with flags:

Flag	Effect
`--mode=crm`	Force Branch A (standalone `/crm` panel), no interactive choice
`--mode=inject --panel=<id>`	Force Branch B injection into panel `<id>`
`--force`	Overwrite an existing `CrmPanelProvider.php` (Branch A) or bypass slug-collision detection (Branch B)
`--skip-crm-install`	Skip the `venturedrake/laravel-crm` install check (assume it has already been installed)
`--modules=leads,deals,…`	Comma-separated module list forwarded to `laravelcrm:install` (requires `laravel-crm` 2.3.0+)
`--allow-teams`	Install onto a CRM with `LARAVEL_CRM_TEAMS=true` anyway. The panel is not tenant-aware — see Multi-tenancy
`--no-composer-hook`	Do not add `laravelcrm:filament-upgrade` to your `composer.json` `post-autoload-dump` scripts — see Updating

Example — non-interactive injection into an existing admin panel:

php artisan laravelcrm:filament-install --mode=inject --panel=admin --force

Add Filament\Models\Contracts\FilamentUser to App\Models\User and implement canAccessPanel():

use Filament\Models\Contracts\FilamentUser;
use Filament\Panel;
use VentureDrake\LaravelCrm\Traits\HasCrmAccess;

class User extends Authenticatable implements FilamentUser
{
    use HasCrmAccess;

    public function canAccessPanel(Panel $panel): bool
    {
        return $this->hasCrmAccess();
    }
}

Updating

Two commands, mirroring the split venturedrake/laravel-crm uses:

Command	Does	When
`laravelcrm:filament-upgrade`	Clears the cached Filament panel components, config, routes and views. Never touches the database, never prompts.	Automatically, from your app's `post-autoload-dump` composer hook — so `composer install` on a production box does it too
`laravelcrm:filament-update`	Runs `laravelcrm:filament-upgrade`, then `laravelcrm:update`, then publishes and runs this package's migrations. Exits non-zero if any of it fails.	Explicitly, by you or your deploy script

laravelcrm:filament-update runs laravelcrm:update before its own migrations — core's schema underneath the panel's, since crm_invoice_payments carries foreign keys into core's tables. So a normal upgrade is two lines, not four:

composer update venturedrake/laravel-crm venturedrake/laravel-crm-filament
php artisan laravelcrm:filament-update

Pass --skip-crm-update if core is already up to date and you only want this package's half.

The cache-clearing half matters more here than it looks: Filament caches the panel's discovered components under bootstrap/cache/filament/, and a stale cache after an upgrade means new CRM resources and pages simply do not appear. laravelcrm:filament-install adds the hook that clears it to your composer.json for you. Panels installed before this release need to add it once, by hand (the CRM package adds its own line, so a host running both ends up with two):

"scripts": {
    "post-autoload-dump": [
        "@php artisan package:discover --ansi",
        "@php artisan laravelcrm:upgrade --ansi",
        "@php artisan laravelcrm:filament-upgrade --ansi"
    ]
}

Order matters: package:discover has to run before either package's artisan command can resolve.

On a production deploy:

composer install --no-dev --optimize-autoloader   # the hook fires laravelcrm:filament-upgrade
php artisan laravelcrm:filament-update --force    # core update + panel migrations, non-interactive
php artisan config:cache && php artisan route:cache && php artisan view:cache

Settings → Updates in the panel reports both versions and tells you when either database is behind its code; the same information reaches every panel page as a dismissible banner. Neither runs anything — applying an update is a console step, taken with a backup in reach.

Registering the plugin

use VentureDrake\LaravelCrmFilament\LaravelCrmPlugin;

->plugin(
    LaravelCrmPlugin::make()
        // ->modules(['leads' => true, 'deals' => true, /* ... */])
        // ->withChat()
        // ->withEmailMarketing()
        // ->withSmsMarketing()
        // ->withCustomers()
        // ->withXero()
        // ->withFeatures()
        // ->withMonitoring()
        // ->withTeams()                 // the CRM *teams module*, not multi-tenancy
        // ->allowUnsupportedTenancy()   // acknowledge LARAVEL_CRM_TEAMS=true; see Multi-tenancy
        // ->navigationGroup('CRM')
        // ->brand('Acme CRM')
        // ->brandLogo('https://example.com/logo.svg')
        // ->favicon('https://example.com/favicon.ico')
        // ->primaryColor('#05b3a9')
)

By default the plugin reads config('laravel-crm.modules') to decide which gated resources to register. Use ->modules([...]) to override per-panel; the with*() methods are shorthands for a single key of that array.

->withTeams() toggles the CRM teams module — a way of grouping users, which gates CrmTeamResource. It is unrelated to LARAVEL_CRM_TEAMS, the multi-tenancy switch; see Multi-tenancy. ->allowUnsupportedTenancy() acknowledges the latter and silences its warning.

If no brand() / brandLogo() is set the plugin falls back to the core CRM's laravel-crm.settings: organization_name and logo_file. If no primaryColor() is set the panel defaults to #05b3a9 (the CRM's teal accent).

Feature catalog

The panel was built up in phases. Each phase below maps to a chunk of functionality in the plugin.

v0.5 — Pipeline conversion actions + PDF download

Quote → Order, Order → Invoice, Order → Delivery, Order → Purchase Order conversion actions on the respective View pages, all routed through the core CRM services (OrderService, InvoiceService, DeliveryService, PurchaseOrderService) so observers, audits, and Xero sync still fire.
Each conversion stamps the back-link FK (quote.accepted_at, order.quote_id, invoice.order_id, etc.), opens an in-app notification with a deep link to the new record, and hides itself once the downstream record exists.
Shared Concerns\DownloadsPdf trait powers both the Send … mail action and a standalone Download PDF header action on Quote / Invoice / Purchase Order View pages.

v0.6 — CSV bulk imports

Header Import CSV action on People, Organizations, Products, and Users list pages. The action exposes:

File upload + header-row toggle.
Reactive column-mapping selects populated from the uploaded CSV's headers.
Dedupe field (e.g. lowercased email, code).
Chunk size for batch processing.
Download sample CSV footer action that streams a UTF-8-BOM template.

Importers route through the core CRM services (PersonService, OrganizationService, ProductService) and respect the encryption-at-rest setting (laravel-crm.encrypt_db_fields).

v0.7 — Standalone activity/file resources + polymorphic Files RM

Top-level read-only resources: Notes, Calls, Meetings, Lunches, Files, Activities — each shows global lists of the entity across all parents, with an Open parent record action that deep-links back into the owning resource.
FilesRelationManager added to every parent resource (Lead, Deal, Person, Organization, Quote, Order, Invoice, Purchase Order, Delivery). Uploads write a File model row with full metadata and log an entry on the parent's activity timeline.

v0.8 — Campaign send-now, per-recipient analytics, performance widgets

Send now header action on Email + SMS Campaign View pages (with recipient-count confirmation modal).
Performance infolist section with sent / failed / skipped counts and open-rate / click-rate / unsubscribe-rate (email) or delivery-rate / click-rate / unsubscribe-rate (SMS).
Per-recipient RelationManager columns: last_opened_at, first_clicked_at, bounce_status (email); delivered_at, clicksend_message_id with copy-to-clipboard (SMS).
Footer Sends over time chart on each campaign View page (auto-hides for sub-hour spans).
Dashboard CampaignPerformanceChart widget for the last 5 sent email campaigns.

v0.9a — Customer resource + lookup resources

CustomerResource (slug customers) — full CRUD with encrypted global search, Files RM, gated on the customers module (->withCustomers()).
Settings-cluster lookup resources: Contact Types, Address Types, Organization Types, Industries, Timezones, Product Attributes (all List+Create+Edit).
Industry select on OrganizationResource::form().
ProductVariationsRelationManager on the Product resource (name + description + attribute select).

v0.9b — Lead/pipeline lookups + Teams + Updates page

LeadStatus + PipelineStageProbability lookup resources in the Settings cluster.
lead_status_id Select on the Lead form; pipeline_stage_probability_id Select on the Pipeline Stage form.
CrmTeams resource in the Settings cluster with a TeamMembersRelationManager for attaching multiple users via crm_team_user.
Updates page (Settings cluster) showing both installed versions side by side, both latest published releases, and whether either database is behind its code, plus a read-only Check for updates action. Core's latest comes from the CRM version API; the panel's comes from Packagist, which is where composer update reads it from too. The page reports; it never runs laravelcrm:filament-update — upgrades stay a console step. See Updating.

v0.10 — Calendar, Task kanban, Reminders settings

Standalone Calendar page rendering Tasks (by due_at) + Calls/Meetings/Lunches (by start_at) in a FullCalendar month/week grid. Drag-to-reschedule updates the underlying record and writes an activity row.
Task Kanban sub-resource page (Open / Today / Overdue / Completed columns) with drag-to-complete.
Reminders settings page — per-type (Task / Call / Meeting / Lunch) checkbox + hours_before input, persisted as user-scoped Setting rows.

v0.11 — Chat widget embed UI, portal preview, branded auth

ChatWidget View page renders the embed <script> snippet with copy-to-clipboard and a live <iframe> preview of the widget.
Quote / Invoice Preview portal action promoted to a primary header action.
Branded Login + Profile auth pages: avatar upload (persisted to Setting), section grouping, link to the Reminders settings, and panel-level brand pickup from SettingService (organization_name, logo_file, primary_color) in CrmPanelProvider.

v1.1 — core 2.4.0 parity

Task start_at on the task form, infolist, table and CSV export, plus calendar spans and span-preserving drag. Core's TaskService writes start_at unconditionally, so a form without the field cleared it on every save.
User invitations on core's UserInvitation lifecycle, with a panel-owned acceptance page (see below) and an index-only pending list.
Settings → Templates, the PDF template picker, with inline thumbnails and an in-panel PDF preview.
Per-record PDF templates on Quote, Order, Invoice, Purchase Order and Delivery.
Decimal line-item quantities (decimal(15,3)) with server-side drawdown validation.
System-check banner rendered through Filament's CONTENT_START hook, sharing core's dismissal key.

User invitations

Inviting a user mints a UserInvitation and mails a one-time link. The host user is created — or, for someone who already has an account, granted CRM access and the invited role — only when the invitee redeems it. Nothing is written up front, so a mistyped address costs nothing and does not burn the unique email index.

Acceptance is a plugin-owned panel route, /{panel}/invitations/accept/{code}, registered outside the panel's auth middleware because the invitee is by definition not a panel user yet. Core's own acceptance routes live in Http/routes.php, which LaravelCrmServiceProvider::registerRoutes() only loads while laravel-crm.user_interface is true — and this plugin's own installer offers to set that to false so the panel can own /crm. In that recommended configuration core's route('laravel-crm.users.invitations.accept') throws inside a queued notification: the admin sees "invitation sent" and the invitee never hears anything. Support\InvitationUrl resolves the panel route first and falls back to core's when the base UI is on; when neither exists the invite action refuses before writing anything.

Three things worth knowing:

Resending does not rotate the code. An invitee who kept the first mail is not locked out by an admin clicking Resend; only last_sent_at changes. This matches core.
Invitations do not expire. Core's are open-ended, and the plugin omits expires_at for the same reason. Revoke (soft-delete) is how you take one back.
The pending list has an index page and nothing else. UserInvitation's route key is the 64-character redemption secret, so a View or Edit page would put it in a URL — and from there into browser history, referrer headers and every access log in between.

Invitations are reached from Users → Pending invitations, which carries a count badge.

Multi-tenancy (not supported)

This plugin is single-tenant. It does not support core's LARAVEL_CRM_TEAMS=true.

Core's BelongsToTeamsScope would scope the CRM models the plugin's resources are built on for free. The exposure is everything outside those models, and there is a lot of it: the Spatie roles and permissions queries, the host users table, the CRM teams list — and there is not one Filament::getTenant() call anywhere in this package. A panel that half-scopes is worse than one that says plainly it does not scope, because it looks tenanted right up to the row that isn't.

So the posture is: refuse at install, warn at runtime, implement nothing.

php artisan laravelcrm:filament-install stops when laravel-crm.teams is on. Pass --allow-teams to install anyway.
A running panel logs a warning and shows a banner. It never throws — throwing from a service provider would break config:cache, migrate and queue:work, and would brick a host that flipped the flag after installing.
LaravelCrmPlugin::make()->allowUnsupportedTenancy() silences the banner, so running anyway is a recorded decision in your panel provider rather than a notice somebody stopped reading.
The user CSV import and the invite action are hidden entirely when teams are on. Use core's tenant-aware /crm/users instead.

Note this is laravel-crm.teams (multi-tenancy), not the teams entry in config('laravel-crm.modules'). The latter is the CRM teams module — a way of grouping users — which the plugin does support, and which gates CrmTeamResource.

Permissions

Every resource routes through core's policies, which read the Spatie permissions seeded by php artisan laravelcrm:permissions (or laravelcrm:update). The plugin's Pages have no core policy, so they declare a permission directly:

Page	Permission
Dashboard	(ungated — a user who can reach the panel has to land somewhere)
Activity feed	`view crm activities`
Calendar	`view crm activities`
General settings	`view crm settings` (writes need `edit crm settings`)
Templates	`view crm settings` (writes need `edit crm settings`)
Integrations	`view crm settings` (writes need `edit crm settings`)
ClickSend integration	`view crm settings` (writes need `edit crm settings`)
Reminders	`view crm tasks` (they are per-user task nudges, not org settings)
Updates	`view crm updates`

The dashboard's three data widgets — contacts stats, tasks due today and recent activity — additionally check view crm contacts, view crm tasks and view crm activities.

Two notes for upgrades:

Product attributes are now permission-gated. Before core 2.4.0 no policy resolved for them, and Filament allows when it finds none — so the resource was reachable by every panel user. It now enforces view|create|edit|delete crm product attributes.
Re-seed after upgrading. Core's policies call hasPermissionTo() unguarded, which throws when a permission row is missing. The plugin catches that on the policied resources so you get a 403 rather than a 500 — but the fix is to run php artisan laravelcrm:update.

The Pages' own checks deliberately fail open on an install that never seeded the permission (and log a warning when they do), so an upgrade cannot lock an operator out of their own settings. The resource-level checks do not: those fail closed.

Support classes

The plugin ships a handful of small Support\* classes that exist because core's equivalent is route-gated, protected, or bound to App\Models\User. Each carries a docblock naming the upstream fix that would let it be deleted.

Class	Why it exists
`CrmPdf`	One place a CRM document becomes a PDF, resolving the view through `PdfTemplateRegistry` instead of a hardcoded path
`PdfTemplatePreview`	Core's `TemplatePreviewController::sampleData()` is `protected` and its routes are behind `laravel-crm.user_interface`
`PortalUrl`	Route-guards core's portal routes, which do not all exist
`PurchaseOrderPortalLink`	The purchase-order portal link and its mail placeholder
`InvitationUrl`	Resolves the accept-invitation link, panel route first
`InvitableEmail`	Core's `UserInvite` email rules as a `ValidationRule`, because Filament evaluates bare closures in `->rules()` as its own
`UserInvitationAcceptor`	The acceptance branches and core's fail-closed Owner check, which is `protected` upstream
`UserGate`	Core registers `UserPolicy` against the literal `App\User` / `App\Models\User` strings, so the Gate denies on any other host model
`RemainingQuantity`	Core's `QuantityWithinRemaining` derives its row index from the attribute path, which silently no-ops inside a Filament Repeater
`OrderDrawdownPrefill`	One implementation of the outstanding-quantity prefill, shared by the page action and the table row action
`MoneyForm`	The cents-to-form conversion, delegating to core's `Money`
`TenancyGuard`	The single multi-tenancy message, shared by the installer, the log line and the banner
`LogoUrl`	Browser-facing logo URLs (PDFs use core's `PdfLogo` instead)
`FormPayload`	Wraps a Filament form array as the `Fluent` core's services expect
`ParentTypeOptions`	Polymorphic parent-type options for the standalone activity resources

What's in the panel

Main panel resources (gated on config('laravel-crm.modules')):

Paths below assume the default /crm mount from the published CrmPanelProvider; adjust if you've changed ->path(...) or injected the plugin into a differently-mounted host panel.

Resource	Slug	Module gate
Lead	`/crm/leads`	`leads`
Deal	`/crm/deals`	`deals`
Quote	`/crm/quotes`	`quotes`
Order	`/crm/orders`	`orders`
Invoice	`/crm/invoices`	`invoices`
Purchase Order	`/crm/purchase-orders`	`purchase-orders`
Delivery	`/crm/deliveries`	`deliveries`
Email Campaign	`/crm/email-campaigns`	`email-marketing`
SMS Campaign	`/crm/sms-campaigns`	`sms-marketing`
Chat	`/crm/chat`	`chat`
Customer	`/crm/customers`	`customers`
Person	`/crm/people`	always
Organization	`/crm/organizations`	always
Task	`/crm/tasks`	always
Product	`/crm/products`	always
Notes / Calls / Meetings / Lunches / Files / Activities	`/crm/{slug}`	always (read-only global views)

Standalone pages:

/crm/calendar — month/week grid for tasks + calls + meetings + lunches.
/crm/leads/kanban, /crm/deals/kanban, /crm/quotes/kanban, /crm/tasks/kanban.

Dashboard widgets: open leads / open deals / tasks due today + open-leads-by-stage chart + recent activity list + (when email-marketing is enabled) CampaignPerformanceChart.

Settings cluster at /crm/settings:

Pipelines, Pipeline Stages, Pipeline Stage Probabilities, Lead Statuses, Lead Sources, Labels, Tax Rates, Product Categories, Product Attributes.
Contact Types, Address Types, Organization Types, Industries, Timezones.
Field Groups + Fields (custom field definitions, including option lists and per-model scoping).
Roles (Spatie\Permission, with Owner/Admin protected from edit/delete).
Email Templates, SMS Templates, Chat Widgets.
CRM Teams (with Team Members relation manager).
General settings page (key/value via SettingService).
Integrations page (Xero connect/disconnect + sync toggles, ClickSend status).
Reminders page (per-user activity reminders).
Updates page (version check only; upgrades are run from the console).

RelationManagers: Notes, Tasks, Calls, Meetings, Files inline on Lead / Deal / Person / Organization / Customer edit pages (polymorphic via HasCrmActivities). Files RM also on Quote / Order / Invoice / Purchase Order / Delivery. Each new entry logs to the core CRM Activity table for the timeline feed. Email/SMS campaign view pages get a per-recipient RelationManager showing per-row send/open/click/unsubscribe state.

Per-resource actions:

Quote / Invoice / Purchase Order: Send (generates dompdf PDF, sends signed-portal mailable via the core's Mail\SendQuote / SendInvoice / SendPurchaseOrder) + Download PDF.
Quote / Invoice: Preview portal (jumps to /p/quotes/... or /p/invoices/...).
Quote: Convert to order. Order: Convert to invoice / delivery / purchase order.
Email Campaign: Send now, Preview (renders EmailCampaignMessage::renderPreview() in a modal), Schedule, Cancel.
SMS Campaign: Send now, Preview (rendered body + segment count via SmsCampaignMessage::renderPreview() / ::segmentCount()), Schedule, Cancel. Body Textarea on the form shows a live segment-count estimate via helperText.
Chat: Reply, Close conversation, Convert to lead (creates Person + Lead from visitor); thread view subscribes to echo:crm-chat.{external_id},.chat.message for realtime message refresh when Laravel Echo is configured.
Tasks: Mark complete bulk action; Task kanban drag-to-complete.

Custom fields

Models with the core's HasCrmFields trait (Lead, Deal, Quote, Order, Invoice, PurchaseOrder, Person, Organization, Task, Product) automatically get a "Custom fields" section in their Filament forms when Field rows are scoped to the model via FieldModel. The plugin's Concerns\HasCrmCustomFields trait handles:

Mapping Field::type (text / textarea / date / checkbox / select / select_multiple / radio / checkbox_multiple) to the right Filament component.
Loading FieldValue rows on edit.
Saving FieldValue rows on create / update via updateOrCreate.

Define fields via the Settings cluster (/crm/settings/fields).

Localization

All user-visible Resource strings (form/column labels, section headings, action labels) are routed through __('laravel-crm-filament::labels.…'). The plugin ships three locale files under resources/lang/:

Locale	Path
English (canonical)	`resources/lang/en/labels.php`
French (starter)	`resources/lang/fr/labels.php`
Spanish (starter)	`resources/lang/es/labels.php`

labels.php is grouped into namespaces: fields, contact, sales, money, campaign, chat, file, sections, actions, import, misc.

Overriding a translation

Publish the translation files into the host app:

php artisan vendor:publish --tag=laravel-crm-filament-translations

This copies the plugin's resources/lang/{locale}/labels.php into the host app's lang/vendor/laravel-crm-filament/{locale}/labels.php (Laravel's default vendor-translation location). Edit any key in the published file — Laravel will pick up the override automatically without touching the plugin source.

You can also add a brand-new locale by dropping a labels.php with the same structure as en/labels.php into lang/vendor/laravel-crm-filament/{your-locale}/. Make sure the structure mirrors en/labels.php exactly — any key the plugin asks for that's missing falls back to the English value via Laravel's translation fallback.

Switching the panel locale

The panel respects the application locale set by app()->setLocale($locale). To switch on a per-user basis, set the locale early in the request (e.g. in a middleware or User::booted()):

Auth::user() && app()->setLocale(Auth::user()->locale ?? config('app.locale'));

Migrating from the `/crm` Livewire UI

The Filament panel and the core CRM's Livewire UI both target the same database. Because the Filament panel now defaults to /crm (matching the Livewire UI's route prefix), the install command asks up front whether to append LARAVEL_CRM_USER_INTERFACE=false to .env — the Livewire UI's kill switch. Pick the path that matches your rollout:

Full cutover. Accept the install prompt so LARAVEL_CRM_USER_INTERFACE=false is written to .env. The Filament panel serves /crm; the Livewire UI stops mounting its routes. This is the simplest path once you're confident the Filament panel covers everything you need.
Side-by-side during transition. Decline the install prompt and change the published CrmPanelProvider's ->path('crm') to a distinct path (e.g. ->path('crm-next')). Both UIs then run against the same database until you're ready to flip the switch.

Regardless of which path you pick, the plugin reads and writes the same crm_* tables. It adds exactly one table of its own, crm_invoice_payments, which records the payment history behind the invoice Mark paid action; laravelcrm:filament-install publishes and runs that migration in both crm and inject mode. If you wire the plugin up by hand instead of running the installer, publish it yourself with php artisan vendor:publish --tag=crm-filament-migrations && php artisan migrate — without the table, Mark paid still updates the invoice totals but silently records no payment history. On subsequent upgrades php artisan laravelcrm:filament-update does the same thing for you, and records that it did — see Updating. Access control routes through the same HasCrmAccess trait and the same Spatie roles/permissions seeded by php artisan laravelcrm:permissions, so a user who can see the Livewire UI can see the Filament panel (subject to canAccessPanel()). All writes from either UI go through the same observers (Observers/), services (Services/), and audit listeners; encrypted columns continue to be transparently encrypted/decrypted via HasEncryptableFields.

Differences hosts should know about

Paths in this table assume the default /crm Filament mount with the Livewire UI kill switch enabled.

Behaviour	Livewire UI (before)	Filament panel
Routing key	mixed `id` / `external_id`	always `external_id` for entity resources, integer `id` for lookup tables that lack `external_id`
Branding source	`laravel-crm.settings` (org name + logo)	`LaravelCrmPlugin::brand()` / `brandLogo()` or fallback to the same settings
Custom fields	Livewire `HasCrmFields` partial	`Concerns\HasCrmCustomFields` trait via `static::crmCustomFieldsSection(...)`
Files	per-model uploads	unified `FilesRelationManager` + read-only `/crm/files` global view
Activities	per-entity timeline	per-entity timeline plus global `/crm/activities`
Calendar	none	`/crm/calendar` aggregating tasks/calls/meetings/lunches
Reminders	global config	per-user `/crm/settings/reminders`
Updates	`laravelcrm:update` artisan only	`/crm/settings/updates` reports installed vs latest published version and whether either database is behind its code; applying the update is still artisan-only, via `laravelcrm:filament-update` — see Updating
PDF templates	`/crm/settings/templates`	`/crm/templates`, with the preview and thumbnails served from the page rather than from routes
Invitation acceptance	`/crm/users/invitations/accept/{code}`	`/crm/invitations/accept/{code}` — core's route is behind `laravel-crm.user_interface`
Multi-tenancy	supported	not supported — see Multi-tenancy

Testing

./vendor/bin/pest --no-coverage

The Pest test suite covers routing, model binding, cluster wiring, RelationManager attachment, custom-fields trait integration, plugin module gating, branding setters, role protection, localization key parity, and structural assertions for every phase's resources/actions/widgets.

Static analysis and style run alongside it:

composer analyse    # PHPStan (larastan), level 4
composer test:lint  # Pint

SQLite caveat. The suite runs against in-memory SQLite, which stores decimal(15,3) as NUMERIC and ignores the precision — so a green run does not prove the string-versus-float behaviour that core's Quantity helper exists for. Fractional quantities are worth one manual round-trip against MySQL before tagging a release.

Contributing

Pull requests are welcome. Before opening a PR, please make sure the test suite and code style checks pass locally:

./vendor/bin/pest --no-coverage
./vendor/bin/pint

Support

Bug reports and feature requests: https://github.com/venturedrake/laravel-crm-filament/issues
Core CRM package (models, services, migrations): https://github.com/venturedrake/laravel-crm

License

MIT — same as the core CRM package.

venturedrake / laravel-crm-filament

Maintainers

Package info

Statistics

Security

README

Requirements

Installation

Branch A — standalone `/crm` panel

Branch B — inject into an existing panel

Scripting the install (CI / provisioning)

Updating

Registering the plugin

Feature catalog

v0.5 — Pipeline conversion actions + PDF download

v0.6 — CSV bulk imports

v0.7 — Standalone activity/file resources + polymorphic Files RM

v0.8 — Campaign send-now, per-recipient analytics, performance widgets

v0.9a — Customer resource + lookup resources

v0.9b — Lead/pipeline lookups + Teams + Updates page

v0.10 — Calendar, Task kanban, Reminders settings

v0.11 — Chat widget embed UI, portal preview, branded auth

v1.1 — core 2.4.0 parity

User invitations

Multi-tenancy (not supported)

Permissions

Support classes

What's in the panel

Custom fields

Localization

Overriding a translation

Switching the panel locale

Migrating from the `/crm` Livewire UI

Differences hosts should know about

Testing

Contributing

Support

License

venturedrake / laravel-crm-filament

Maintainers

Package info

Statistics

Security

README

Requirements

Installation

Branch A — standalone /crm panel

Branch B — inject into an existing panel

Scripting the install (CI / provisioning)

Updating

Registering the plugin

Feature catalog

v0.5 — Pipeline conversion actions + PDF download

v0.6 — CSV bulk imports

v0.7 — Standalone activity/file resources + polymorphic Files RM

v0.8 — Campaign send-now, per-recipient analytics, performance widgets

v0.9a — Customer resource + lookup resources

v0.9b — Lead/pipeline lookups + Teams + Updates page

v0.10 — Calendar, Task kanban, Reminders settings

v0.11 — Chat widget embed UI, portal preview, branded auth

v1.1 — core 2.4.0 parity

User invitations

Multi-tenancy (not supported)

Permissions

Support classes

What's in the panel

Custom fields

Localization

Overriding a translation

Switching the panel locale

Migrating from the /crm Livewire UI

Differences hosts should know about

Testing

Contributing

Support

License

Branch A — standalone `/crm` panel

Migrating from the `/crm` Livewire UI