# Workspaces 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 [プロジェクトのアクセス制御](https://docs.weblate.org/ja/latest/admin/access.md#acl). The workspace page lists projects in that workspace that you can access.  Signed-in users can also review grouped project and component findings on the workspace Diagnostics tab. See [Project and workspace diagnostics overviews](https://docs.weblate.org/ja/latest/devel/alerts.md#diagnostics-overviews). Signed-in users can open Projects ↓ My workspaces to list workspaces where they have an explicit workspace-team assignment. This list does not include workspaces merely because the user has site-wide management access. Site managers can list all workspaces in the management interface at Manage ↓ Workspaces.  Workspace statistics aggregate all owned and shared content, including projects and restricted components that you cannot access. Project listings and actions remain permission-filtered. See [statistics access filtering](https://docs.weblate.org/ja/latest/admin/access.md#statistics-access-filtering). The workspace Files menu downloads a ZIP archive of owned components that you can access and have permission to download. Workspace membership does not bypass project access control or component restrictions. The menu also provides Upload translation guidance. Uploading at workspace level is not supported; select a project and open an individual translation to upload a file. Users who can edit translations in an accessible project can choose Operations ↓ Search and replace to replace text across permission-filtered owned project content in the workspace. The existing [検索と置換](https://docs.weblate.org/ja/latest/user/translating.md#search-replace) preview and confirmation workflow applies. ## Workspace removal Users with the Edit workspace settings permission can remove a workspace from Operations ↓ Organize or remove. Only empty workspaces can be removed. Move or remove all projects in the workspace first. Workspaces associated with billing cannot be removed. ## 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 [Weblate の REST API](https://docs.weblate.org/ja/latest/api.md#api), pass the workspace UUID in the `workspace` field. Existing projects can be moved between workspaces from the project Organize tab or by changing the `workspace` field with the [Weblate の REST API](https://docs.weblate.org/ja/latest/api.md#api). Moving a project requires permission to edit the project and the Edit workspace settings permission for the source and target workspace. The target workspace also requires the Add projects to workspace permission. Moving a project out of a workspace also requires the site-wide Add new projects permission. ## Workspace settings Workspace settings define workspace identity and defaults inherited by projects and components. ### Workspace name 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. Users with permission to edit the workspace can open Operations ↓ Translation memory to browse, download, delete, or rebuild automatically created workspace translation-memory entries. See [ユーザー インターフェイス](https://docs.weblate.org/ja/latest/admin/memory.md#memory-user). ### 翻訳のライセンス Default translation license for projects and components in this workspace. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [翻訳のライセンス](https://docs.weblate.org/ja/latest/admin/projects.md#component-license) ### 貢献者ライセンス同意書 Default contributor license agreement for projects and components in this workspace. Markdown can be used for text formatting or inserting links. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [貢献者ライセンス同意書](https://docs.weblate.org/ja/latest/admin/projects.md#component-agreement) ### 新しい翻訳の追加 Default behavior for requests to create new translations in projects and components in this workspace. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [新しい翻訳の追加](https://docs.weblate.org/ja/latest/admin/projects.md#component-new-lang) ### 言語コード スタイル Default language code style for translations created by Weblate in projects and components in this workspace. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [言語コード スタイル](https://docs.weblate.org/ja/latest/admin/projects.md#component-language-code-style) ### 第二言語 Default secondary language to show together with the source language while translating projects and components in this workspace. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [第二言語](https://docs.weblate.org/ja/latest/user/profile.md#secondary-languages) * [第二言語](https://docs.weblate.org/ja/latest/admin/projects.md#component-secondary-language) ### 翻訳フラグ Workspace-level translation flags. These are merged with project, component, and translation flags instead of being inherited as a replacement. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [フラグを使用した動作の設定](https://docs.weblate.org/ja/latest/admin/checks.md#custom-checks) ### コミット、追加、削除、マージ、アドオン、およびマージ リクエストのメッセージ 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. #### SEE ALSO * [Settings inheritance](#workspace-inherited-settings) * [テンプレート用のマークアップ](https://docs.weblate.org/ja/latest/admin/projects.md#markup) * [コミット、追加、削除、マージ、アドオン、およびマージ リクエストのメッセージ](https://docs.weblate.org/ja/latest/admin/projects.md#component-commit-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, enforced checks, 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. When upgrading existing installations, Weblate consolidates matching settings: if all components in a project use the same value, the value is moved to the project and those components inherit it. The same consolidation is then applied from projects to workspaces. Category settings are initialized to inherit from their parent and matching explicit child overrides can be consolidated to the category. Differing values remain configured directly on the lower scope. #### SEE ALSO * [Workspace settings](#workspace-settings) * [プロジェクトの設定](https://docs.weblate.org/ja/latest/admin/projects.md#project) * [コンポーネント構成](https://docs.weblate.org/ja/latest/admin/projects.md#component) ## ワークスペースのアクセス制御 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. プロジェクトの作成者 : 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. ## 課金 When [課金](https://docs.weblate.org/ja/latest/admin/optionals.md#billing) 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. #### SEE ALSO * [翻訳プロジェクトとコンポーネントの追加](https://docs.weblate.org/ja/latest/admin/projects.md#adding-projects) * [アクセス制御](https://docs.weblate.org/ja/latest/admin/access.md#access-control) * [課金](https://docs.weblate.org/ja/latest/admin/optionals.md#billing) * [Weblate の REST API](https://docs.weblate.org/ja/latest/api.md#api)