[Settings]: General — Company Information

[nielsdrost7]

SMART Plan — Set default company name in General Settings

Specific

A TextInput field labelled "Company Name" in the General tab of the Company Settings page. Stores a plain string under the key company_name, scoped to the current company. The value is used as the display name in PDF headers (invoices, quotes).

Measurable

• The field appears in the General section of the Company Settings page
• Saving the form persists the value to the settings table with key company_name and company_id scope
• The value is read back correctly on page reload

Achievable

1. Create/extend Modules/Core/Filament/Company/Pages/CompanySettings.php (Filament page with tabs)
2. Add a TextInput::make('company_name')->label('Company Name') field to the General tab section
3. Add const COMPANY_NAME = 'company_name'; to Modules/Core/Models/Setting.php constants
4. Register the page in CompanyPanelProvider

Relevant

The company name is the primary branding element on all PDF documents sent to clients. Allowing per-company overrides means each tenant can maintain their own display name without touching system-level config.

Time-bound

Sprint 6.

---

Arrange · Act · Assert

// Modules/Core/Tests/Feature/CompanySettingsTest.php

#[Test]
public function it_saves_company_name_setting(): void
{
    /* Arrange */
    $page = Livewire::actingAs($this->user)
        ->test(\Modules\Core\Filament\Company\Pages\CompanySettings::class);

    /* Act */
    $page->set('data.company_name', 'Acme Corp')
         ->call('save');

    /* Assert */
    $page->assertSuccessful();
    $this->assertDatabaseHas('settings', [
        'company_id' => $this->company->id,
        'key'        => 'company_name',
        'value'      => 'Acme Corp',
    ]);
}

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• [Settings]: Company panel — assign Payment Methods #241
• [Settings]: Company panel — assign Users #243
• [Settings]: Company panel — assign Email Templates #239
• [Settings]: Company panel — assign Invoice Groups #240
• [Settings]: Company panel — manage Tax Rates #238

👤 Suggested Assignees

• nielsdrost7

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[nielsdrost7]

SMART Plan — Company panel — manage Company Information

Specific

Within the Company panel Settings → General tab, add text fields for company information: business name, address (street, city, state, postal code, country), phone, website, tax ID, and registration number. These fields are stored in the companies table (new columns) or in the settings table scoped to the company.

Measurable

• All information fields are editable in CompanySettings.
• Data persists when saved.
• Fields appear on company dashboards, invoice headers, and company profile pages.
• Success message confirms the information was updated.

Achievable

1. Add columns to the companies table (or settings rows): business_name, address_line_1, address_line_2, city, state, postal_code, country, phone, website, tax_id, registration_number.
2. Add text/textarea fields in CompanySettings form.
3. Update invoice/quote templates to display this information.

Relevant

Professional invoices require company details for legal/regulatory compliance. This lets each company maintain their branding information.

Time-bound

Sprint 6.

[nielsdrost7]

Partial correction: the unmerged branch settings-cluster-2026-07-19 already has a "Company Name" text field (Setting::KEY_COMPANY_NAME) in the General tab of CompanySettings.php. Address, phone, website, and tax-ID fields described above are genuinely not implemented there — only the name field overlaps. Worth checking that branch before adding a duplicate name field.

[KhawarMehfooz]

Already implemented and merged via PR #686