Courtesy Translation
Click-DummySharePoint reimagined

Bertelsmann T-HUB

One frontendthat organizesprojects, data,and approvals.

The new T-HUB translates the existing SharePoint logic into a more modern, faster, and more controllable workspace. Instead of forcing teams to work around technical limits, the interface is organized around processes, visibility, and the reality of files, including large media, external approvals, and protected areas.

240+

Client workspaces

4

Clear zones

1

One interface

T-HUB overview visual

Example state in the new hub

Client 1 - Project package issue 04/2026

Media-heavy, yet manageable

Active layers

Internal assets
Customer approvals
Live project status
Governance SnapshotControl surface

Approvals, routing, and roles on a clearer visual surface

The right-hand surface stays calm, but now brings the relevant control points into view much earlier.

internal / client separated

Storage route

internal / client separated

Approvals

7 open / 2 critical

Role model

inherited + controlled overrides

Hub overview

From overview directly into the operational space

The start page condenses the new T-HUB into a few clear entry points. Operational work, setup, and permission management intentionally live on their own subpages.

01

Central full-text search

Clients, zones, projects, and file contexts become searchable from a single interface.

02

Large files without friction

Blob and archive paths are visibly integrated instead of being worked around with improvised solutions.

03

Permissions with intent

Finance, TSAC, and client exchange remain clearly separated and transparent.

04

Onboarding in project context

New team members see contacts, quick links, and relevant project basics right from the start.

Client overview

Client workspaces, setup, and permissions are separated - but consistent

The new app structure prevents operational lists, setup flows, and permission cards from disrupting each other inside one endless one-pager.

Governance principles

Internal discussions stay isolated in dedicated message paths.
Client-visible files are mirrored only from approved states.
Roles are inherited per client workspace and only selectively extended per project.