wandb · mdlinville · Jun 22, 2026 · Jun 12, 2026 · Jun 12, 2026 · Jun 12, 2026
@@ -54,10 +54,6 @@ Pour définir la portée de visibilité d’un nouveau projet :
 
 3. Après avoir sélectionné l’équipe parente et saisi le nom du projet, sélectionnez la portée souhaitée dans le menu déroulant **Project Visibility**.
 
-   <Frame>
-     <img src="/images/hosting/restricted_project_add_new.gif" alt="Création d’un projet restreint" />
-   </Frame>
-
    Effectuez l’étape suivante si vous sélectionnez la visibilité **Restricted**.
 
 4. Saisissez le nom d’un ou plusieurs membres de l’équipe W&amp;B dans le champ **Inviter des membres de l’équipe**. Ajoutez uniquement les membres indispensables à la collaboration sur le projet, car les autres membres de l’équipe n’ont pas automatiquement accès à un projet restreint.
@@ -86,10 +82,6 @@ Pour modifier la portée de visibilité d’un projet existant :
 
 4. Dans le menu déroulant **Project Visibility**, sélectionnez la portée souhaitée.
 
-   <Frame>
-     <img src="/images/hosting/restricted_project_edit.gif" alt="Modification des paramètres d’un projet restreint" />
-   </Frame>
-
    Effectuez l’étape suivante si vous sélectionnez la visibilité **Restricted**.
 
 5. Accédez à l’onglet **Users** du projet, puis cliquez sur le bouton **Add user** pour inviter des utilisateurs précis au projet restreint.
@@ -149,4 +141,4 @@ Gardez les comportements suivants à l’esprit lorsque vous attribuez ou modifi
 * Vous ne **pouvez pas** modifier le rôle au niveau du projet d’un utilisateur qui a le rôle *lecture seule* au niveau de l’équipe.
 * Si le rôle au niveau du projet d’un utilisateur dans un projet donné **est identique à** son rôle au niveau de l’équipe, et qu’un administrateur de l’équipe modifie ensuite le rôle au niveau de l’équipe, W&amp;B modifie automatiquement le rôle de projet correspondant pour l’aligner sur le rôle au niveau de l’équipe.
 * Si vous modifiez le rôle au niveau du projet d’un utilisateur dans un projet donné de sorte qu’il **diffère de** son rôle au niveau de l’équipe, et qu’un administrateur de l’équipe modifie ensuite le rôle au niveau de l’équipe, le rôle correspondant au niveau du projet reste inchangé.
-* Si vous retirez un utilisateur d’un projet *Restricted* alors que son rôle au niveau du projet différait de son rôle au niveau de l’équipe, puis que vous l’ajoutez de nouveau au projet plus tard, il hérite du rôle au niveau de l’équipe en raison du comportement par défaut. Si nécessaire, modifiez de nouveau le rôle au niveau du projet afin qu’il diffère du rôle au niveau de l’équipe.
+* Si vous retirez un utilisateur d’un projet *Restricted* alors que son rôle au niveau du projet différait de son rôle au niveau de l’équipe, puis que vous l’ajoutez de nouveau au projet plus tard, il hérite du rôle au niveau de l’équipe en raison du comportement par défaut. Si nécessaire, modifiez de nouveau le rôle au niveau du projet afin qu’il diffère du rôle au niveau de l’équipe.
@@ -54,10 +54,6 @@ W&amp;B チーム内の任意のprojectのアクセスレベルは、2 つの設
 
 3. 親チームを選択し、プロジェクトの名を入力したら、**Project Visibility** ドロップダウンから目的の公開範囲を選択します。
 
-   <Frame>
-     <img src="/images/hosting/restricted_project_add_new.gif" alt="制限付きプロジェクトを作成する" />
-   </Frame>
-
    **Restricted** の公開範囲を選択した場合は、次の step を実行します。
 
 4. **Invite team members** フィールドに、1人以上のW&amp;Bチームメンバーの名を入力します。制限付きプロジェクトには他のチームメンバーが暗黙的にアクセスできないため、プロジェクトでの共同作業に必要なメンバーのみを追加してください。
@@ -86,10 +82,6 @@ W&amp;B は、選択した公開範囲で project を作成し、招待された
 
 4. **Project Visibility** ドロップダウンから、希望する公開範囲を選択します。
 
