Teams in the admin panel

The admin panel is the base's, at /admin, for accounts with the global admin role; see The admin panel on the base's site. The team layer adds two resources to it and puts the team on the billing screens. This guide covers those.

Teams

/admin/teams lists every team in the product: name, description, owner, dates. From it an administrator:

• Creates a team for a customer, naming the owner. The team is born the same way as one created from the switcher: the owner becomes its first member, the roles are created, the owner role is assigned. Use it when your product signs customers up by hand.
• Edits the name and the description.
• Sees the members on the detail page.
• Deletes a team, which soft deletes it, and restores one that was closed. A restored team comes back with its members, roles and subscription.

The owner field is set at creation and cannot be changed afterwards: the kit has no ownership transfer.

The team's add-ons

When add-ons are on, the team's edit form ends with the Add-ons panel: one switch per add-on that carries a capability, showing what the team has. Switching one on grants the capability to the team for free; switching it off withdraws that grant. An add-on the team bought, or that its plan includes, shows as on and cannot be switched off from here, because the grant is not the administrator's to remove.

The list can be filtered by plan, so an administrator finds every team on a given plan.

Fields of your own on a team

The teams list has a Custom fields button in the bar above the table, the same one the users list has. From it you add fields the team form does not ask for yet: a tax id, an account manager, a contract date, a value picked from a list, an image. From then on they appear in every team's form, after the team's own fields, and each one can be shown as a read-only column in the list. None of them is required.

Anyone who can create or edit a team can change that list, with no new permission. Adding, ordering, changing and deleting the fields works the same way everywhere in the panel, and is written once in Add custom fields on the base's site.

Three things are worth knowing on a team in particular:

• These are not the team's extra fields. The team writes those itself, from its settings screen, and never sees the fields you add here. The two lists are separate: the same name can live in both without either touching the other.
• An image you upload here is stored in your own library and counts against your space, not the team's. You find it in a folder named Teams, with one subfolder per team. If your account has no library yet the team is saved and the image is dropped without a message, so open your files once before you use an image field.
• Closing a team deletes those images for good. A closed team can be restored with its members, roles and plan, but a picture stored in one of these fields is not restored with it: the field is left pointing at a picture that no longer exists.

Team members

/admin/user_teams lists the memberships: which person is in which team, and since when. It is the raw table behind the members screen of each team, for when an administrator has to see or fix a membership without entering the team. Deleting a row removes the person from that team and sends them the same notification as being removed by the owner.

Global roles and team roles

/admin/roles is the base's roles resource and shows the global roles only: the ones on the web guard, with team_id at 0. The roles a team writes for itself live at /team/roles inside that team and never appear here. See Team roles and permissions.

Plans and add-ons

The plans and add-ons resources are the base's. In the form of each one, the context field says who it is sold to: users, teams or both. As shipped only the team adapter is registered, so a plan for users would be offered to nobody; keep the context on teams unless you turned BILLING_USER_ENABLED on. See Team plans and billing.

The add-on form's capability field lists the methods of app/Classes/TeamPlanFeatures.php when the context is teams. A capability the class does not declare is shown with a warning: the add-on can be sold, but switches nothing on until the method exists.

Users

The base's users resource is unchanged. A person's teams do not show on it: open the memberships resource, or the team, for that. Impersonating a person from here lands you where they would land, the switcher, with their teams.