Issue Summary

Currently, the section Workspace permissions contains information that only applies to Legacy workspaces. This should be updated to avoid confusion with UUM workspaces

Provide groups with the permissions they need to collaborate across the workspace. These permissions apply to all projects and repositories in this workspace.

When you add a group at the Workspace Level, if the Workspace is UUM, this group won't propagate to all the repositories and projects. It will only give users access to the workspace but not to the repositories. 

With UUM, users and groups should be assigned permissions based on specific projects, aligning with the necessary access levels. This new structure enables more precise and granular management of user permissions at the project level instead of the workspace level, allowing for a more efficient and practical approach to permission allocation and role assignment.

Expected Results

Clarify that the behavior will be different in Legacy and UUM.

Actual Results

The text implies that adding a group there will propagate it to all the repositories and projects without specifying that it only applies to Legacy Workspaces.