-   <Frame>
-     <img src="/images/hosting/restricted_project_edit.gif" alt="制限付きプロジェクト設定を編集している画面" />
-   </Frame>
-
    **Restricted** の公開範囲を選択した場合は、次の step を完了してください。
 
 5. プロジェクトの **Users** タブにアクセスし、**Add user** ボタンをクリックして、特定のユーザーを制限付きプロジェクトに招待します。
@@ -149,4 +141,4 @@ project の可視性スコープを設定した後、プロジェクトレベル
 * チームレベルで *View-Only* ロールを持つユーザーのプロジェクトレベルのロールは**変更できません**。
 * 特定の project 内のユーザーのプロジェクトレベルのロールがチームレベルのロールと**同じである**場合、その後 Team Admin がチームレベルのロールを変更すると、W&amp;B は自動的に該当する project ロールも変更し、チームレベルのロールをトラッキングします。
 * 特定の project 内のユーザーのプロジェクトレベルのロールをチームレベルのロールと**異なる状態に**変更した場合、その後 Team Admin がチームレベルのロールを変更しても、該当するプロジェクトレベルのロールはそのまま維持されます。
-* *Restricted* project で、ユーザーのプロジェクトレベルのロールがチームレベルのロールと異なる状態のままそのユーザーを削除し、その後そのユーザーを再度 project に追加すると、デフォルトの動作によりチームレベルのロールを継承します。必要に応じて、プロジェクトレベルのロールがチームレベルのロールと異なるように再度変更してください。
+* *Restricted* project で、ユーザーのプロジェクトレベルのロールがチームレベルのロールと異なる状態のままそのユーザーを削除し、その後そのユーザーを再度 project に追加すると、デフォルトの動作によりチームレベルのロールを継承します。必要に応じて、プロジェクトレベルのロールがチームレベルのロールと異なるように再度変更してください。
@@ -54,10 +54,6 @@ W&amp;B 프로젝트의 범위를 정의하여 누가 해당 프로젝트의 W&a
 
 3. 상위 팀을 선택하고 프로젝트 이름을 입력한 후 **Project Visibility** 드롭다운에서 원하는 범위를 선택합니다.
 
-   <Frame>
-     <img src="/images/hosting/restricted_project_add_new.gif" alt="제한된 프로젝트 생성" />
-   </Frame>
-
    **Restricted** 가시성을 선택한 경우에만 다음 step을 완료합니다.
 
 4. **Invite team members** 필드에 W&amp;B 팀 구성원 한 명 이상의 이름을 입력합니다. 제한된 프로젝트에서는 다른 팀 구성원에게 암묵적으로 액세스 권한이 부여되지 않으므로, 프로젝트 협업에 꼭 필요한 구성원만 추가합니다.
@@ -86,10 +82,6 @@ W&amp;B는 선택한 가시성 범위로 프로젝트를 생성하며, 초대된
 
 4. **Project Visibility** 드롭다운에서 원하는 범위를 선택합니다.
 
-   <Frame>
-     <img src="/images/hosting/restricted_project_edit.gif" alt="제한된 프로젝트 설정 편집" />
-   </Frame>
-
    **Restricted** 가시성을 선택한 경우 다음 step을 완료합니다.
 
 5. 프로젝트의 **Users** 탭으로 이동한 다음, **Add user** 버튼을 클릭해 특정 사용자를 제한된 프로젝트에 초대합니다.
@@ -149,4 +141,4 @@ W&amp;B는 프로젝트의 가시성 범위를 업데이트하며, 액세스 권
 * 팀 수준에서 *View-Only* 역할을 가진 사용자의 프로젝트 수준 역할은 **변경할 수 없습니다**.
 * 특정 프로젝트에서 사용자의 프로젝트 수준 역할이 팀 수준 역할과 **같은 경우**, 나중에 팀 관리자가 팀 수준 역할을 변경하면 W&amp;B가 해당 프로젝트 역할도 팀 수준 역할을 따르도록 자동으로 변경합니다.
 * 특정 프로젝트에서 사용자의 프로젝트 수준 역할을 팀 수준 역할과 **다르게** 변경한 경우, 나중에 팀 관리자가 팀 수준 역할을 변경해도 해당 프로젝트 수준 역할은 그대로 유지됩니다.
