1. data.world help center
  2. Metadata
  3. Organization and user management

Multi-organization models

Overview

Companies with multiple departments or divisions using data.world may choose to create more than one organization.  Reasons for doing this include:

  • You don't want to provide visibility of certain datasets to the entire organization,
  • You want to provide the entire company visibility of each division's business glossary, but grant Admin privileges to each business glossary separately

Top-down model

In the top-down model, the main corporate organization adds each department's organization as a member.

It is permissible for one person to be a member of multiple department organizations.  If those organizations provide different levels of access to the corporate organization, the individual will be granted the higher level of access.

Key features

  • Membership to the main corporate organization can be granted to individuals directly or through their membership in department orgs
  • Different departments can be granted different levels of access over resources owned by the main corporate org(e.g everyone in a 'Governance' org can be given Admin access to the corporate org)
  • Resources owned at the department level must be explicitly shared company wide - there's greater control over which other departments can see them
  • Removing members from the corporate organization does not revoke access to department organizations

Limitations

  • When the main corporate organization has multiple Collections, administrators have control over all Collections

orgs-top-down.png

Bottom-up model

In the bottom-up model, each department's organization adds the main corporate organization as a member.

Key features

  • Each department can have its own Collection catalog with a unique administrator
  • Resources owned at the department-level are visible company wide
  • When a member is removed from the corporate organization, they also lose the inherited view access to each department organization
  • Can be used for department organizations that include contractors, clients, or others that should not have access to corporate resources - those third parties can be given view access to only the department

orgs-bottom-up.png

 

Hybrid models

Top-down and bottom-up structures are not mutually exclusive.  A company could use a top-down structure for the majority of its work, but also create a single org with a bottom-up structure for sharing client work with clients.