Ability to change naming

[dominikfomicz]

For example instead of /companies/1 we could have a like teams or ogranization - would be helpful :)

[pixelastronauts]

On another note; Renaming the entire system to 'filament-teams' would be a strategic move, broadening its appeal for both professional and personal applications. Currently, incorporating 'companies' in an application geared towards consumers seems out of place. However, the term 'teams' fits seamlessly in contexts oriented towards both business and personal use.

[andrewdwallo]

I understand your perspective on renaming the package to filament-teams. However, the choice of filament-companies is intentional, aligning with the package's focus on managing separate business entities, each representing an individual company. This approach caters to businesses operating multiple entities, emphasizing the broader organizational context.

Additionally, within this company-focused structure, the package allows for the inclusion of teams as a subset within a company tenant, akin to departments within a company. This ensures that the package addresses company-level management while also providing the flexibility to manage team-level dynamics.

Furthermore, this approach of using companies as separate tenants is a common practice in the industry. Popular web applications and software like Wave Accounting, QuickBooks, Xero, FreshBooks, Zoho Books, Trello, Asana, SAP Business One, and Oracle NetSuite all utilize a similar model. Even Akaunting, which is made with Laravel, utilizes a similar model. These platforms allow users to manage different business entities as distinct tenants, supporting the rationale behind filament-companies. As the sole developer of this package, my goal is to create a tool that is versatile and reflective of real organizational structures.

So, in short, I completely disagree, and neither the package nor the namespaces will be changed. I appreciate your opinion though. You are fully welcome to fork the repository and change this yourself.

[andrewdwallo]

@dominikfomicz Just a note here. You can definitely do this just by changing the path used to "team" in the Company panel stub. Then you can also change the wording of "Company"/"companies" inside of the language file and you should be good to go.

[sairiz]

I am doing this. So far so good. Most importantly this plugin is awesome. Thanks.

[mmoollllee]

I'm trying to add this plugin to an existing project:
Currently I have tenancy for "projects" instead of "companies".
Now if I understand correctly, to use this plugin, I'd have to rename my current Project Model to Company?

Altough there'd be ways to match it, and change the nameing in the views, urls,... Code would get hard to read and understand.
Why not name the Plugin's Model to "Tenant" instead of "Company"? This would make usage for the plugin more flexible.

I hope I'm not missing something and my proposal is understandable.