-* 사용자의 프로젝트 수준 역할이 팀 수준 역할과 달랐던 상태에서 해당 사용자를 *Restricted* 프로젝트에서 제거한 후 나중에 다시 프로젝트에 추가하면, 기본 동작에 따라 팀 수준 역할을 상속합니다. 필요한 경우 프로젝트 수준 역할을 다시 변경해 팀 수준 역할과 다르게 설정하세요.
+* 사용자의 프로젝트 수준 역할이 팀 수준 역할과 달랐던 상태에서 해당 사용자를 *Restricted* 프로젝트에서 제거한 후 나중에 다시 프로젝트에 추가하면, 기본 동작에 따라 팀 수준 역할을 상속합니다. 필요한 경우 프로젝트 수준 역할을 다시 변경해 팀 수준 역할과 다르게 설정하세요.
@@ -4,6 +4,8 @@ title: Manage access control for projects
 keywords: ["project visibility", "restricted project", "project roles", "project permissions"]
 ---
 
+import ProjectVisibilityScopesTable from "/snippets/_includes/project-visibility-scopes-table.mdx";
+
 Define the scope of a W&B project to limit who can view, edit, and submit W&B runs to it. This page is for team and organization admins, and project owners, who need to control access to sensitive workflows or limit collaboration to a specific group of users.
 
 You can combine two controls to configure the access level for any project within a W&B team. **Visibility scope** is the higher-level mechanism. Use it to control which groups of users can view or submit runs in a project. For a project with _Team_ or _Restricted_ visibility scope, you can then use **Project level roles** to control the level of access that each user has within the project.
@@ -17,12 +19,7 @@ The owner of a project, a team admin, or an organization admin can set or edit a
 Visibility scope determines which users in your organization can see and contribute to a project. You can choose from four project visibility scopes. From most public to most private, they are:
 
 
-| Scope | Description | 
-| ----- | ----- |
-| Open |Anyone who knows about the project can view it and submit runs or reports.|
-| Public |Anyone who knows about the project can view it. Only your team can submit runs or reports.|
-| Team | Only members of the parent team can view the project and submit runs or reports. Anyone outside the team can't access the project. |
-| Restricted| Only invited members from the parent team can view the project and submit runs or reports.|
+<ProjectVisibilityScopesTable />
 
 
 <Note>
@@ -47,9 +44,6 @@ To set the visibility scope for a new project:
 1. Navigate to your W&B organization on a W&B Multi-tenant Cloud, Dedicated Cloud, or Self-Managed instance.
 2. Click the **Create a new project** button in the left-hand sidebar's **My projects** section. Alternatively, navigate to the **Projects** tab of your team and click the **Create new project** button in the upper right-hand corner.
 3. After you select the parent team and enter the name of the project, select the desired scope from the **Project Visibility** dropdown.
-   <Frame>
-       <img src="/images/hosting/restricted_project_add_new.gif" alt="Creating restricted project"  />
-   </Frame>
 
    Complete the following step if you select **Restricted** visibility.
 
@@ -69,21 +63,19 @@ W&B creates the project with the selected visibility scope, and only the invited
 To change the visibility scope of an existing project:
 
 1. Navigate to your W&B project.
-2. Select the **Overview** tab on the left column.
-3. Click the **Edit Project Details** button on the upper right corner.
-4. From the **Project Visibility** dropdown, select the desired scope.
-   <Frame>
-       <img src="/images/hosting/restricted_project_edit.gif" alt="Editing restricted project settings"  />
-   </Frame>
-
-   Complete the following step if you select **Restricted** visibility.
+2. From the top of any project page, click the icon next to the project name to edit the project's visibility. The icon reflects the current visibility scope: **Open**, **Public**, **Team**, or **Restricted**. See [Visibility scopes](#visibility-scopes).
+3. From the **Project Visibility** dropdown, select the desired scope, then click **Save**.
 
-5. Navigate to the **Users** tab in the project, and click the **Add user** button to invite specific users to the restricted project.
+    <Important>If you select **Restricted** visibility, you must complete the next step.</Important>
 
