Organizational Knowledge

As projects are set up — lifecycle scripts, dependencies, acceptance criteria, instructions — automatically makes that knowledge available across your organization. The Organizational Knowledge page provides a single place to see everything your organization has built, and when creating a new project you can import from it to skip onboarding.

​

How It Works

automatically tags project artifacts (lifecycle scripts, dependencies, acceptance criteria, instructions, project configuration, and wikis) with their associated repositories. This makes them discoverable as organizational knowledge without any manual step. The following artifact types are tracked:

​

Browsing Organizational Knowledge

The Organizational Knowledge page (accessible via the Knowledge tab in the sidebar, visible to administrators) is the central hub for all knowledge across your organization. Use it to understand what configuration exists, review how other projects are set up, and identify reusable patterns. The page shows a card for each knowledge group. Each card displays:

• The repository handles the knowledge applies to
• Which project it originated from
• Artifact type buttons with counts you can expand to read the full content

​

Reading Artifact Content

Click any artifact type button on a card to expand and read its content. The content renders in the same format used in the project’s own knowledge views. When an artifact type has multiple items (for example, 2 instructions), each item is numbered (e.g., “Instructions 1/2”, “Instructions 2/2”) with a divider between them.

​

Searching and Filtering

Use the search bar to find knowledge by repository name. Matching text is highlighted in the results. Use the Filter by repo dropdown to narrow the list to cards containing specific repositories. The filter supports two modes: Use the Filter by project dropdown to narrow the list to knowledge originating from specific projects. Multiple projects can be selected.

​

Importing During Project Creation

When you create a new project and select repositories, automatically checks for available organizational knowledge. You see one of two states in the Organizational Knowledge section of the create project form:

​

Selecting Items to Import

Click Manage to open the knowledge transfer drawer. During project creation, the drawer is focused on the knowledge most relevant to your new project: it shows only instructions and wikis that are recommended (i.e. whose repositories overlap with the project’s selected repositories). Filtering and searching. Use the category tabs at the top to filter by artifact type (All, Instructions, Wikis) or type into the search bar to find items by name. When a search is active, matching text is highlighted in the results. Selecting items. Each item has a checkbox. Click an item row or its checkbox to select it. All displayed items are pre-selected by default. Use the footer links to quickly select all, clear your selection, or reset to the default set. Previewing content. Click the Preview button on any item to expand its full content inline, rendered in the same format as the project’s own knowledge views. Importing. The footer shows how many items are selected. Click Import to proceed. If no items are selected, click Continue without importing to start fresh. Once you close the drawer, the create project form updates to show how many items are selected (for example, “3 items selected”). Click Manage again to reopen the drawer and adjust your selection.

​

After Import

When you create the project, selected items are copied into it. Onboarding stages covered by the imported configuration are marked as complete, and you proceed directly to later stages. After import, the new project owns its own copy of the configuration. Changes in the new project do not affect the source, and changes in the source project do not affect projects that already imported from it.

​

Importing During the Migration

You can also import organizational knowledge into an existing project. On the project page, click Import Knowledge in the sidebar to open the import drawer. The mid-project import drawer shows a different set of artifact types than the creation-time drawer: During mid-project import, items whose repositories overlap with the project’s repositories are marked with a green Recommended tag and pre-selected, but any displayed item can be imported regardless of repository match. Collision handling. When importing into an existing project, items that share the same name as an existing wiki or instruction in the project are flagged as collisions. For each collision, you can choose to replace the existing item, keep both, or cancel the import for that item.

​

Matching Rules

Organizational knowledge is available to all new projects in the tenant. Items whose repositories overlap with the new project’s selected repositories are considered recommended. During project creation, only recommended items are shown (and only instructions and wikis), so the drawer is already filtered to the most relevant knowledge. During mid-project import, all non-environment items are shown, with recommended items highlighted and pre-selected — any item can be imported regardless of repository match.