🧰Tools - Workspace-level tool library with workspace-specific adoption

📍 Today: Tools appear to be managed at the individual workspace level. In large enterprise environments, that means admins have to recreate or reconfigure the same tools repeatedly across multiple workspaces. This creates avoidable setup work, increases the chance of drift between workspaces, and makes governance harder when teams need a consistent approved toolset.

It also creates a confusing admin experience when there is no clear distinction between centrally managed tools and workspace-only tools.

✨ Desired: Add tools at the All Workspace level first, so enterprise admins can maintain a central approved tool library once and make those tools available for adoption inside individual workspaces.

Within each workspace, the tools area could be presented as My Tools or a similar workspace-level view that lets admins:

• Add approved tools from the central workspace library

• See which tools are centrally managed versus locally created

• Optionally create a workspace-specific custom tool when a local exception is needed

This would mirror how mature enterprise platforms handle centralized configuration with local flexibility.

📊 Business Justification: For enterprise customers, duplicated setup across workspaces does not scale. A centralized tool library would reduce admin overhead, improve consistency, and support better governance.

Key impacts:

• Lower admin effort: Configure once instead of repeating the same work in every workspace

• Better consistency: Reduce configuration drift across business units, regions, or environments

• Stronger governance: Make it easier to control which tools are approved for enterprise use

• Faster rollout: New tools and updates can be introduced centrally instead of workspace by workspace

• Cleaner change management: Admins can support standardization without blocking legitimate local exceptions

✅ Acceptance Criteria

• Enterprise admins can create and manage tools from an All Workspace level

• Individual workspaces can add or enable tools from that central library without recreating them from scratch

• Workspace admins can clearly distinguish between centrally managed tools and workspace-specific custom tools

• Workspace admins can still create local custom tools when needed

• Updates to centrally managed tools can be rolled out consistently across workspaces using them

• Permissions support appropriate separation between enterprise-level admins and workspace-level admins