-W&B updates the project's visibility scope, and access reflects the new scope along with any invited members.
+    W&B updates the project's visibility scope, and access reflects the new scope.
+4. To share a restricted project:
+    1. Click **Project** in the left navigation to open the project **Overview** page.
+    2. Select the **Users** tab.
+    3. Click **Add user** and select one or more specific users to invite them to the project.
 
 <Warning>
-* All members of a team lose access to a project if you change its visibility scope from **Team** to **Restricted**, unless you invite the required team members to the project.
+* All members of a team lose access to a project if you change its visibility scope from **Team** to **Restricted**, and you must invite team members to give them access.
 * All members of a team get access to a project if you change its visibility scope from **Restricted** to **Team**.
 * If you remove a team member from the user list for a restricted project, they lose access to that project.
 </Warning>
@@ -110,7 +102,7 @@ Project level roles are in preview on W&B Multi-tenant Cloud, Dedicated Cloud, a
 To assign a project level role:
 
 1. Navigate to your W&B project.
-2. Select the **Overview** tab on the left column.
+2. In the project sidebar, click **Project**.
 3. Navigate to the **Users** tab in the project.
 4. Click the currently assigned role for the relevant user in the **Project Role** field, which opens a dropdown listing the other available roles.
 5. Select another role from the dropdown. The change saves instantly.

@@ -74,14 +74,17 @@ products:
   - slug: weave
     display_name: "W&B Weave"
     allowed_keywords:
+      - Agents
       - Client Info
       - Code Capture
       - Data Capture
       - Evaluation
       - Performance
       - System Info
       - Trace Data
+      - Tracing
       - UI Rendering
+      - weave.op
 
   - slug: inference
     display_name: "Serverless Inference"

@@ -0,0 +1,6 @@
+| Scope | Icon | Description |
+| ----- | ---- | ----------- |
+| Open | <Icon icon="globe" iconType="solid" /> | Anyone who knows about the project can view it and submit runs or reports. |
+| Public | <Icon icon="lock-open" iconType="solid" /> | Anyone who knows about the project can view it. Only your team can submit runs or reports. |
+| Team | <Icon icon="users" iconType="solid" /> | Only members of the parent team can view the project and submit runs or reports. Anyone outside the team can't access the project. |
+| Restricted | <Icon icon="lock" iconType="solid" /> | Only invited members from the parent team can view the project and submit runs or reports. |
@@ -1,15 +1,18 @@
-1. In the W&B App, from any page in the project, click **Overview** in the left navigation.
-1. At the top right, click **Edit**.
-1. Choose a new value for **Project visibility**:
+import ProjectVisibilityScopesTable from "/snippets/_includes/project-visibility-scopes-table.mdx";
 
-    - **Team** (default): Only your team can view and edit the project.
-    - **Restricted**: Only invited members can access the project, and public access is turned off.
-    - **Open**: Anyone can submit runs or create reports, but only your team can edit it. Use this only for short-lived projects such as classroom settings or public benchmark competitions.
-    - **Public**: Anyone can view the project, but only your team can edit it.
+1. Navigate to your W&B project.
+2. From the top of any project page, click the icon next to the project name to edit the project's visibility. The icon reflects the current visibility scope: **Open**, **Public**, **Team**, or **Restricted**. See [Visibility scopes](#visibility-scopes).
+3. From the **Project Visibility** dropdown, select the desired scope, then click **Save**.
+
+    <ProjectVisibilityScopesTable />
+
+    <Note>
+    **Edit** allows a user to submit runs or create reports in the project.
+    </Note>
 
         <Note>
-        If your W&B organization's admins have turned off **Public** visibility, you can't choose it. Instead, you can share a view-only [W&B Report](/models/reports/collaborate-on-reports#share-a-report), or contact your W&B organization's admins for assistance.
+        If your W&B organization admins have turned off **Public** visibility for the organization, you cannot choose it. Instead, you can share a view-only [W&B Report](/models/reports/collaborate-on-reports#share-a-report), or contact your W&B organization's admins for assistance.
         </Note>
 1. Click **Save**.
-
-If you update a project to a stricter privacy setting, you might need to re-invite individual users to restore their access to the project.
+    
+If you update a project to a stricter privacy setting, you may need to re-invite individual users to restore their access.