Upstream/Downstream Inheritance for KBs and Assets
P
Previous Gecko
We propose implementing a system where an asset (or any item, e.g., Folder, KB, Password, etc.) can have an “Upstream Inheritance” toggle:
- Upstream: The original source (e.g., Golden Template KB).
- Downstream: The company-specific instances that inherit from the upstream source.
When enabled:
- Updates to the upstream item automatically propagate to all downstream instances.
- Downstream items can exist in multiple companies without affecting the original upstream source.
- Version control should track changes in both upstream and downstream instances to maintain consistency and allow rollback if needed.
Key Benefits:
- Standardizes processes across multiple companies while allowing company-specific modifications.
- Ensures that the upstream source remains unaffected by downstream changes.
-Saves time and reduces errors by eliminating the need for manual updates across multiple KBs or assets.
-This feature would significantly improve efficiency and consistency in managing company-specific KBs, assets, folders, passwords, and other resources derived from a central template.