Feature Request

In our Document360 project, we have several workspaces. Maintaining the different workspaces and related site customizations is quite cumbersome. • Each workspace has its own ‘Home’ site, which can be turned off. • One workspace is the ‘main’ workspace. • Each workspace has its own ‘Site header & footer’ settings. • etc. Issues: This setup causes several issues. For example: • Set up ‘Site header & footer’ separately for each workspace. Running the risk of inconsistencies. • Breadcrumbs are not project based (generic). o Breadcrumb ‘Home’ icon leads to the workspace ‘Home’ instead of a project ‘Home’. o When workspace ‘Home’ is switch off, no home icon is shown in breadcrumbs, breaking the navigation. o There’s a ‘Documentation’ part in the breadcrumbs, that should show the workspace name. Solution: To solve this, an architectural change is required for the Document360 platform. The solution for this would be to introduce a project ‘Home’. Benefits would, for example, be: • One site setup (headers, footers, etc.) that can be inherited by the project workspaces. (You can still keep the workspace-specific site setup, but make it by default inherit the project site setup) • Project-based breadcrumbs: o ‘Home’ icon always can be shown and navigates to the project Home. o Workspace names can be shown in the breadcrumbs. • Improved ‘workspace’ switch in the published sites. • More flexibility (less restrictions) in the documentation web site setup. • No need to mark one workspace as ‘Main’, with all related technical consequences and limitations.

As admins, we would like a dashboard or console within the platform to view the entirety of our environment's configurations, including the site map (Categories, Sub-Cats, Articles, Titles, Slugs Descriptions, Related Articles, Default Drive), metadata (Labels, Tags, Glossary usage), workflow status if applicable, and permissions (user names, roles, profiles etc across all levels) so that we can easily audit or review across all aspects of our environment instead of browsing into different areas of the back-end. This dashboard would also offer the ability to export configs as a CSV or Excel.

The customer has multiple active workspaces and would like the workspace search to function as a dedicated search that retrieves results only from the specific workspace being used. However, they also prefer to maintain a global homepage where the search functionality is global, pulling results from all workspaces.