Guides

What teams add to Weblabor Base, what they change, and where the rest is documented.

What a person sees after signing in, how a team is created, entered, configured, left and closed.

How a person is added to a team by email, phone or username, what happens when they have no account yet, and how roles are changed from the list.

How to pack a team's data into a file from the team settings screen, and how to bring that file into another team.

The shared file library a team gets, the storage quota you set on its plan, the permission that opens both screens, and where the team logo now lives.

The config keys and environment variables the team layer adds, with what each one changes.

How plans, add-ons, limits and cards attach to the team, who can manage them, and what a team without a plan can do.

The two screens teams add to the admin panel, what an administrator can change from them, and how billing shows up per team.

The owner role, the default role, the roles a team writes for itself, and what each permission lets a member do.

How a request knows which team it is in, how the permission guard is chosen, and what to do in a job, a command or a Livewire component.

The resource base class that keeps a Laravel Front CRUD inside the team, and how to register its route and permissions.