Usuário do parceiro

Anchor screen for the detail dictionary. Does not appear in the menu. — this is the role of the "Partner user" screen within the platform.

Each link carries its own switches: view tickets, view customers, view finance, approve quotes and view commission. This lets you calibrate the portal person by person — the partner's owner can see finance and commission, while operations staff see only tickets. The Active field controls the link without deleting it, and the Contact name and ERP code help match the user to the external record when there is an integration.

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.

Links a person from the partner to a portal user. It is through this link that they see only their own partner's data — removing the row cuts off access without deleting the user.

When someone from the partner logs in, the Partner portal finds out "who you are and which partner you belong to" precisely through this user–partner link — it decides which portfolio, which pipeline and which commission appear, and the link's permissions decide which blocks the user sees. That is why the normal maintenance path is the Users tab inside the partner record: there the link is born in the right context, with no risk of attaching the person to the wrong partner.

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.

"Where do I see partner users?" — whenever that question comes up, this is the screen that answers it.

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?".