-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
5
-
Problem
Confluence administrators currently face challenges in efficiently managing a wide range of features across all spaces, including blogs, calendars, analytics, automation, whiteboards, databases, smart links, etc.
Each feature must be configured separately for each space, leading to a decentralized and time-consuming management approach that can result in inconsistencies.
Suggested Solution
Introduce a centralized feature management system that allows Confluence administrators to control the availability of all features site-wide.
This chance could include:
- Options to enable or disable features by default for all spaces.
- The ability to apply bulk changes across existing spaces.
- Global default settings for new spaces.
- API capabilities to manage these settings programmatically, allowing for integration with existing administrative tools and automation of routine configuration tasks.
Why This Is Important
Centralized and API-driven management would streamline administrative processes, ensuring consistent application of organizational policies and reducing manual effort. This is crucial for maintaining security, compliance, and a uniform user experience across all spaces.
Workaround
Currently, administrators must adjust feature settings manually for each space as described in the documentation. This process is not scalable for organizations with many spaces and lacks API support.
- derived from
-
CONFCLOUD-76287 Ability to disable Whiteboards Site wide
- Closed
-
CONFCLOUD-78127 Ability to disable Confluence Database Site wide
- Closed