diff --git a/CLAUDE.md b/CLAUDE.md index c407c974..da87062d 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -428,7 +428,7 @@ LOGIN_RATE_LIMIT_GLOBAL_MAX="100" # Max failed login attempts instance-wide « Aide » (`/help`, from the account menu) ships with the app, in French, English and European Portuguese. The articles are Markdown files in `app/features/help/content/{fr,en,pt-PT}/`, one per task, with a frontmatter block: `slug`, `title`, `summary`, `module`, `permission`, `keywords`, `related`, `order`. `permission` is the name of the `Permission` member the feature needs, several comma-separated when the feature opens to any of them, or `none`. `GroupLeader` among them opens the article to a group's overseer and assistant too, who hold no right for their group (`helpReaderFor` reads it from the account's record). A reader without it never sees the article, nor its search hits or links, and no permission is ever changed to show help. -A « ? » goes in the header's `help` slot (`} />`, or `SettingsHeader`), which puts it at the far right of the top bar and at the end of the title's row on a phone. Its page and every layout with a loader above it export `skipRevalidationForHelpPanel as shouldRevalidate` from `~/features/help`, so opening the panel fetches the article only. A page that writes its own `shouldRevalidate` starts it with `if (onlyHelpPanelChanged(args)) return false`. The publisher record draws its own title row (`RecordHeader`), so it takes the « ? » twice: in `PageTopbar`'s `help` and in `RecordHeader`'s, which shows on a phone only. A page serving several rights may put a component of its own named `…Help` in the slot, choosing the article of the first right the reader holds (« Gérer le tableau »). The territory editor and « Créer en lot » do the same as the record: `TerritoryEditor` and `TerritoryBatchCreator` take a `help` for their column's title row. +A « ? » goes in the header's `help` slot (`} />`, or `SettingsHeader`), which puts it at the far right of the top bar and at the end of the title's row on a phone. Its page and every layout with a loader above it export `skipRevalidationForHelpPanel as shouldRevalidate` from `~/features/help`, so opening the panel fetches the article only. A page that writes its own `shouldRevalidate` starts it with `if (onlyHelpPanelChanged(args)) return false`. The publisher record draws its own title row (`RecordHeader`), so it takes the « ? » twice: in `PageTopbar`'s `help` and in `RecordHeader`'s, which shows on a phone only. A page serving several rights may put a component of its own named `…Help` in the slot, choosing the article of the first right the reader holds (« Gérer le tableau »). The organigram's screens take it for their top bar and their heading (`OrgHeading`, phone only). The territory editor and « Créer en lot » do the same as the record: `TerritoryEditor` and `TerritoryBatchCreator` take a `help` for their column's title row. `app/features/help/entry-points.test.ts` is the authoritative wiring: it scans the app source for every `` and fails unless each one is pinned there and ships in every language. Keep this table in step with it. @@ -450,6 +450,11 @@ A « ? » goes in the header's `help` slot (` [{ title: m.org_meta_title() }] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + export function loader({ request, context }: Route.LoaderArgs) { const permissions = context.get(permissionsContext) if (!permissions.has(Permission.CanViewRoles) && !permissions.has(Permission.CanManageRoles)) { @@ -45,5 +48,5 @@ export async function action({ request, context }: Route.ActionArgs) { } export default function OrganigramRoute({ loaderData }: Route.ComponentProps) { - return + return } /> } diff --git a/app/features/congregation/routes/roles/role-list.tsx b/app/features/congregation/routes/roles/role-list.tsx index ebb261ae..91641e74 100644 --- a/app/features/congregation/routes/roles/role-list.tsx +++ b/app/features/congregation/routes/roles/role-list.tsx @@ -4,6 +4,7 @@ import { type BuiltInFilterKey, toggleSchema } from '~/features/congregation/sch import { loadTeamsPage, TEAMS_VIEWS } from '~/features/congregation/server/teams-page.queries' import type { TeamToggleResult } from '~/features/congregation/ui/TeamCell' import { TeamsScreen } from '~/features/congregation/ui/TeamsScreen' +import { HelpEntryButton } from '~/features/help' import * as m from '~/i18n/paraglide/messages' import { currentAccountContext, permissionsContext, withScopeFromContext } from '~/shared/auth/route-context.server' import { holderOfMember } from '~/shared/domain/role-assignments.server' @@ -16,6 +17,8 @@ import type { Route } from './+types/role-list' export const meta: Route.MetaFunction = () => [{ title: m.teams_meta_title() }] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + export function loader({ request, context }: Route.LoaderArgs) { const permissions = context.get(permissionsContext) if (!permissions.has(Permission.CanViewRoles) && !permissions.has(Permission.CanManageRoles)) throw redirect('/') @@ -71,5 +74,5 @@ export async function action({ request, context }: Route.ActionArgs) { } export default function TeamsRoute({ loaderData }: Route.ComponentProps) { - return + return } /> } diff --git a/app/features/congregation/ui/OrgHeading.tsx b/app/features/congregation/ui/OrgHeading.tsx index cd4eb888..4a3e21ea 100644 --- a/app/features/congregation/ui/OrgHeading.tsx +++ b/app/features/congregation/ui/OrgHeading.tsx @@ -1,4 +1,5 @@ import { Plus } from 'lucide-react' +import type { ReactNode } from 'react' import { Link } from 'react-router' import * as m from '~/i18n/paraglide/messages' import { Button } from '~/shared/ui/button' @@ -8,13 +9,15 @@ interface OrgHeadingProps { canCreate: boolean /** « Nouveau rôle »: a link to the dialog, or what opens it here. */ newRole: { to: string } | { onClick: () => void } + /** The page's « ? », beside the title on a phone; the top bar carries it from md. */ + help?: ReactNode } /** * The organigram's title and subtitle. On a phone, « Nouveau rôle » is a « + » beside the title, as the shell's other * phone headers carry their action, instead of a full-width button under it; from md up it stays in the top bar. */ -export function OrgHeading({ canCreate, newRole }: OrgHeadingProps) { +export function OrgHeading({ canCreate, newRole, help }: OrgHeadingProps) { return (
@@ -33,6 +36,7 @@ export function OrgHeading({ canCreate, newRole }: OrgHeadingProps) {
) } diff --git a/app/features/congregation/ui/OrganigramScreen.tsx b/app/features/congregation/ui/OrganigramScreen.tsx index 9e7323a6..f2d00b64 100644 --- a/app/features/congregation/ui/OrganigramScreen.tsx +++ b/app/features/congregation/ui/OrganigramScreen.tsx @@ -1,5 +1,5 @@ import { Eye, Network, Plus } from 'lucide-react' -import { useCallback, useEffect, useRef, useState } from 'react' +import { type ReactNode, useCallback, useEffect, useRef, useState } from 'react' import { Link, useSearchParams } from 'react-router' import type { OrganigramPage } from '~/features/congregation/model/organigram-page.type' import { AdoptCommitteeDialog } from '~/features/congregation/ui/AdoptCommitteeDialog' @@ -30,7 +30,14 @@ interface NewRole { parentId: number | null } -export function OrganigramScreen({ page }: { page: OrganigramPage & { canManage: boolean } }) { +export function OrganigramScreen({ + page, + help, +}: { + page: OrganigramPage & { canManage: boolean } + /** The page's « ? »: in the top bar from md, beside the title on a phone. */ + help?: ReactNode +}) { const { tree, panel, boardDocumentId, manage, canManage } = page const [params, setParams] = useSearchParams() const docked = useMediaQuery(DOCKED) === true @@ -100,6 +107,7 @@ export function OrganigramScreen({ page }: { page: OrganigramPage & { canManage: {boardDocumentId != null && ( @@ -119,7 +127,7 @@ export function OrganigramScreen({ page }: { page: OrganigramPage & { canManage: } > - + diff --git a/app/features/congregation/ui/TeamsScreen.tsx b/app/features/congregation/ui/TeamsScreen.tsx index ba83e0df..59bb187b 100644 --- a/app/features/congregation/ui/TeamsScreen.tsx +++ b/app/features/congregation/ui/TeamsScreen.tsx @@ -1,5 +1,5 @@ import { ChevronDown, CircleAlert, CircleCheck, Plus } from 'lucide-react' -import { useState } from 'react' +import { type ReactNode, useState } from 'react' import { Link, useSearchParams } from 'react-router' import type { MatrixGroup, MatrixMember } from '~/features/congregation/model/role-matrix.type' import type { BuiltInFilterKey } from '~/features/congregation/schemas/role.schema' @@ -107,6 +107,7 @@ export function TeamsScreen({ views, view, canManage, + help, }: { groups: MatrixGroup[] members: MatrixMember[] @@ -114,6 +115,8 @@ export function TeamsScreen({ views: Record view: BuiltInFilterKey canManage: boolean + /** The page's « ? »: in the top bar from md, beside the title on a phone. */ + help?: ReactNode }) { const [last, setLast] = useState(null) const body = { groups, members, counts, canManage, onResult: setLast } @@ -123,6 +126,7 @@ export function TeamsScreen({ @@ -134,7 +138,7 @@ export function TeamsScreen({ ) } > - + diff --git a/app/features/help/content/captures.json b/app/features/help/content/captures.json index 21396e8f..e1e6b2b5 100644 --- a/app/features/help/content/captures.json +++ b/app/features/help/content/captures.json @@ -120,6 +120,11 @@ "height": 71, "captured": "2026-11-17" }, + "organigram-role-panel": { + "width": 398, + "height": 633, + "captured": "2026-11-18" + }, "pioneers-summary": { "width": 644, "height": 278, @@ -140,11 +145,36 @@ "height": 210, "captured": "2026-11-18" }, + "settings-account-roles": { + "width": 599, + "height": 435, + "captured": "2026-11-18" + }, + "settings-account-security": { + "width": 596, + "height": 397, + "captured": "2026-11-18" + }, + "settings-audit-toolbar": { + "width": 600, + "height": 104, + "captured": "2026-11-18" + }, "settings-bano": { "width": 509, "height": 208, "captured": "2026-11-17" }, + "settings-data-export": { + "width": 596, + "height": 385, + "captured": "2026-11-18" + }, + "settings-new-user": { + "width": 446, + "height": 338, + "captured": "2026-11-18" + }, "settings-phone-switch": { "width": 473, "height": 81, @@ -302,6 +332,11 @@ "height": 71, "captured": "2026-11-17" }, + "organigram-role-panel": { + "width": 398, + "height": 633, + "captured": "2026-11-18" + }, "pioneers-summary": { "width": 644, "height": 278, @@ -322,11 +357,36 @@ "height": 210, "captured": "2026-11-18" }, + "settings-account-roles": { + "width": 599, + "height": 415, + "captured": "2026-11-18" + }, + "settings-account-security": { + "width": 596, + "height": 374, + "captured": "2026-11-18" + }, + "settings-audit-toolbar": { + "width": 600, + "height": 104, + "captured": "2026-11-18" + }, "settings-bano": { "width": 509, "height": 208, "captured": "2026-11-17" }, + "settings-data-export": { + "width": 596, + "height": 385, + "captured": "2026-11-18" + }, + "settings-new-user": { + "width": 446, + "height": 318, + "captured": "2026-11-18" + }, "settings-phone-switch": { "width": 473, "height": 81, @@ -484,6 +544,11 @@ "height": 71, "captured": "2026-11-18" }, + "organigram-role-panel": { + "width": 398, + "height": 633, + "captured": "2026-11-18" + }, "pioneers-summary": { "width": 644, "height": 278, @@ -504,11 +569,36 @@ "height": 210, "captured": "2026-11-18" }, + "settings-account-roles": { + "width": 599, + "height": 435, + "captured": "2026-11-18" + }, + "settings-account-security": { + "width": 596, + "height": 397, + "captured": "2026-11-18" + }, + "settings-audit-toolbar": { + "width": 600, + "height": 104, + "captured": "2026-11-18" + }, "settings-bano": { "width": 509, "height": 208, "captured": "2026-11-18" }, + "settings-data-export": { + "width": 596, + "height": 405, + "captured": "2026-11-18" + }, + "settings-new-user": { + "width": 446, + "height": 338, + "captured": "2026-11-18" + }, "settings-phone-switch": { "width": 473, "height": 81, diff --git a/app/features/help/content/en/audit-log.md b/app/features/help/content/en/audit-log.md new file mode 100644 index 00000000..9f85060e --- /dev/null +++ b/app/features/help/content/en/audit-log.md @@ -0,0 +1,24 @@ +--- + +slug: audit-log +title: How do I find who did what in the audit log? +summary: The congregation’s sensitive actions, by person, action and period. +module: settings +permission: CanConfigureCongregation +keywords: audit log, audit, history, actions, sign-ins, rights, deletions, who did, traceability, security +related: congregation-data +order: 5 +--- + +The audit log keeps the sensitive actions made in the congregation: sign-ins, rights, data, deletions. Each line says when, who, which action and on what. + +## Find an action + +1. In **Settings › Audit log**, choose the **Period**: the last 7 or 30 days, the last 3 or 12 months, **All time**, or **Chosen dates**. +2. For a person, type their name in the search. For a kind of action, choose it in **Action**. + + ![The audit log’s bar: the search, the action, the period and the number of actions](capture:settings-audit-toolbar) + +3. Click a line to see its detail beside the list. + +Actions made by the app itself, such as automatic tasks, show under **The app**. diff --git a/app/features/help/content/en/congregation-data.md b/app/features/help/content/en/congregation-data.md new file mode 100644 index 00000000..dc80710f --- /dev/null +++ b/app/features/help/content/en/congregation-data.md @@ -0,0 +1,32 @@ +--- + +slug: congregation-data +title: How do I export or import the congregation’s data? +summary: A .unitae archive of all the data, to keep it or take it elsewhere. +module: settings +permission: CanExportCongregationData, CanImportCongregationData +keywords: export, import, archive, backup, data, unitae, transfer, migration, audit log +related: audit-log +order: 4 +--- + +**Settings › Import and export** makes a `.unitae` archive of all the congregation’s data, and takes in an archive made by Unitae, for instance to move from one instance to another. + +## Export + +1. In **Settings › Import and export**, choose what the archive holds on top of the data: **Include the information board’s documents (PDF)** and **Include the audit log**. Both can make it much heavier. +2. Click **Start the export**. The archive is prepared in the background. + + ![The Export section: the board’s documents, the audit log and Start the export](capture:settings-data-export) + +3. When it is ready, click **Download archive**. + +Earlier archives stay under **Previous exports**, to download them again. + +## Import + +1. In **Import**, drop the `.unitae` archive, then click **Read the archive**. +2. The app shows what it holds: the data to import, the items that already exist, updated or skipped, and the warnings. +3. If everything suits you, click **Start the import**. + +If the import fails, the congregation’s data is not changed. Importing takes being an administrator. diff --git a/app/features/help/content/en/give-rights.md b/app/features/help/content/en/give-rights.md new file mode 100644 index 00000000..cfa4cecf --- /dev/null +++ b/app/features/help/content/en/give-rights.md @@ -0,0 +1,43 @@ +--- + +slug: give-rights +title: How do I give someone a right? +summary: Rights go through roles: give a role, or change what a role allows. +module: settings +permission: CanManageUsers, CanConfigurePermissions +keywords: right, rights, permission, permissions, role, roles, access, give, remove, administrator, account +related: invite-user, organigram, reset-two-step +order: 3 +--- + +A right is never given straight to a person: it goes through a role. A person has the rights of all their roles. + +There are three kinds of roles: + +- **Record roles** follow what each person’s record says: elder, ministerial servant, pioneer… They change when the record changes. +- **Congregation roles** are created by the congregation in the organization chart, and given from the chart or the account. +- **Administrator** can do anything, including giving this role. + +## Give someone a role + +1. In **Settings › Users**, open their account. +2. In **Roles**, tick the role to give them, or untick it to take it away, then click **Save**. + + ![The top of an account’s Roles section: the roles to tick, ticked for those they already have](capture:settings-account-roles) + +A role held by one person only (a personal role of the organization chart) is given from the chart, not here. + +## Change what a role allows + +1. In **Settings › Roles and permissions**, choose the role. +2. Tick the rights it gives, category by category. Some rights need another one: the line says so. +3. Click **Save**. + +The change applies to everyone who has that role. + +## Good to know + +- You can only give the rights you hold yourself; otherwise an administrator does it. +- Only an administrator changes what a record role allows. +- The administrator cannot be restricted: to take a right away from an administrator, remove that role and give them a congregation role. +- The app refuses to leave the congregation without an administrator. diff --git a/app/features/help/content/en/invite-user.md b/app/features/help/content/en/invite-user.md new file mode 100644 index 00000000..d9a0e780 --- /dev/null +++ b/app/features/help/content/en/invite-user.md @@ -0,0 +1,38 @@ +--- + +slug: invite-user +title: How do I invite someone to sign in? +summary: Create their account, from their record or from Settings › Users. +module: settings +permission: CanManageUsers, CanManagePublishers +keywords: invite, invitation, account, user, login, sign in, email, password, new user, resend +related: give-rights, reset-two-step +order: 2 +--- + +To sign in, a person needs an account. They receive an email to choose their password, then sign in with their address. + +## For a publisher + +1. Open their record in **Publishers**. +2. In the **…** menu, under **Login**, choose **Create a login…**. +3. Enter their email address, then click **Create login**. + +The account is linked to their record: their name comes from it, and they get the roles of their record. + +## For someone without a record + +1. In **Settings › Users**, click **New user**. +2. Fill in their **First name**, **Last name** and **Sign-in email**. + + ![The New user window: first name, last name and sign-in email](capture:settings-new-user) + +3. Click **Create and send the invitation**. + +Their roles are then given on their page. + +## Follow the invitation + +Until the person has chosen their password, their account shows **Invitation sent** in the list of users. If the email got lost, open their account and click **Resend the invitation…**: the new link replaces the earlier ones. + +An address can be used by one account only. diff --git a/app/features/help/content/en/organigram.md b/app/features/help/content/en/organigram.md new file mode 100644 index 00000000..e6dda38d --- /dev/null +++ b/app/features/help/content/en/organigram.md @@ -0,0 +1,35 @@ +--- + +slug: organigram +title: How do I keep the congregation’s organization chart? +summary: Create the roles, name people to them and form the teams. +module: organigram +permission: CanManageRoles +keywords: organization chart, organigram, role, roles, team, teams, overseer, assistant, member, holder, committee, name, replace, board +related: give-rights +order: 1 +--- + +The organization chart shows the congregation’s responsibilities. Each box is a role: a **team**, with overseers, assistants and members, or a **personal role**, held by one person. It starts with the elders and the ministerial servants, kept up to date from the records. + +## Create a role + +1. In the sidebar, open **Organization chart**, then click **New role**. +2. Give it a **Name** and, if you like, a **Description**. +3. Choose its **Place**: which role it sits under, or **Outside the organigram** for a role with no box on the chart or the board. +4. Click **Create the role**. + +## Name people + +1. Click the role’s box: its panel opens. +2. Search for the person. In a team, choose **In charge** or **Assistant**. Then click **Name**. In a personal role that is already held, the button becomes **Replace**: the holder changes, their assistants stay. + + ![A team’s panel: its people in charge, the search to name someone, and its members](capture:organigram-role-panel) + +A role can be given to a publisher who has no account. A team’s members are added in the **Teams** tab: a ticked box adds the person, and it is saved straight away. + +## Edit or move a role + +In the role’s panel, **Edit** changes its name, its type, its description and the **Note on the board**, printed under the role in the board’s organization chart. At the bottom of the panel, **Place in the organigram** puts it under another role, moves it up or down, or takes it off the chart. **Delete the role** is possible only once the roles under it have been moved. + +What each role allows in the app is set in **Settings › Roles and permissions**. diff --git a/app/features/help/content/en/reset-two-step.md b/app/features/help/content/en/reset-two-step.md new file mode 100644 index 00000000..fde53daf --- /dev/null +++ b/app/features/help/content/en/reset-two-step.md @@ -0,0 +1,36 @@ +--- + +slug: reset-two-step +title: How do I help someone who can no longer sign in? +summary: Resend the invitation, send a password link, or reset two-step verification. +module: settings +permission: CanManageUsers +keywords: sign in, locked out, forgotten password, two-step verification, two-factor, code, lost phone, reset, unlock, invitation, link +related: invite-user, two-step-verification +order: 6 +--- + +When someone can no longer sign in, the **Security** section of their account offers what helps. Open their account in **Settings › Users**. + +![An account’s Security section: password, two-step verification and their data](capture:settings-account-security) + +## They lost their phone + +If two-step verification is on and they can no longer read their codes: + +1. In **Security**, on the **Two-step verification** line, click **Reset…**. +2. Confirm with **Reset**. + +They then sign in with their password alone, and can turn it on again from **My account**. + +## They forgot their password + +On the **Password** line, click **Send a link…**, then **Send the link**. They receive a link to choose a new password; their devices are signed out at once. + +They can also do it themselves from the sign-in screen. + +## They never got the invitation + +Until they have chosen their password, the section offers **Resend the invitation…**. The new link replaces the earlier ones. + +An administrator’s account is managed by an administrator only. diff --git a/app/features/help/content/fr/audit-log.md b/app/features/help/content/fr/audit-log.md new file mode 100644 index 00000000..6fdecf8f --- /dev/null +++ b/app/features/help/content/fr/audit-log.md @@ -0,0 +1,24 @@ +--- + +slug: audit-log +title: Comment retrouver qui a fait quoi dans le journal d’audit ? +summary: Les actions sensibles de l’assemblée, par personne, action et période. +module: settings +permission: CanConfigureCongregation +keywords: journal d’audit, audit, historique, actions, connexions, droits, suppressions, qui a fait, traçabilité, sécurité +related: congregation-data +order: 5 +--- + +Le journal d’audit garde les actions sensibles faites dans l’assemblée : connexions, droits, données, suppressions. Chaque ligne dit quand, qui, quelle action et sur quel objet. + +## Chercher une action + +1. Dans **Réglages › Journal d’audit**, choisissez la **Période** : les 7 ou 30 derniers jours, les 3 ou 12 derniers mois, **Depuis toujours**, ou **Dates choisies**. +2. Pour une personne, tapez son nom dans la recherche. Pour un type d’action, choisissez-le dans **Action**. + + ![La barre du journal d’audit : la recherche, l’action, la période et le nombre d’actions](capture:settings-audit-toolbar) + +3. Cliquez sur une ligne pour voir son détail à côté de la liste. + +Les actions faites par l’application elle-même, comme les tâches automatiques, apparaissent au nom de **L’application**. diff --git a/app/features/help/content/fr/congregation-data.md b/app/features/help/content/fr/congregation-data.md new file mode 100644 index 00000000..2d08632a --- /dev/null +++ b/app/features/help/content/fr/congregation-data.md @@ -0,0 +1,32 @@ +--- + +slug: congregation-data +title: Comment exporter ou importer les données de l’assemblée ? +summary: Une archive .unitae de toutes les données, pour la garder ou la reprendre ailleurs. +module: settings +permission: CanExportCongregationData, CanImportCongregationData +keywords: export, exporter, import, importer, archive, sauvegarde, données, unitae, transfert, migration, journal d’audit +related: audit-log +order: 4 +--- + +**Réglages › Import et export** fait une archive `.unitae` de toutes les données de l’assemblée, et reprend une archive faite par Unitae, par exemple pour passer d’une instance à une autre. + +## Exporter + +1. Dans **Réglages › Import et export**, choisissez ce que l’archive contient en plus des données : **Inclure les documents du tableau d’affichage (PDF)** et **Inclure le journal d’audit**. Les deux peuvent beaucoup l’alourdir. +2. Cliquez sur **Lancer l’export**. L’archive se prépare en arrière-plan. + + ![La section Exporter : les documents du tableau, le journal d’audit et Lancer l’export](capture:settings-data-export) + +3. Quand elle est prête, cliquez sur **Télécharger l’archive**. + +Les archives précédentes restent dans **Exports précédents**, pour les télécharger de nouveau. + +## Importer + +1. Dans **Importer**, déposez l’archive `.unitae`, puis cliquez sur **Lire l’archive**. +2. L’application montre ce qu’elle contient : les données à importer, les éléments qui existent déjà, mis à jour ou ignorés, et les avertissements. +3. Si tout vous convient, cliquez sur **Lancer l’import**. + +Si l’import échoue, les données de l’assemblée ne sont pas modifiées. Importer demande d’être administrateur. diff --git a/app/features/help/content/fr/give-rights.md b/app/features/help/content/fr/give-rights.md new file mode 100644 index 00000000..992180ea --- /dev/null +++ b/app/features/help/content/fr/give-rights.md @@ -0,0 +1,43 @@ +--- + +slug: give-rights +title: Comment donner un droit à quelqu’un ? +summary: Les droits passent par les rôles : donner un rôle, ou changer ce qu’un rôle permet. +module: settings +permission: CanManageUsers, CanConfigurePermissions +keywords: droit, droits, autorisation, autorisations, permission, rôle, rôles, accès, donner, retirer, administrateur, compte +related: invite-user, organigram, reset-two-step +order: 3 +--- + +Un droit ne se donne jamais directement à une personne : il passe par un rôle. Une personne a les droits de tous ses rôles. + +Il y a trois sortes de rôles : + +- **Les rôles de la fiche** suivent ce que dit la fiche de chacun : ancien, assistant ministériel, pionnier… Ils changent quand la fiche change. +- **Les rôles de l’assemblée** sont créés par l’assemblée dans l’organigramme, et donnés depuis l’organigramme ou le compte. +- **Administrateur** peut tout faire, y compris donner ce rôle. + +## Donner un rôle à quelqu’un + +1. Dans **Réglages › Utilisateurs**, ouvrez son compte. +2. Dans **Rôles**, cochez le rôle à lui donner, ou décochez-le pour le retirer, puis cliquez sur **Enregistrer**. + + ![Le début de la section Rôles d’un compte : les rôles à cocher, cochés pour ceux qu’il a déjà](capture:settings-account-roles) + +Un rôle d’une seule personne (un rôle personnel de l’organigramme) se donne depuis l’organigramme, pas ici. + +## Changer ce qu’un rôle permet + +1. Dans **Réglages › Rôles et autorisations**, choisissez le rôle. +2. Cochez les droits qu’il donne, catégorie par catégorie. Certains droits en demandent un autre : la ligne l’indique. +3. Cliquez sur **Enregistrer**. + +Le changement vaut pour toutes les personnes qui ont ce rôle. + +## Bon à savoir + +- Vous ne pouvez donner que les droits que vous avez vous-même ; sinon, un administrateur s’en charge. +- Seul un administrateur change ce que permet un rôle de la fiche. +- L’administrateur ne se restreint pas : pour retirer un droit à un administrateur, retirez-lui ce rôle et donnez-lui un rôle de l’assemblée. +- L’application refuse de laisser l’assemblée sans administrateur. diff --git a/app/features/help/content/fr/invite-user.md b/app/features/help/content/fr/invite-user.md new file mode 100644 index 00000000..ddc76b02 --- /dev/null +++ b/app/features/help/content/fr/invite-user.md @@ -0,0 +1,38 @@ +--- + +slug: invite-user +title: Comment inviter quelqu’un à se connecter ? +summary: Créer son compte, depuis sa fiche ou depuis Réglages › Utilisateurs. +module: settings +permission: CanManageUsers, CanManagePublishers +keywords: inviter, invitation, compte, utilisateur, identifiant, connexion, e-mail, mot de passe, nouvel utilisateur, renvoyer +related: give-rights, reset-two-step +order: 2 +--- + +Pour se connecter, une personne a besoin d’un compte. Elle reçoit un e-mail pour choisir son mot de passe, puis elle se connecte avec son adresse. + +## Pour un proclamateur + +1. Ouvrez sa fiche dans **Proclamateurs**. +2. Dans le menu **…**, sous **Connexion**, choisissez **Créer un identifiant…**. +3. Saisissez son adresse e-mail, puis cliquez sur **Créer l’identifiant**. + +Le compte est lié à sa fiche : son nom en vient, et les rôles de sa fiche lui sont donnés. + +## Pour quelqu’un sans fiche + +1. Dans **Réglages › Utilisateurs**, cliquez sur **Nouvel utilisateur**. +2. Renseignez son **Prénom**, son **Nom** et son **E-mail de connexion**. + + ![La fenêtre Nouvel utilisateur : prénom, nom et e-mail de connexion](capture:settings-new-user) + +3. Cliquez sur **Créer et envoyer l’invitation**. + +Ses rôles se donnent ensuite sur sa page. + +## Suivre l’invitation + +Tant que la personne n’a pas choisi son mot de passe, son compte indique **Invitation envoyée** dans la liste des utilisateurs. Si l’e-mail s’est perdu, ouvrez son compte et cliquez sur **Renvoyer l’invitation…** : le nouveau lien remplace les précédents. + +Une adresse ne sert qu’à un seul compte. diff --git a/app/features/help/content/fr/organigram.md b/app/features/help/content/fr/organigram.md new file mode 100644 index 00000000..d4bd8a2c --- /dev/null +++ b/app/features/help/content/fr/organigram.md @@ -0,0 +1,35 @@ +--- + +slug: organigram +title: Comment tenir l’organigramme de l’assemblée ? +summary: Créer les rôles, y nommer les personnes et former les équipes. +module: organigram +permission: CanManageRoles +keywords: organigramme, rôle, rôles, équipe, équipes, responsable, adjoint, membre, titulaire, comité, nommer, remplacer, tableau +related: give-rights +order: 1 +--- + +L’organigramme montre les responsabilités de l’assemblée. Chaque case est un rôle : une **équipe**, avec des responsables, des adjoints et des membres, ou un **rôle personnel**, tenu par une seule personne. Il commence par les anciens et les assistants ministériels, tenus à jour depuis les fiches. + +## Créer un rôle + +1. Dans la barre latérale, ouvrez **Organigramme**, puis cliquez sur **Nouveau rôle**. +2. Donnez-lui un **Nom** et, si vous voulez, une **Description**. +3. Choisissez sa **Place** : sous quel rôle il se range, ou **Hors organigramme** pour un rôle sans case dans l’arbre ni sur le tableau. +4. Cliquez sur **Créer le rôle**. + +## Nommer les personnes + +1. Cliquez sur la case du rôle : son panneau s’ouvre. +2. Cherchez la personne. Dans une équipe, choisissez **Responsable** ou **Adjoint**. Cliquez ensuite sur **Nommer**. Dans un rôle personnel déjà tenu, le bouton devient **Remplacer** : le titulaire change, ses adjoints restent. + + ![Le panneau d’une équipe : ses responsables, la recherche pour nommer quelqu’un, et ses membres](capture:organigram-role-panel) + +Un rôle peut être donné à un proclamateur qui n’a pas de compte. Les membres d’une équipe s’ajoutent dans l’onglet **Équipes** : une case cochée ajoute la personne, et c’est enregistré aussitôt. + +## Modifier ou déplacer un rôle + +Dans le panneau du rôle, **Modifier** change son nom, son type, sa description et la **Note sur le tableau**, imprimée sous le rôle dans l’organigramme du tableau d’affichage. En bas du panneau, **Place dans l’organigramme** le rattache sous un autre rôle, le monte ou le descend, ou le sort de l’organigramme. **Supprimer le rôle** n’est possible qu’une fois ses rôles rattachés déplacés. + +Ce que chaque rôle permet de faire dans l’application se règle dans **Réglages › Rôles et autorisations**. diff --git a/app/features/help/content/fr/reset-two-step.md b/app/features/help/content/fr/reset-two-step.md new file mode 100644 index 00000000..b367ec84 --- /dev/null +++ b/app/features/help/content/fr/reset-two-step.md @@ -0,0 +1,36 @@ +--- + +slug: reset-two-step +title: Comment aider quelqu’un qui ne peut plus se connecter ? +summary: Renvoyer l’invitation, envoyer un lien de mot de passe, ou réinitialiser la vérification en deux étapes. +module: settings +permission: CanManageUsers +keywords: connexion, bloqué, mot de passe oublié, vérification en deux étapes, double authentification, code, téléphone perdu, réinitialiser, débloquer, invitation, lien +related: invite-user, two-step-verification +order: 6 +--- + +Quand quelqu’un ne peut plus se connecter, la section **Sécurité** de son compte propose de quoi l’aider. Ouvrez son compte dans **Réglages › Utilisateurs**. + +![La section Sécurité d’un compte : mot de passe, vérification en deux étapes et ses données](capture:settings-account-security) + +## Il a perdu son téléphone + +Si la vérification en deux étapes est activée et qu’il ne peut plus lire ses codes : + +1. Dans **Sécurité**, à la ligne **Vérification en deux étapes**, cliquez sur **Réinitialiser…**. +2. Confirmez avec **Réinitialiser**. + +Il se connecte ensuite avec son seul mot de passe, et peut la réactiver depuis **Mon compte**. + +## Il a oublié son mot de passe + +À la ligne **Mot de passe**, cliquez sur **Envoyer un lien…**, puis sur **Envoyer le lien**. Il reçoit un lien pour choisir un nouveau mot de passe ; ses appareils sont déconnectés tout de suite. + +Il peut aussi le faire lui-même depuis l’écran de connexion. + +## Il n’a jamais reçu l’invitation + +Tant qu’il n’a pas choisi son mot de passe, la section propose **Renvoyer l’invitation…**. Le nouveau lien remplace les précédents. + +Le compte d’un administrateur ne se gère que par un administrateur. diff --git a/app/features/help/content/pt-PT/audit-log.md b/app/features/help/content/pt-PT/audit-log.md new file mode 100644 index 00000000..d1749251 --- /dev/null +++ b/app/features/help/content/pt-PT/audit-log.md @@ -0,0 +1,24 @@ +--- + +slug: audit-log +title: Como encontro quem fez o quê no registo de auditoria? +summary: As ações sensíveis da congregação, por pessoa, ação e período. +module: settings +permission: CanConfigureCongregation +keywords: registo de auditoria, auditoria, histórico, ações, inícios de sessão, permissões, eliminações, quem fez, rastreabilidade, segurança +related: congregation-data +order: 5 +--- + +O registo de auditoria guarda as ações sensíveis feitas na congregação: inícios de sessão, permissões, dados, eliminações. Cada linha indica quando, quem, que ação e sobre o quê. + +## Procurar uma ação + +1. Em **Definições › Registo de auditoria**, escolha o **Período**: os últimos 7 ou 30 dias, os últimos 3 ou 12 meses, **Sempre**, ou **Datas escolhidas**. +2. Para uma pessoa, escreva o nome na pesquisa. Para um tipo de ação, escolha-o em **Ação**. + + ![A barra do registo de auditoria: a pesquisa, a ação, o período e o número de ações](capture:settings-audit-toolbar) + +3. Clique numa linha para ver o detalhe ao lado da lista. + +As ações feitas pela própria aplicação, como as tarefas automáticas, aparecem em nome de **A aplicação**. diff --git a/app/features/help/content/pt-PT/congregation-data.md b/app/features/help/content/pt-PT/congregation-data.md new file mode 100644 index 00000000..7f00d8eb --- /dev/null +++ b/app/features/help/content/pt-PT/congregation-data.md @@ -0,0 +1,32 @@ +--- + +slug: congregation-data +title: Como exporto ou importo os dados da congregação? +summary: Um arquivo .unitae com todos os dados, para os guardar ou levar para outro lado. +module: settings +permission: CanExportCongregationData, CanImportCongregationData +keywords: exportar, exportação, importar, importação, arquivo, cópia de segurança, dados, unitae, transferência, migração, registo de auditoria +related: audit-log +order: 4 +--- + +**Definições › Importar e exportar** cria um arquivo `.unitae` com todos os dados da congregação, e recebe um arquivo criado pelo Unitae, por exemplo para passar de uma instância para outra. + +## Exportar + +1. Em **Definições › Importar e exportar**, escolha o que o arquivo inclui além dos dados: **Incluir os documentos do quadro de anúncios (PDF)** e **Incluir o registo de auditoria**. Ambos podem tornar o arquivo muito mais pesado. +2. Clique em **Iniciar exportação**. O arquivo é preparado em segundo plano. + + ![A secção Exportar: os documentos do quadro, o registo de auditoria e Iniciar exportação](capture:settings-data-export) + +3. Quando estiver pronto, clique em **Transferir arquivo**. + +Os arquivos anteriores ficam em **Exportações anteriores**, para os transferir de novo. + +## Importar + +1. Em **Importar**, largue o arquivo `.unitae` e clique em **Ler o arquivo**. +2. A aplicação mostra o que ele contém: os dados a importar, os elementos que já existem, atualizados ou ignorados, e os avisos. +3. Se estiver tudo bem, clique em **Iniciar importação**. + +Se a importação falhar, os dados da congregação não são alterados. Importar exige ser administrador. diff --git a/app/features/help/content/pt-PT/give-rights.md b/app/features/help/content/pt-PT/give-rights.md new file mode 100644 index 00000000..fd9f39a9 --- /dev/null +++ b/app/features/help/content/pt-PT/give-rights.md @@ -0,0 +1,43 @@ +--- + +slug: give-rights +title: Como dou uma permissão a alguém? +summary: As permissões passam pelas funções: dar uma função, ou mudar o que uma função permite. +module: settings +permission: CanManageUsers, CanConfigurePermissions +keywords: permissão, permissões, função, funções, acesso, dar, retirar, administrador, conta +related: invite-user, organigram, reset-two-step +order: 3 +--- + +Uma permissão nunca se dá diretamente a uma pessoa: passa por uma função. Uma pessoa tem as permissões de todas as suas funções. + +Há três tipos de funções: + +- **As funções do registo** seguem o que diz o registo de cada pessoa: ancião, servo ministerial, pioneiro… Mudam quando o registo muda. +- **As funções da congregação** são criadas pela congregação no organigrama, e dadas a partir do organigrama ou da conta. +- **Administrador** pode fazer tudo, incluindo dar esta função. + +## Dar uma função a alguém + +1. Em **Definições › Utilizadores**, abra a conta da pessoa. +2. Em **Funções**, marque a função a dar, ou desmarque-a para a retirar, e clique em **Guardar**. + + ![O início da secção Funções de uma conta: as funções a marcar, marcadas as que a pessoa já tem](capture:settings-account-roles) + +Uma função de uma só pessoa (uma função pessoal do organigrama) dá-se a partir do organigrama, não aqui. + +## Mudar o que uma função permite + +1. Em **Definições › Funções e permissões**, escolha a função. +2. Marque as permissões que ela dá, categoria a categoria. Algumas permissões precisam de outra: a linha indica-o. +3. Clique em **Guardar**. + +A alteração vale para todas as pessoas que têm essa função. + +## Bom saber + +- Só pode dar as permissões que tem; caso contrário, um administrador trata disso. +- Só um administrador muda o que uma função do registo permite. +- O administrador não se restringe: para retirar uma permissão a um administrador, retire-lhe essa função e dê-lhe uma função da congregação. +- A aplicação recusa deixar a congregação sem administrador. diff --git a/app/features/help/content/pt-PT/invite-user.md b/app/features/help/content/pt-PT/invite-user.md new file mode 100644 index 00000000..cb52eabc --- /dev/null +++ b/app/features/help/content/pt-PT/invite-user.md @@ -0,0 +1,38 @@ +--- + +slug: invite-user +title: Como convido alguém a iniciar sessão? +summary: Criar a conta, a partir do registo da pessoa ou de Definições › Utilizadores. +module: settings +permission: CanManageUsers, CanManagePublishers +keywords: convidar, convite, conta, utilizador, iniciar sessão, e-mail, palavra-passe, novo utilizador, reenviar +related: give-rights, reset-two-step +order: 2 +--- + +Para iniciar sessão, uma pessoa precisa de uma conta. Recebe um e-mail para escolher a palavra-passe e depois inicia sessão com o seu endereço. + +## Para um publicador + +1. Abra o registo da pessoa em **Publicadores**. +2. No menu **…**, em **Conta**, escolha **Criar conta de início de sessão…**. +3. Escreva o endereço de e-mail e clique em **Criar conta**. + +A conta fica ligada ao registo: o nome vem dele, e a pessoa recebe as funções do seu registo. + +## Para alguém sem registo + +1. Em **Definições › Utilizadores**, clique em **Novo utilizador**. +2. Preencha o **Nome próprio**, o **Apelido** e o **E-mail de início de sessão**. + + ![A janela Novo utilizador: nome próprio, apelido e e-mail de início de sessão](capture:settings-new-user) + +3. Clique em **Criar e enviar convite**. + +As funções dão-se depois na página da pessoa. + +## Acompanhar o convite + +Enquanto a pessoa não escolher a palavra-passe, a conta indica **Convite enviado** na lista de utilizadores. Se o e-mail se perdeu, abra a conta e clique em **Reenviar convite…**: a nova ligação substitui as anteriores. + +Um endereço só serve para uma conta. diff --git a/app/features/help/content/pt-PT/organigram.md b/app/features/help/content/pt-PT/organigram.md new file mode 100644 index 00000000..7c93651d --- /dev/null +++ b/app/features/help/content/pt-PT/organigram.md @@ -0,0 +1,35 @@ +--- + +slug: organigram +title: Como mantenho o organigrama da congregação? +summary: Criar as funções, nomear as pessoas e formar as equipas. +module: organigram +permission: CanManageRoles +keywords: organigrama, função, funções, equipa, equipas, superintendente, ajudante, membro, titular, comissão, nomear, substituir, quadro +related: give-rights +order: 1 +--- + +O organigrama mostra as responsabilidades da congregação. Cada caixa é uma função: uma **equipa**, com responsáveis, ajudantes e membros, ou uma **função pessoal**, de uma só pessoa. Começa pelos anciãos e pelos servos ministeriais, atualizados a partir dos registos. + +## Criar uma função + +1. Na barra lateral, abra **Organigrama** e clique em **Nova função**. +2. Dê-lhe um **Nome** e, se quiser, uma **Descrição**. +3. Escolha onde a **Colocar**: debaixo de que função fica, ou **Fora do organigrama** para uma função sem caixa na árvore nem no quadro. +4. Clique em **Criar função**. + +## Nomear as pessoas + +1. Clique na caixa da função: o painel abre-se. +2. Procure a pessoa. Numa equipa, escolha **Responsável** ou **Ajudante**. Depois clique em **Nome**. Numa função pessoal já ocupada, o botão passa a **Substituir**: o titular muda, os ajudantes ficam. + + ![O painel de uma equipa: os responsáveis, a pesquisa para nomear alguém, e os membros](capture:organigram-role-panel) + +Uma função pode ser dada a um publicador sem conta. Os membros de uma equipa adicionam-se no separador **Equipas**: uma caixa marcada adiciona a pessoa, e fica guardado de imediato. + +## Editar ou mover uma função + +No painel da função, **Editar** muda o nome, o tipo, a descrição e a **Nota no quadro de anúncios**, impressa debaixo da função no organigrama do quadro. No fundo do painel, **Colocar no organigrama** coloca-a debaixo de outra função, sobe-a ou desce-a, ou retira-a do organigrama. **Eliminar função** só é possível depois de mover as funções que estão debaixo dela. + +O que cada função permite fazer na aplicação define-se em **Definições › Funções e permissões**. diff --git a/app/features/help/content/pt-PT/reset-two-step.md b/app/features/help/content/pt-PT/reset-two-step.md new file mode 100644 index 00000000..b9c5ee9e --- /dev/null +++ b/app/features/help/content/pt-PT/reset-two-step.md @@ -0,0 +1,36 @@ +--- + +slug: reset-two-step +title: Como ajudo alguém que já não consegue iniciar sessão? +summary: Reenviar o convite, enviar uma ligação de palavra-passe, ou repor a verificação em dois passos. +module: settings +permission: CanManageUsers +keywords: iniciar sessão, bloqueado, palavra-passe esquecida, verificação em dois passos, autenticação de dois fatores, código, telemóvel perdido, repor, desbloquear, convite, ligação +related: invite-user, two-step-verification +order: 6 +--- + +Quando alguém já não consegue iniciar sessão, a secção **Segurança** da sua conta tem o que precisa para ajudar. Abra a conta em **Definições › Utilizadores**. + +![A secção Segurança de uma conta: palavra-passe, verificação em dois passos e os dados da pessoa](capture:settings-account-security) + +## Perdeu o telemóvel + +Se a verificação em dois passos estiver ativada e a pessoa já não conseguir ler os códigos: + +1. Em **Segurança**, na linha **Verificação em dois passos**, clique em **Repor…**. +2. Confirme com **Repor**. + +A pessoa passa a iniciar sessão só com a palavra-passe, e pode voltar a ativá-la em **A minha conta**. + +## Esqueceu-se da palavra-passe + +Na linha **Palavra-passe**, clique em **Enviar ligação…** e depois em **Enviar ligação**. A pessoa recebe uma ligação para escolher uma nova palavra-passe; os seus dispositivos terminam a sessão de imediato. + +Também o pode fazer sozinha no ecrã de início de sessão. + +## Nunca recebeu o convite + +Enquanto a pessoa não escolher a palavra-passe, a secção propõe **Reenviar convite…**. A nova ligação substitui as anteriores. + +A conta de um administrador só é gerida por um administrador. diff --git a/app/features/help/entry-points.test.ts b/app/features/help/entry-points.test.ts index beba47e7..14b2c073 100644 --- a/app/features/help/entry-points.test.ts +++ b/app/features/help/entry-points.test.ts @@ -53,6 +53,14 @@ const PINS: Record = { 'features/publishers/routes/publishers/group.tsx': 'field-service-reports', 'features/publishers/routes/activity/publisher-list.tsx': 'field-service-reports', 'features/publishers/routes/activity/pioneers.tsx': 'pioneers', + 'features/settings/routes/users/user-list.tsx': 'invite-user', + 'features/settings/routes/users/account.tsx': 'give-rights', + 'features/settings/routes/roles.tsx': 'give-rights', + 'features/settings/routes/data/settings.tsx': 'congregation-data', + 'features/settings/routes/audit-log.tsx': 'audit-log', + // The organigram's screens draw their own heading: the « ? » goes in the top bar, and beside the title on a phone. + 'features/congregation/routes/roles/organigram.tsx': 'organigram', + 'features/congregation/routes/roles/role-list.tsx': 'organigram', } // The routes with a loader matched above the pinned pages (see app/routes.ts). diff --git a/app/features/help/model/help.type.ts b/app/features/help/model/help.type.ts index 3b49a1dd..da273353 100644 --- a/app/features/help/model/help.type.ts +++ b/app/features/help/model/help.type.ts @@ -24,6 +24,7 @@ export const HELP_MODULES = [ 'publishers', 'groups', 'activity', + 'organigram', 'programs', 'external-speakers', 'attendance', diff --git a/app/features/help/server/help-content.server.test.ts b/app/features/help/server/help-content.server.test.ts index 0c7849cc..208cb9f9 100644 --- a/app/features/help/server/help-content.server.test.ts +++ b/app/features/help/server/help-content.server.test.ts @@ -13,6 +13,7 @@ const SHIPPED_SLUGS = [ 'activity-exports', 'attendance-entry', 'attendance-s88', + 'audit-log', 'bano', 'batch-territories', 'board-add-pdf', @@ -24,21 +25,26 @@ const SHIPPED_SLUGS = [ 'board-versions', 'calendar-feed', 'campaign-create', + 'congregation-data', 'create-territory', 'emergency-roster', 'external-speakers', 'field-service-reports', + 'give-rights', 'groups', + 'invite-user', 'language', 'my-data', 'my-parts', 'my-territories', 'notifications', + 'organigram', 'password', 'phone-territories', 'pioneers', 'prospection', 'publisher-arrivals-departures', + 'reset-two-step', 'split-territory', 'territories-settings', 'territory-attributions', @@ -372,6 +378,12 @@ describe('loadHelpArticles: the articles as shipped', () => { expect(fr.get('board-dynamic')?.permission).toEqual(['CanManageDynamicBoardDocuments']) expect(fr.get('board-sections')?.permission).toEqual(['CanConfigureBoardSections', 'CanOrganiseBoardDocuments']) expect(fr.get('board-reads')?.permission).toEqual(['CanReviewBoardDocuments']) + expect(fr.get('invite-user')?.permission).toEqual(['CanManageUsers', 'CanManagePublishers']) + expect(fr.get('give-rights')?.permission).toEqual(['CanManageUsers', 'CanConfigurePermissions']) + expect(fr.get('organigram')?.permission).toEqual(['CanManageRoles']) + expect(fr.get('congregation-data')?.permission).toEqual(['CanExportCongregationData', 'CanImportCongregationData']) + expect(fr.get('audit-log')?.permission).toEqual(['CanConfigureCongregation']) + expect(fr.get('reset-two-step')?.permission).toEqual(['CanManageUsers']) expect(fr.get('territory-stats')?.permission).toEqual(['CanManageTerritories']) for (const slug of [ 'my-parts', diff --git a/app/features/help/ui/help-module-label.ts b/app/features/help/ui/help-module-label.ts index 13d0e63a..436fdc58 100644 --- a/app/features/help/ui/help-module-label.ts +++ b/app/features/help/ui/help-module-label.ts @@ -9,6 +9,7 @@ const LABELS: Record string> = { publishers: m.sidebar_publishers, groups: m.sidebar_publisher_groups, activity: m.sidebar_activity, + organigram: m.sidebar_assembly_organigram, programs: m.sidebar_programs, 'external-speakers': m.sidebar_external_speakers, attendance: m.sidebar_attendance, diff --git a/app/features/settings/routes/audit-log.tsx b/app/features/settings/routes/audit-log.tsx index 954a5d19..42591013 100644 --- a/app/features/settings/routes/audit-log.tsx +++ b/app/features/settings/routes/audit-log.tsx @@ -1,4 +1,5 @@ import { SidePanel } from '@unitae/ui' +import { HelpEntryButton } from '~/features/help' import { auditActionLabel } from '~/features/settings/model/audit-actions' import { auditDetails } from '~/features/settings/model/audit-details' import { auditEntityLabel } from '~/features/settings/model/audit-entities' @@ -25,6 +26,8 @@ import type { Route } from './+types/audit-log' export const meta: Route.MetaFunction = () => [{ title: m.audit_log_meta_title() }] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + /** The sizes the pagination offers; any other asks for the first. */ const PAGE_SIZES = [25, 50, 100, 250, 500, 1000, 2000] @@ -90,7 +93,11 @@ export default function AuditLogPage({ loaderData }: Route.ComponentProps) { return (
- + } + subtitle={m.audit_log_subtitle()} + />
{/* The `list` container: beside the docked detail the table drops to its docked columns. */} diff --git a/app/features/settings/routes/data/settings.tsx b/app/features/settings/routes/data/settings.tsx index f5804c3e..62219b02 100644 --- a/app/features/settings/routes/data/settings.tsx +++ b/app/features/settings/routes/data/settings.tsx @@ -1,4 +1,5 @@ import { redirect } from 'react-router' +import { HelpEntryButton } from '~/features/help' import { getOwnedDataTransferJob } from '~/features/settings/server/data-transfer.queries' import { dataTransferQueue } from '~/features/settings/server/data-transfer-queue.server' import { validateImport } from '~/features/settings/server/import-congregation.server' @@ -13,6 +14,8 @@ import type { Route } from './+types/settings' export const meta: Route.MetaFunction = () => [{ title: m.settings_data_meta_title() }] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + function rightsOf(permissions: Set) { // An import restores roles, permissions, accounts and assignments, so it can grant anything: admin only. const canImport = permissions.has(Permission.CanImportCongregationData) && permissions.has(Permission.CanDoAnything) @@ -90,7 +93,11 @@ export default function DataPage({ loaderData }: Route.ComponentProps) { const { canExport, canImport, history, timeZone, exportJob, importJob, pending, expired } = loaderData return (
- + } + subtitle={m.settings_data_subtitle()} + />
{canExport && } {canImport && } diff --git a/app/features/settings/routes/roles.tsx b/app/features/settings/routes/roles.tsx index cf12d758..4ee2e5db 100644 --- a/app/features/settings/routes/roles.tsx +++ b/app/features/settings/routes/roles.tsx @@ -2,6 +2,7 @@ import { parseWithZod } from '@conform-to/zod/v4' import { Callout, SidePanel } from '@unitae/ui' import { useEffect } from 'react' import { data, Link, redirect, useFetcher, useSearchParams } from 'react-router' +import { HelpEntryButton } from '~/features/help' import { editPermissionsSchema } from '~/features/settings/schemas/permissions.schema' import { listRolesForPermissions } from '~/features/settings/server/role-permissions.queries' import { peopleLabel, RoleList } from '~/features/settings/ui/RoleList' @@ -31,6 +32,8 @@ import type { Route } from './+types/roles' export const meta: Route.MetaFunction = () => [{ title: m.settings_roles_meta_title() }] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + /** Every right, under its category, in the categories' order. */ function permissionCatalogue(): PermissionCategoryGroup[] { const keys = Object.values(Permission).filter(key => key !== Permission.CanDoAnything) @@ -131,6 +134,7 @@ export default function RolesPage({ loaderData }: Route.ComponentProps) {
} subtitle={m.settings_roles_subtitle()} actions={ canManageRoles && ( diff --git a/app/features/settings/routes/users/account.tsx b/app/features/settings/routes/users/account.tsx index 53118ea4..9e23807f 100644 --- a/app/features/settings/routes/users/account.tsx +++ b/app/features/settings/routes/users/account.tsx @@ -2,6 +2,7 @@ import { getFormProps, useForm } from '@conform-to/react' import { parseWithZod } from '@conform-to/zod/v4' import { Status } from '@unitae/ui' import { data, redirect } from 'react-router' +import { HelpEntryButton } from '~/features/help' import { editUserSchema } from '~/features/settings/schemas/user.schema' import { updateAccount } from '~/features/settings/server/update-account.server' import { getAccountPage } from '~/features/settings/server/user-accounts.queries' @@ -35,6 +36,8 @@ export const meta: Route.MetaFunction = ({ loaderData }) => [ { title: loaderData ? m.settings_account_meta_title({ name: loaderData.name }) : m.settings_users_meta_title() }, ] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + export async function loader({ params, context }: Route.LoaderArgs) { const permissions = context.get(permissionsContext) const currentUser = context.get(currentAccountContext) @@ -130,6 +133,7 @@ export default function AccountPage({ loaderData, actionData }: Route.ComponentP
} subtitle={page.email} titleBadge={state && {state.label}} trail={[{ label: m.settings_entry_users(), to: '/settings/users' }]} diff --git a/app/features/settings/routes/users/user-list.tsx b/app/features/settings/routes/users/user-list.tsx index ee0caad4..ab030906 100644 --- a/app/features/settings/routes/users/user-list.tsx +++ b/app/features/settings/routes/users/user-list.tsx @@ -1,6 +1,7 @@ import { Plus } from 'lucide-react' import { useState } from 'react' import { redirect, useSearchParams } from 'react-router' +import { HelpEntryButton } from '~/features/help' import { listUserAccounts } from '~/features/settings/server/user-accounts.queries' import { NewUserDialog } from '~/features/settings/ui/NewUserDialog' import { SettingsHeader } from '~/features/settings/ui/SettingsHeader' @@ -15,6 +16,8 @@ import type { Route } from './+types/user-list' export const meta: Route.MetaFunction = () => [{ title: m.settings_users_meta_title() }] +export { skipRevalidationForHelpPanel as shouldRevalidate } from '~/features/help' + const VIEWS = ['all', 'active', 'deactivated'] as const type View = (typeof VIEWS)[number] const isView = (value: string | null): value is View => VIEWS.includes(value as View) @@ -66,6 +69,7 @@ export default function UserListPage({ loaderData }: Route.ComponentProps) {
} subtitle={m.settings_users_subtitle()} actions={ canManage && ( diff --git a/public/help-captures/en/organigram-role-panel.dark.webp b/public/help-captures/en/organigram-role-panel.dark.webp new file mode 100644 index 00000000..9dc1334e Binary files /dev/null and b/public/help-captures/en/organigram-role-panel.dark.webp differ diff --git a/public/help-captures/en/organigram-role-panel.webp b/public/help-captures/en/organigram-role-panel.webp new file mode 100644 index 00000000..7085ec11 Binary files /dev/null and b/public/help-captures/en/organigram-role-panel.webp differ diff --git a/public/help-captures/en/settings-account-roles.dark.webp b/public/help-captures/en/settings-account-roles.dark.webp new file mode 100644 index 00000000..f06957cd Binary files /dev/null and b/public/help-captures/en/settings-account-roles.dark.webp differ diff --git a/public/help-captures/en/settings-account-roles.webp b/public/help-captures/en/settings-account-roles.webp new file mode 100644 index 00000000..30832173 Binary files /dev/null and b/public/help-captures/en/settings-account-roles.webp differ diff --git a/public/help-captures/en/settings-account-security.dark.webp b/public/help-captures/en/settings-account-security.dark.webp new file mode 100644 index 00000000..d2fc9441 Binary files /dev/null and b/public/help-captures/en/settings-account-security.dark.webp differ diff --git a/public/help-captures/en/settings-account-security.webp b/public/help-captures/en/settings-account-security.webp new file mode 100644 index 00000000..3692c969 Binary files /dev/null and b/public/help-captures/en/settings-account-security.webp differ diff --git a/public/help-captures/en/settings-audit-toolbar.dark.webp b/public/help-captures/en/settings-audit-toolbar.dark.webp new file mode 100644 index 00000000..4f8993f3 Binary files /dev/null and b/public/help-captures/en/settings-audit-toolbar.dark.webp differ diff --git a/public/help-captures/en/settings-audit-toolbar.webp b/public/help-captures/en/settings-audit-toolbar.webp new file mode 100644 index 00000000..d53d99a4 Binary files /dev/null and b/public/help-captures/en/settings-audit-toolbar.webp differ diff --git a/public/help-captures/en/settings-data-export.dark.webp b/public/help-captures/en/settings-data-export.dark.webp new file mode 100644 index 00000000..678c7a44 Binary files /dev/null and b/public/help-captures/en/settings-data-export.dark.webp differ diff --git a/public/help-captures/en/settings-data-export.webp b/public/help-captures/en/settings-data-export.webp new file mode 100644 index 00000000..f6785efc Binary files /dev/null and b/public/help-captures/en/settings-data-export.webp differ diff --git a/public/help-captures/en/settings-new-user.dark.webp b/public/help-captures/en/settings-new-user.dark.webp new file mode 100644 index 00000000..9ec5c757 Binary files /dev/null and b/public/help-captures/en/settings-new-user.dark.webp differ diff --git a/public/help-captures/en/settings-new-user.webp b/public/help-captures/en/settings-new-user.webp new file mode 100644 index 00000000..93bde0de Binary files /dev/null and b/public/help-captures/en/settings-new-user.webp differ diff --git a/public/help-captures/fr/organigram-role-panel.dark.webp b/public/help-captures/fr/organigram-role-panel.dark.webp new file mode 100644 index 00000000..1d133b94 Binary files /dev/null and b/public/help-captures/fr/organigram-role-panel.dark.webp differ diff --git a/public/help-captures/fr/organigram-role-panel.webp b/public/help-captures/fr/organigram-role-panel.webp new file mode 100644 index 00000000..55228161 Binary files /dev/null and b/public/help-captures/fr/organigram-role-panel.webp differ diff --git a/public/help-captures/fr/settings-account-roles.dark.webp b/public/help-captures/fr/settings-account-roles.dark.webp new file mode 100644 index 00000000..17c2d01c Binary files /dev/null and b/public/help-captures/fr/settings-account-roles.dark.webp differ diff --git a/public/help-captures/fr/settings-account-roles.webp b/public/help-captures/fr/settings-account-roles.webp new file mode 100644 index 00000000..3e91bbc5 Binary files /dev/null and b/public/help-captures/fr/settings-account-roles.webp differ diff --git a/public/help-captures/fr/settings-account-security.dark.webp b/public/help-captures/fr/settings-account-security.dark.webp new file mode 100644 index 00000000..4e674b48 Binary files /dev/null and b/public/help-captures/fr/settings-account-security.dark.webp differ diff --git a/public/help-captures/fr/settings-account-security.webp b/public/help-captures/fr/settings-account-security.webp new file mode 100644 index 00000000..e348666e Binary files /dev/null and b/public/help-captures/fr/settings-account-security.webp differ diff --git a/public/help-captures/fr/settings-audit-toolbar.dark.webp b/public/help-captures/fr/settings-audit-toolbar.dark.webp new file mode 100644 index 00000000..c7e57281 Binary files /dev/null and b/public/help-captures/fr/settings-audit-toolbar.dark.webp differ diff --git a/public/help-captures/fr/settings-audit-toolbar.webp b/public/help-captures/fr/settings-audit-toolbar.webp new file mode 100644 index 00000000..5123f4e6 Binary files /dev/null and b/public/help-captures/fr/settings-audit-toolbar.webp differ diff --git a/public/help-captures/fr/settings-data-export.dark.webp b/public/help-captures/fr/settings-data-export.dark.webp new file mode 100644 index 00000000..fa4340a7 Binary files /dev/null and b/public/help-captures/fr/settings-data-export.dark.webp differ diff --git a/public/help-captures/fr/settings-data-export.webp b/public/help-captures/fr/settings-data-export.webp new file mode 100644 index 00000000..7137c300 Binary files /dev/null and b/public/help-captures/fr/settings-data-export.webp differ diff --git a/public/help-captures/fr/settings-new-user.dark.webp b/public/help-captures/fr/settings-new-user.dark.webp new file mode 100644 index 00000000..794d4d5b Binary files /dev/null and b/public/help-captures/fr/settings-new-user.dark.webp differ diff --git a/public/help-captures/fr/settings-new-user.webp b/public/help-captures/fr/settings-new-user.webp new file mode 100644 index 00000000..834d08d1 Binary files /dev/null and b/public/help-captures/fr/settings-new-user.webp differ diff --git a/public/help-captures/pt-PT/organigram-role-panel.dark.webp b/public/help-captures/pt-PT/organigram-role-panel.dark.webp new file mode 100644 index 00000000..8dceaf50 Binary files /dev/null and b/public/help-captures/pt-PT/organigram-role-panel.dark.webp differ diff --git a/public/help-captures/pt-PT/organigram-role-panel.webp b/public/help-captures/pt-PT/organigram-role-panel.webp new file mode 100644 index 00000000..c18e87e3 Binary files /dev/null and b/public/help-captures/pt-PT/organigram-role-panel.webp differ diff --git a/public/help-captures/pt-PT/settings-account-roles.dark.webp b/public/help-captures/pt-PT/settings-account-roles.dark.webp new file mode 100644 index 00000000..92045cd1 Binary files /dev/null and b/public/help-captures/pt-PT/settings-account-roles.dark.webp differ diff --git a/public/help-captures/pt-PT/settings-account-roles.webp b/public/help-captures/pt-PT/settings-account-roles.webp new file mode 100644 index 00000000..e9184989 Binary files /dev/null and b/public/help-captures/pt-PT/settings-account-roles.webp differ diff --git a/public/help-captures/pt-PT/settings-account-security.dark.webp b/public/help-captures/pt-PT/settings-account-security.dark.webp new file mode 100644 index 00000000..f90b9549 Binary files /dev/null and b/public/help-captures/pt-PT/settings-account-security.dark.webp differ diff --git a/public/help-captures/pt-PT/settings-account-security.webp b/public/help-captures/pt-PT/settings-account-security.webp new file mode 100644 index 00000000..ef481fa1 Binary files /dev/null and b/public/help-captures/pt-PT/settings-account-security.webp differ diff --git a/public/help-captures/pt-PT/settings-audit-toolbar.dark.webp b/public/help-captures/pt-PT/settings-audit-toolbar.dark.webp new file mode 100644 index 00000000..aac150fa Binary files /dev/null and b/public/help-captures/pt-PT/settings-audit-toolbar.dark.webp differ diff --git a/public/help-captures/pt-PT/settings-audit-toolbar.webp b/public/help-captures/pt-PT/settings-audit-toolbar.webp new file mode 100644 index 00000000..3248817d Binary files /dev/null and b/public/help-captures/pt-PT/settings-audit-toolbar.webp differ diff --git a/public/help-captures/pt-PT/settings-data-export.dark.webp b/public/help-captures/pt-PT/settings-data-export.dark.webp new file mode 100644 index 00000000..7a5b5409 Binary files /dev/null and b/public/help-captures/pt-PT/settings-data-export.dark.webp differ diff --git a/public/help-captures/pt-PT/settings-data-export.webp b/public/help-captures/pt-PT/settings-data-export.webp new file mode 100644 index 00000000..fc3ecccb Binary files /dev/null and b/public/help-captures/pt-PT/settings-data-export.webp differ diff --git a/public/help-captures/pt-PT/settings-new-user.dark.webp b/public/help-captures/pt-PT/settings-new-user.dark.webp new file mode 100644 index 00000000..93d47c7e Binary files /dev/null and b/public/help-captures/pt-PT/settings-new-user.dark.webp differ diff --git a/public/help-captures/pt-PT/settings-new-user.webp b/public/help-captures/pt-PT/settings-new-user.webp new file mode 100644 index 00000000..302b2f5e Binary files /dev/null and b/public/help-captures/pt-PT/settings-new-user.webp differ diff --git a/scripts/help-captures/shots.ts b/scripts/help-captures/shots.ts index d154ae07..6e218696 100644 --- a/scripts/help-captures/shots.ts +++ b/scripts/help-captures/shots.ts @@ -31,6 +31,9 @@ const MARC = 'marc.dupont@demo.unitae.app' const MAXIME = 'maxime.mensah@demo.unitae.app' // Maxime's publisher record: someone else's for MARC, whose own status he could not change. const MAXIME_RECORD = 100 +// Maxime's account, for the pages about an account; and a team of the organigram with people in it. +const MAXIME_ACCOUNT = 83 +const AUDIO_VIDEO_ROLE = 64 /** The nearest enclosing element that matches, e.g. the row around a button. */ function closest(locator: Locator, xpathTest: string): Locator { @@ -521,6 +524,75 @@ export const HELP_SHOTS: HelpShot[] = [ margin: -1, viewport: { width: 1600, height: 900 }, }, + { + // invite-user: « Nouvel utilisateur » on Réglages › Utilisateurs. + id: 'settings-new-user', + account: MARC, + path: '/settings/users', + prepare: async (page, locale) => { + await page.getByRole('button', { name: m.settings_users_new_button({}, { locale }), exact: true }).click() + await page.getByRole('dialog').waitFor() + }, + frame: page => [page.getByRole('dialog')], + margin: -1, + }, + { + // give-rights: the « Rôles » section of an account. + id: 'settings-account-roles', + account: MARC, + path: `/settings/users/${MAXIME_ACCOUNT}`, + // The section's title and its first roles: the whole list runs to every role of the congregation. + frame: (page, locale) => [ + page.getByText(m.settings_account_section_roles({}, { locale }), { exact: true }).first(), + section(page, m.settings_account_section_roles({}, { locale })).locator('label').nth(3), + ], + margin: 12, + viewport: { width: 1100, height: 1200 }, + }, + { + // reset-two-step: the « Sécurité » section of an account. + id: 'settings-account-security', + account: MARC, + path: `/settings/users/${MAXIME_ACCOUNT}`, + frame: (page, locale) => [section(page, m.settings_account_section_security({}, { locale }))], + margin: 10, + viewport: { width: 1100, height: 1400 }, + }, + { + // organigram: a team's panel, with its people and the search to name someone. + id: 'organigram-role-panel', + account: MARC, + path: `/congregation/roles/organigram?role=${AUDIO_VIDEO_ROLE}`, + prepare: settledPanel, + frame: page => [sidePanel(page)], + margin: -1, + viewport: { width: 1600, height: 900 }, + }, + { + // congregation-data: « Exporter » on Réglages › Import et export. + id: 'settings-data-export', + account: MARC, + path: '/settings/data', + frame: (page, locale) => [section(page, m.settings_data_export({}, { locale }))], + margin: 10, + viewport: { width: 1100 }, + }, + { + // audit-log: the bar above the journal: the search, the action, the period, the count. + id: 'settings-audit-toolbar', + account: MARC, + path: '/settings/audit-log', + // The smallest block holding the search and the period: the whole bar, with the count. + frame: (page, locale) => [ + page + .locator('div:visible') + .filter({ has: page.getByPlaceholder(m.audit_log_search({}, { locale })) }) + .filter({ has: page.getByText(m.audit_log_period_30d({}, { locale }), { exact: true }) }) + .last(), + ], + margin: 12, + viewport: { width: 1100 }, + }, ] /** Waits for the docked side panel to finish sliding in: framed before, the crop would cut its right side. */ diff --git a/scripts/help-captures/translate-demo-pt-PT.sql b/scripts/help-captures/translate-demo-pt-PT.sql index 40fb3496..813b786e 100644 --- a/scripts/help-captures/translate-demo-pt-PT.sql +++ b/scripts/help-captures/translate-demo-pt-PT.sql @@ -20,7 +20,7 @@ UPDATE "EventPart" t SET "readerLabel" = v.pt FROM (VALUES ('Orateur', 'Orador') UPDATE "TemplatePart" t SET "readerLabel" = v.pt FROM (VALUES ('Orateur', 'Orador'), ('Lecteur', 'Leitor'), ('Proclamateur', 'Publicador'), ('Interlocuteur', 'Morador'), ('Conducteur', 'Dirigente'), ('Président', 'Presidente'), ('Frère', 'Irmão')) AS v(fr, pt) WHERE t."readerLabel" = v.fr; UPDATE "EventServicePart" t SET "name" = v.pt FROM (VALUES ('Sono (audio)', 'Áudio'), ('Sono (vidéo)', 'Vídeo'), ('Accueil (porte)', 'Indicador (entrada)'), ('Accueil (auditorium)', 'Indicador (auditório)'), ('Accueil (zoom)', 'Indicador (Zoom)'), ('Perchiste (gauche)', 'Microfones (esquerda)'), ('Perchiste (droite)', 'Microfones (direita)'), ('Audio-vidéo', 'Áudio e vídeo'), ('Estrade', 'Palco'), ('Préposés à l’accueil', 'Indicadores'), ('Nettoyage', 'Limpeza')) AS v(fr, pt) WHERE t."name" = v.fr; UPDATE "TemplateServicePart" t SET "name" = v.pt FROM (VALUES ('Sono (audio)', 'Áudio'), ('Sono (vidéo)', 'Vídeo'), ('Accueil (porte)', 'Indicador (entrada)'), ('Accueil (auditorium)', 'Indicador (auditório)'), ('Accueil (zoom)', 'Indicador (Zoom)'), ('Perchiste (gauche)', 'Microfones (esquerda)'), ('Perchiste (droite)', 'Microfones (direita)'), ('Audio-vidéo', 'Áudio e vídeo'), ('Estrade', 'Palco'), ('Préposés à l’accueil', 'Indicadores'), ('Nettoyage', 'Limpeza')) AS v(fr, pt) WHERE t."name" = v.fr; -UPDATE "Role" t SET "name" = v.pt FROM (VALUES ('Conducteur de l’étude de la Tour de Garde', 'Dirigente do Estudo de A Sentinela'), ('Conseiller pour l’enseignement', 'Conselheiro assistente'), ('Coordinateur du nettoyage', 'Coordenador da limpeza'), ('Coordinateur du programme des discours publics', 'Coordenador dos discursos públicos'), ('Covoiturage pour les compagnons âgés', 'Transporte para os mais idosos'), ('Lecteurs EBA/TG', 'Leitores (Estudo Bíblico, A Sentinela)'), ('Orateurs DP', 'Oradores de discursos públicos'), ('Orateurs EBA', 'Dirigentes do Estudo Bíblico de Congregação'), ('Orateurs Joyaux', 'Oradores de Tesouros'), ('Orateurs Perles', 'Oradores de Pérolas espirituais'), ('Orateurs VCM', 'Oradores de Viver Como Cristãos'), ('Perches', 'Microfones'), ('Porte', 'Indicadores da entrada'), ('Prières publiques', 'Orações públicas'), ('Prospection', 'Levantamento de edifícios'), ('Présidents DP/TG', 'Presidentes da reunião de fim de semana'), ('Présidents VCM', 'Presidentes da reunião de semana'), ('RPP', 'Reunião dos superintendentes de grupo'), ('Responsable Réunion Vie Chrétienne et Ministère', 'Superintendente da Reunião Vida e Ministério Cristãos'), ('Responsable du programme des services', 'Coordenador da escala de serviços'), ('Scène', 'Palco'), ('Service Accueil', 'Indicadores'), ('Service Audio/Vidéo', 'Áudio e vídeo'), ('Service Comptes', 'Contas'), ('Service Publications', 'Publicações'), ('Service TPL', 'Testemunho público'), ('Service Territoires', 'Territórios'), ('Sono', 'Áudio'), ('Visite pastorale', 'Visitas de pastoreio')) AS v(fr, pt) WHERE t."name" = v.fr; +UPDATE "Role" t SET "name" = v.pt FROM (VALUES ('Conducteur de l’étude de la Tour de Garde', 'Dirigente do Estudo de A Sentinela'), ('Conseiller pour l’enseignement', 'Conselheiro assistente'), ('Coordinateur du nettoyage', 'Coordenador da limpeza'), ('Coordinateur du programme des discours publics', 'Coordenador dos discursos públicos'), ('Covoiturage pour les compagnons âgés', 'Transporte para os mais idosos'), ('Lecteurs EBA/TG', 'Leitores (Estudo Bíblico, A Sentinela)'), ('Orateurs DP', 'Oradores de discursos públicos'), ('Orateurs EBA', 'Dirigentes do Estudo Bíblico de Congregação'), ('Orateurs Joyaux', 'Oradores de Tesouros'), ('Orateurs Perles', 'Oradores de Pérolas espirituais'), ('Orateurs VCM', 'Oradores de Viver Como Cristãos'), ('Perches', 'Microfones'), ('Porte', 'Indicadores da entrada'), ('Prières publiques', 'Orações públicas'), ('Prospection', 'Levantamento de edifícios'), ('Présidents DP/TG', 'Presidentes da reunião de fim de semana'), ('Présidents VCM', 'Presidentes da reunião de semana'), ('RPP', 'Reunião dos superintendentes de grupo'), ('Responsable Réunion Vie Chrétienne et Ministère', 'Superintendente da Reunião Vida e Ministério Cristãos'), ('Responsable du programme des services', 'Coordenador da escala de serviços'), ('Scène', 'Palco'), ('Service Accueil', 'Indicadores'), ('Service Audio/Vidéo', 'Áudio e vídeo'), ('Service Comptes', 'Contas'), ('Service Publications', 'Publicações'), ('Service TPL', 'Testemunho público'), ('Service Territoires', 'Territórios'), ('Sono', 'Áudio'), ('Visite pastorale', 'Visitas de pastoreio'), ('Auditorium', 'Auditório')) AS v(fr, pt) WHERE t."name" = v.fr; UPDATE "PublisherGroup" t SET "name" = v.pt FROM (VALUES ('Groupe Centre', 'Grupo Centro'), ('Groupe Nord', 'Grupo Norte'), ('Groupe Sud', 'Grupo Sul'), ('Groupe Est', 'Grupo Este'), ('Groupe Ouest', 'Grupo Oeste')) AS v(fr, pt) WHERE t."name" = v.fr; UPDATE "BoardSection" t SET "name" = v.pt FROM (VALUES ('Annonces', 'Anúncios'), ('Programmes', 'Programas'), ('Prédication', 'Serviço de campo'), ('Entretien', 'Manutenção'), ('Comptes', 'Contas'), ('Vie de l’assemblée', 'Vida da congregação')) AS v(fr, pt) WHERE t."name" = v.fr; UPDATE "BoardDocument" t SET "title" = v.pt FROM (VALUES ('Accueil des nouveaux', 'Acolher os novos'), ('Visite du responsable de circonscription', 'Visita do superintendente de circuito'), ('Plan d’évacuation', 'Plano de evacuação'), ('Rapport des comptes', 'Relatório de contas'), ('Consignes de sécurité', 'Instruções de segurança'), ('Planning de nettoyage', 'Escala de limpeza'), ('Planning TPL', 'Escala de testemunho público'), ('Rendez-vous de prédication', 'Reuniões para o serviço de campo'), ('Assemblée de circonscription', 'Assembleia de circuito'), ('Programme des discours publics', 'Programa dos discursos públicos'), ('Rappel : covoiturage pour l’assemblée de circonscription', 'Lembrete: boleias para a assembleia de circuito'), ('Lettre du Collège central', 'Carta do Corpo Governante'), ('Changement d’horaire des réunions', 'Mudança do horário das reuniões')) AS v(fr, pt) WHERE t."title" = v.fr;