About The Org

Many companies have employees and departments spread across buildings, cities, and countries, which causes unique problems when trying to manage content.

Kapost created the Organizations Feature (aka The Org) to help people manage content between parts of their companies that otherwise have little contact - this prevents duplications, promotes efficiency by increasing content visibility, and allows multiple departments to work together.

Here is how it works:

This feature allows a company to have a single overarching Organization (often called “Parent” or “Org”) unit of Kapost. Underneath that Org group, we can setup unique, individual “child” instances. For example, a company might have one Org level instance named for their company, and three “child” instances named by region such as “Company Name North America”, “Company Name EMEA”, “Company Name APAC."

The “Parent” or “Org” Instance:

You don't create content from the Org - rather, it's a way to see all of the content published by the different "Child" instances that your company owns. There isn’t a Settings page, as the Child instances are managed on their own unique set of settings.  What the Org is is a place to have one global editorial calendar rolled up, track activity day-to-day, see all initiatives rolled up together and aggregate analytics.

The Org view also allows you to hop over to various Child instances. If you’re a member of the Parent (Org) instance, you’re able to choose from your drop-down of Kapost instances (the Children) from within your navigation bar, then connect on over to begin working or looking in that unique instance.


The Org instance provides that one holistic view into content across businesses.

The “Child” Instance – Child instances basically stand-alone instances that happen to have an Org in common. These exist and look exactly like your Kapost instance does today. The only difference is that they are rolled up into an Organization. We tell people that this is only a structural or setup choice. There aren’t extra features in the Child instances aside from the face that they belong to an Org.

Visibility – If someone is invited to be part of the Org Instance, they will automatically be added to all of its Child instances as well.  This means that they can see every instance. A Contributor member of the Org instance will have contributor abilities in all instances, likewise with Editor Org users. Users invited to be admin members of The Org will have admin abilities in every instanceThey behave like an admin with the unique ability to move between the Org level and its unique child instances. 

Admins can invite members to a child instance within an Org, giving them the ability to see and work only in that instance.  Alternatively, Org-level admins can invite members to the Org giving them access to multiple child instances. This will give the members the ability to see and work in multiple child instances under the Org without actually seeing the Org.

Learn how to copy content between child instances here

To learn more about managing Org members here.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request