Skip to main content

Moving an initiative up to a higher level in a company network

Do you manage initiatives across a network of entities and want to move them to a higher level of the hierarchy? This article explains how, and which rules apply depending on your role and the initiative's situation.

🎯 Purpose of this article

This article guides you through moving an initiative to a parent entity within a company network. It's intended for company administrators operating in a multi-entity context

✅ Prerequisites

  • Have a company admin account with rights on the entity concerned (and the target entities).

  • The initiative must have been created at the level of a sub-entity of the network.

  • For dedicated initiatives with registered volunteers, the partner organization must be a partner of a higher-level entity.

📋 How to move an initiative?

The move is done from the initiative's page:
​Catalog > Edit > Dedicated company > Edit company
The list of entities available in this menu depends on your role and the initiative's situation (with or without registered volunteers).

➡️ Initiative without registered volunteers

You can move the initiative to any entity within the branch associated with the partnership with the organization — provided you have administration rights on the target entity.

👉 In practice: you can freely move the initiative anywhere within your administration scope, as long as it stays within the branch where the organization is a partner.

➡️ Initiative with registered volunteers

As soon as a volunteer has registered, the move is more restricted: you can only move the initiative up to a higher entity in the hierarchy (parent entity, grandparent entity, etc.), never beyond the level at which the organization is a partner.

⚠️ You cannot move the initiative to an entity in a different branch of the network — only "upward" within the current branch.

➡️ General rule — Organization partnered with multiple entities

If the partner organization is linked to several entities in the network (in different branches), the maximum allowed move level is determined by the closest common ancestor of all these entities.


​Example: If the organization is a partner of two entities that have no closer common ancestor than the top of the network, the initiative can be moved up to the global level.

🗂️ Viewing the network hierarchy

To get your bearings within your network structure before moving an initiative, use the network list view, available on the company admin side. It lets you view all entities and their hierarchy, and identify the right target level for the move.

To access it: Administration > Company > My network

💡 Good to know

  • A company admin can only move an initiative within their own scope: their entity and its child entities.

  • For dedicated initiatives (associated with one or more partner organizations), the move rules take into account the organization's partnership level — not just the company's internal structure.

  • If in doubt about the applicable scope, check with your Komeet admin or your Komeet contact.

Did this answer your question?