Espaços de trabalho¶
Workspaces group related translation projects. They sit above projects and provide a shared place for project listings, workspace-scoped access control, and billing details when the billing module is enabled.
Workspace membership does not grant access to translate or manage projects in the workspace. Project access is still controlled by the project access control settings and project teams, see Controlo de acesso ao projeto.
The workspace page lists projects in that workspace that you can access.
You can list all workspaces in the management interface at Manage ↓ Workspaces.
Project creation and moves¶
Projects can be created with or without a workspace:
Creating a project in a workspace requires the Add projects to workspace permission for that workspace.
Creating a project without a workspace requires the site-wide Add new projects permission.
When creating a project with the API REST do Weblate, pass the workspace UUID in the
workspace field.
Projetos existentes podem ser movidos entre espaços de trabalho a partir da aba do projeto Organizar ou ao mudar o campo workspace com o API REST do Weblate. Mover um projeto requer permissão para editar o projeto e a permissão Editar definições de espaço de trabalho para o espaço de trabalho fonte e alvo. O espaço de trabalho alvo também requer a permissão. Adicionar projetos ao espaço de trabalho. Mover um projeto para fora de um espaço de trabalho também requer a permissão no site inteiro Adicionar novos projetos.
Workspace settings¶
Workspace settings define workspace identity and defaults inherited by projects and components.
Nome do espaço de trabalho.¶
Verbose workspace name used in workspace listings and project organization.
Use workspace translation memory¶
Whether projects in this workspace can use translation memory shared within the workspace. Individual projects also have to enable workspace translation memory.
Contribute to workspace translation memory¶
Whether projects in this workspace can contribute translations to the workspace translation memory. Individual projects also have to enable contribution.
Licença da tradução¶
Default translation license for projects and components in this workspace.
Veja também
Contrato de licença do colaborador¶
Default contributor license agreement for projects and components in this workspace. Markdown can be used for text formatting or inserting links.
Adicionar nova tradução¶
Default behavior for requests to create new translations in projects and components in this workspace.
Veja também
Estilo de código de idioma¶
Default language code style for translations created by Weblate in projects and components in this workspace.
Veja também
Idioma secundário¶
Default secondary language to show together with the source language while translating projects and components in this workspace.
Veja também
Marcadores de tradução¶
Workspace-level translation flags. These are merged with project, component, and translation flags instead of being inherited as a replacement.
Mensagens de commit, add, merge, extensão e merge request¶
Default commit and merge request message templates for projects and components in this workspace. These templates use the same markup as component message settings.
The built-in defaults follow Conventional Commits and include Weblate links where available. Use Restore site default next to a message editor to restore the current installation default for that message.
Settings inheritance¶
Settings inheritance lets common defaults be configured once and reused in lower scopes:
Workspaces define defaults for projects in the workspace.
Projects define defaults for categories and components in the project.
Categories define defaults for nested categories and components in the category.
Components use the effective value from the nearest inherited scope unless inheritance is disabled for that setting.
This is available for translation license, contributor license agreement, adding new translations, language code style, secondary language, and commit message templates.
Project, category, and component settings expose Inherit from workspace, Inherit from project, or Inherit from category checkboxes for these values. When inheritance is enabled, the inherited value is shown in the settings form; disable inheritance and save to edit the stored override value.
Translation flags are handled differently. Workspace, project, category, component, and translation flags are merged, so each level can add flags without replacing the lower levels.
When a workspace is created, these defaults are copied from the current installation defaults. Later changes to installation defaults do not update existing workspaces.
Workspace-less projects also store their own defaults when created and do not inherit from a workspace unless moved into one and configured to inherit.
Ao atualizar instalações existentes, o Weblate consolida configurações correspondentes: se todos os componentes em um projeto usam o mesmo valor, o valor é movido para o projeto e para os componentes que o herdam. A mesma consolidação é aplicada a partir de projetos e espaços de trabalho. Definições de categoria são inicializadas para herdar do seu parente e as substituições explícitas correspondentes dos elementos filhos podem ser consolidadas na categoria. Valores diferentes permanecem configurados diretamente no escopo inferior.
Controlo de acesso ao espaço de trabalho¶
Workspaces have workspace-scoped teams. These teams control workspace-level actions only; they do not grant translation access to the projects in the workspace.
The default workspace teams are:
- Owners
Can edit workspace settings, add projects to the workspace, manage workspace access, and view or pay billing plans assigned to the workspace.
- Criadores do projeto
Can add projects to the workspace.
Users can still view a workspace page when they can access at least one project in that workspace. This does not grant billing access or permission to add more projects.
Faturação¶
When Faturação is enabled, a billing plan is assigned to a workspace. Projects in that workspace count against the workspace billing plan.
Users with Edit workspace settings permission can view and pay the billing plan. Billing notification e-mails are sent to these users.
Billing is optional. Workspaces are still available when the billing module is not installed.
Upgrading from billing owners¶
Older Weblate versions stored billing owners directly on billing plans. These users are migrated to the workspace Owners team for the workspace covered by the billing plan.