Commit 33b12c7b authored by Sid Sijbrandij's avatar Sid Sijbrandij Committed by Evan Read

Workspace update

parent a33da2cc
...@@ -11,15 +11,10 @@ Workspace will be above the [top-level namespaces](../group/index.md#namespaces) ...@@ -11,15 +11,10 @@ Workspace will be above the [top-level namespaces](../group/index.md#namespaces)
- Defining and applying settings to all of your groups, subgroups, and projects. - Defining and applying settings to all of your groups, subgroups, and projects.
- Aggregating data from all your groups, subgroups, and projects. - Aggregating data from all your groups, subgroups, and projects.
The functionality in the [Admin Area](../admin_area/index.md) of self-managed installations will be split up and go to:
1. Groups (available in the Workspace, Top-level group namespaces, and Sub-groups)
1. Hardware Controls (for functionality that does not apply to groups)
Our goal is to reach feature parity between SaaS and Self-Managed installations, with all [Admin Area settings](/ee/user/admin_area/settings/) moving to either: Our goal is to reach feature parity between SaaS and Self-Managed installations, with all [Admin Area settings](/ee/user/admin_area/settings/) moving to either:
- Workspace (contains features relevant to both GitLab-managed and self-managed installations) with a dedicated Settings menu available within the left navigation bar. 1. Groups (available in the Workspace, Top-level group namespaces, and Sub-groups)
- Hardware controls (only contains features relative to Self-Managed installations, with one per installation). 1. Hardware Controls (for functionality that does not apply to Groups, Hardware Controls are only applicable to Self-managed Installations, there is one Hardware Controls section per installation)
NOTE: NOTE:
Workspace is currently in development. Workspace is currently in development.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment