Term extraction: Set up organization - candidate list (#928) · Issues · GitLab.com / localization / Docs Site Localization

Term extraction: Set up organization - candidate list

#### Context Part of the EN baseline term extraction (#916+). The hub and sub-pages of the [Manage your organization](https://docs.gitlab.com/topics/set_up_organization/) section were scanned for terminology candidates. Pages processed: - Hub: `doc/topics/set_up_organization.md` - `doc/user/group/_index.md` - `doc/user/group/access_and_permissions.md` - `doc/user/group/manage.md` - `doc/user/namespace/_index.md` - `doc/user/members/_index.md` - `doc/user/project/members/sharing_projects_groups.md` - `doc/user/permissions.md` - `doc/user/custom_roles/_index.md` - `doc/user/profile/_index.md` - `doc/user/group/import/_index.md` - `doc/subscriptions/gitlab_com/_index.md` **Scope note:** extraction was limited to the section `_index` pages listed above — one level below the hub. Sub-pages of those sections were not scanned. Additional scope needs to be defined for a deeper pass. Each candidate was evaluated using the 8-criteria framework (2+ required) plus the translation-risk test: 1=Terminologization, 2=Confusability, 3=Specialization, 4=Frequency, 5=Visibility, 6=Novelty, 7=System relationships, 8=Standardization potential. `namespace` and `subgroup` are already covered in #923. @maud-L , before we proceed to writing TBX briefs and entries, your guidance is needed on: 1. Which terms should be included vs. skipped 2. For flagged Quickterm situations in the Notes column — add a comment or resolution #### How to review 1. **Read the table** 2. **Work through the checklist at the bottom** - check the box to include a term in the TBX, leave it unchecked to skip it. 3. **Add an inline comment on a checklist line** if you have a question, a different FR suggestion, or a reason for skipping. #### Extracted terms <table> <tr> <th>Term</th> <th>File(s)</th> <th>Count</th> <th>In Quickterm</th> <th>FR (from Quickterm)</th> <th>Notes</th> </tr> <tr> <td>top-level group</td> <td>doc/user/group/_index.md, doc/user/group/access_and_permissions.md, doc/user/group/manage.md, doc/user/permissions.md</td> <td>~60</td> <td>Yes</td> <td>groupe principal (Preferred)</td> <td>Root group in a hierarchy; has specific billing and visibility implications not shared by subgroups. Quickterm: groupe principal. Criteria: 1,2,4,7,8.</td> </tr> <tr> <td>Planner</td> <td>doc/user/permissions.md</td> <td>~50</td> <td>Yes</td> <td>Planificateur (Preferred)</td> <td>New default role (GitLab 17.7) positioned between Guest and Reporter. Quickterm translates it as Planificateur — but role names are typically kept untranslated in GitLab docs. Requires a clear decision. Criteria: 1,2,4,6,7,8.</td> </tr> <tr> <td>Security Manager</td> <td>doc/user/permissions.md</td> <td>~15</td> <td>No</td> <td></td> <td>New default role (GitLab 18.11) between Reporter and Developer. 'Manager' in FR is often left in English but responsable sécurité is also plausible. Must align with role ladder. Not in Quickterm. Criteria: 1,2,4,6,7,8.</td> </tr> <tr> <td>Minimal Access</td> <td>doc/user/permissions.md, doc/user/group/manage.md</td> <td>~30</td> <td>Yes</td> <td>accès minimum (Preferred)</td> <td>Special role granting only limited group visibility, below Guest. Non-billable (changed in 18.9). Quickterm: accès minimum — note 'minimum' not 'minimal'. Criteria: 1,2,3,4,7,8.</td> </tr> <tr> <td>custom role</td> <td>doc/user/custom_roles/_index.md, doc/user/permissions.md</td> <td>~50</td> <td>Yes</td> <td>rôle personnalisé (Preferred)</td> <td>User-defined role built on a base role with added permissions. Must be distinguished from default role and base role. Criteria: 1,2,3,4,7,8.</td> </tr> <tr> <td>base role</td> <td>doc/user/custom_roles/_index.md</td> <td>~8</td> <td>No</td> <td></td> <td>The default role a custom role extends. False friend: rôle de base — 'base' can suggest 'database' in FR technical contexts. Not in Quickterm. Criteria: 1,2,3,7.</td> </tr> <tr> <td>custom permission</td> <td>doc/user/custom_roles/_index.md</td> <td>~8</td> <td>No</td> <td></td> <td>An individual capability added on top of a base role (e.g. <code>read_code</code>, <code>admin_vulnerability</code>). Distinct from 'permissions' in the general role table sense. FR: autorisation personnalisée vs. permission personnalisée — must be uniform. Not in Quickterm. Criteria: 1,2,3,7,8.</td> </tr> <tr> <td>billable member</td> <td>doc/user/custom_roles/_index.md, doc/user/group/_index.md</td> <td>~35</td> <td>Partial (as billable user)</td> <td>utilisateur facturable (Preferred)</td> <td>A user consuming a seat in the subscription. Quickterm has <code>billable user</code> → utilisateur facturable; the 'member' form should follow the same pattern. Criteria: 1,2,4,7,8.</td> </tr> <tr> <td>seat</td> <td>doc/user/group/_index.md, doc/user/custom_roles/_index.md</td> <td>~55</td> <td>Yes</td> <td>siège (Preferred)</td> <td>One unit of subscription entitlement. Quickterm: siège. Translator must not use licence or poste. Criteria: 1,2,3,4,7,8.</td> </tr> <tr> <td>overage</td> <td>doc/user/group/manage.md</td> <td>~12</td> <td>No</td> <td></td> <td>Users/seats in excess of purchased subscription quantity; triggers billing consequences. No direct French cognate — dépassement is most accurate but surplus and excédent are alternatives that create inconsistency. Not in Quickterm. Criteria: 1,2,3,4,8.</td> </tr> <tr> <td>restricted access</td> <td>doc/user/group/manage.md, doc/user/group/access_and_permissions.md</td> <td>~22</td> <td>No</td> <td></td> <td>GitLab group setting that blocks adding new billable users when seat limit is reached. Confusable with general concept of restricting access by IP or domain. Not in Quickterm. Criteria: 1,2,3,4,7.</td> </tr> <tr> <td>user cap</td> <td>doc/user/group/manage.md</td> <td>~10</td> <td>No</td> <td></td> <td>Numeric ceiling on billable users, triggering a pending-member approval flow. Distinct from 'restricted access' (toggle) and subscription seat limit (quantity). FR: limite d'utilisateurs vs. plafond d'utilisateurs. Not in Quickterm. Criteria: 1,2,3,7.</td> </tr> <tr> <td>quarterly reconciliation</td> <td>doc/user/group/manage.md</td> <td>~4</td> <td>No</td> <td></td> <td>GitLab billing process in which seat overages are calculated and billed each quarter. Not just 'quarterly review' — it has financial consequences. FR: réconciliation trimestrielle vs. more idiomatic régularisation trimestrielle. Not in Quickterm. Criteria: 1,2,3,7,8.</td> </tr> <tr> <td>direct member</td> <td>doc/user/members/_index.md, doc/user/project/members/sharing_projects_groups.md</td> <td>~20</td> <td>No</td> <td></td> <td>User explicitly added to a group/project (as opposed to inherited). Four-way taxonomy: direct / inherited / shared / inherited shared. FR: membre direct — must be strictly consistent with inherited member. Criteria: 1,2,4,7,8.</td> </tr> <tr> <td>inherited member</td> <td>doc/user/members/_index.md, doc/user/project/members/sharing_projects_groups.md</td> <td>~15</td> <td>No</td> <td></td> <td>User with access because they belong to a parent group. 'Inherited' in membership context — FR membre hérité; translator may use transmis or délégué without guidance. Criteria: 1,2,4,7,8.</td> </tr> <tr> <td>shared project</td> <td>doc/user/project/members/sharing_projects_groups.md</td> <td>~12</td> <td>No</td> <td></td> <td>A project that has invited a group as a member. Not 'a public project.' FR: projet partagé blurs the distinction between group-invited and publicly available. Criteria: 1,2,4,7.</td> </tr> <tr> <td>shared group</td> <td>doc/user/project/members/sharing_projects_groups.md</td> <td>~10</td> <td>No</td> <td></td> <td>A group invited to another group; members of the source group get access. Parallel to shared project. Same FR disambiguation risk. Criteria: 1,2,4,7.</td> </tr> <tr> <td>group membership lock</td> <td>doc/user/group/access_and_permissions.md, doc/user/members/_index.md</td> <td>~5</td> <td>No</td> <td></td> <td>Setting preventing new members from being added to projects within a group. 'Lock' in a membership context is domain-specific. FR: verrouillage d'appartenance vs. verrouillage des membres. Criteria: 1,2,3,7.</td> </tr> <tr> <td>direct transfer</td> <td>doc/user/group/import/_index.md</td> <td>~15</td> <td>No</td> <td></td> <td>GitLab-to-GitLab migration method using a direct API connection (vs. file export/import). Named feature. FR: transfert direct — 'migration directe' may tempt translators. Not in Quickterm. Criteria: 1,2,3,4,7.</td> </tr> <tr> <td>placeholder user</td> <td>doc/user/group/import/_index.md</td> <td>~4</td> <td>Yes (no FR)</td> <td></td> <td>Temporary account created during import for contribution mapping. Entry in Quickterm but FR empty. FR candidates: utilisateur fictif, espace réservé — no established form. Criteria: 1,2,3,6,7.</td> </tr> <tr> <td>enterprise user</td> <td>doc/user/group/manage.md</td> <td>~6</td> <td>No</td> <td></td> <td>User whose account is owned/managed by an enterprise via domain-linked groups; subject to specific restrictions. FR: utilisateur entreprise vs. utilisateur d'entreprise — 'enterprise' often left untranslated in FR IT. Criteria: 1,2,3,6,7.</td> </tr> <tr> <td>pending deletion</td> <td>doc/user/group/_index.md, doc/user/group/manage.md</td> <td>~8</td> <td>No</td> <td></td> <td>State of a group/project after deletion is initiated but before the grace period expires. Not 'pending' in the general sense. FR word order: suppression en attente vs. en attente de suppression — must be standardized. Criteria: 1,2,4,7.</td> </tr> <tr> <td>access expiration date</td> <td>doc/user/group/_index.md, doc/user/members/_index.md</td> <td>~10</td> <td>No</td> <td></td> <td>Date on which a member's access automatically ends. FR: date d'expiration d'accès vs. date d'expiration de l'accès — minor but appears in UI strings and tables; must be consistent. Criteria: 1,2,4,7.</td> </tr> <tr> <td>visibility level</td> <td>doc/user/group/_index.md, doc/user/group/access_and_permissions.md, doc/user/permissions.md</td> <td>~15</td> <td>No</td> <td></td> <td>Public/internal/private access classification. 'Level' here is a discrete enum (not a degree). FR: niveau de visibilité must not be confused with paramètre de visibilité. The three values (public/interne/privé) must also be rendered consistently. Criteria: 1,2,4,7,8.</td> </tr> <tr> <td>service account</td> <td>doc/user/group/access_and_permissions.md, doc/user/custom_roles/_index.md</td> <td>~6</td> <td>Yes</td> <td>compte de service (Preferred)</td> <td>Non-human user account for automation. FR confirmed by Quickterm. Criteria: 1,2,3,7.</td> </tr> <tr> <td>rate limit</td> <td>doc/user/group/_index.md, doc/user/group/manage.md</td> <td>~25</td> <td>Yes</td> <td>limite de débit (Preferred)</td> <td>Max requests per time window. Quickterm: limite de débit. In GitLab FR strings, limite de taux also appears — consistency risk. Criteria: 1,2,4,8.</td> </tr> </table> #### Terms excluded after applying extraction criteria - `namespace` — already in #923 - `subgroup` — already in #923; sous-groupe is transparent in FR - `role (standalone)` — too generic; proper-noun role names (Guest, Developer, etc.) are UI labels, not TBX candidates - `access level` — UI label equivalent to 'role'; redundant - `contribution calendar` — calendrier des contributions is natural and unambiguous - `dormant project` — projet inactif is unambiguous - `commit email` — removed: e-mail de commit is derivable; low specialization score - `group sync` — removed: synchronisation de groupe is derivable; removed after 8-criteria re-evaluation - `LDAP, SAML, OAuth, SCIM` — third-party protocol names - `Owner, Maintainer, Developer, Reporter, Guest` — proper-noun role names — UI labels, must stay untranslated, not TBX candidates #### Review checklist  - [ ] top-level group - [ ] Planner - [ ] Security Manager - [ ] Minimal Access - [ ] custom role - [ ] base role - [ ] custom permission - [ ] billable member - [ ] seat - [ ] overage - [ ] restricted access - [ ] user cap - [ ] quarterly reconciliation - [ ] direct member - [ ] inherited member - [ ] shared project - [ ] shared group - [ ] group membership lock - [ ] direct transfer - [ ] placeholder user - [ ] enterprise user - [ ] pending deletion - [ ] access expiration date - [ ] visibility level - [ ] service account - [ ] rate limit

issue