Answer
Workspace can be adapted to different roles, data, views, cases and integrations. The specific scope depends on the available product version and the project. Not every conceivable change should be implemented. Too many customer-specific special paths can make use, testing and updates harder and turn an extensible platform into a one-off solution that is hard to maintain.
That is why we distinguish between extensions that are necessary for the business, configuration and mere habit. A special feature makes sense if it lowers risk, saves work or reflects an important competitive advantage. In other cases, an adapted process within the standard can be more economical. Before we commit, we clarify whether the change should be part of Workspace, a project-specific extension or a separate business application.
As of 3 September 2026
Further reading
Related topic: Workspace overview