Scenarios

Each member link keeps more than the name: the role defines the person's function within that team (the same person can have different roles in different teams); start and end delimit the link's validity — ending it by date preserves the team's history, deleting the link erases the memory; and the "development pair" (mentor) records who follows that member's development, which appears in the pairs view of the Team calendar.

Here you see and fix loose child records, one by one. In day-to-day work, however, the right thing is to create and edit them inside the parent record's form: that is where the business rules run (recalculated totals, validations, numbering, history). Editing directly here is useful for auditing and for correcting a specific case — but it can leave the parent record with an outdated total, and that raises no error on screen.

The team composition feeds the distribution of demands and the team's capacity. Removing someone from here does not delete the demands that are already theirs — reassign them first, otherwise they stay with someone in charge who no longer belongs to the team.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

On the Members tab of the Teams record (Operations ▸ Teams ▸ open the team). This entry exists to give names and help to the detail fields — the day-to-day work of putting teams together and taking them apart happens inside the team form. When removing someone, prefer ending the validity (End field) and unchecking Active over deleting the link: the historical numbers per team remain explainable when the team's past stays recorded.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".