Types of Repositories
Last updated
Was this helpful?
Last updated
Was this helpful?
In the Content Library, three types of repositories exist:
Open Repository: Open repositories are available to anyone with repository access. Users with permission can view and edit the content within this repository. Open repositories are created for easy access and collaboration, allowing users to contribute and modify content freely. They serve as a shared space.
Managed Repository: Managed repositories are accessible to anyone with repository access, allowing them to view the repository content. Editors must be added manually. Managed repositories are suitable for creating shared spaces where multiple users can access and utilize the content but have limited editing capabilities.
Private Repository: Private repositories are the most restricted. Only added users with specific permissions can view and edit the content within private repositories. Private repositories are ideal for in-process documents or content that should only be accessible to select individuals.
Users' level of access and editing permissions should be considered when selecting a repository type.
Managed repositories allow for broader access with limited editing capabilities, private repositories restrict access to authorized individuals, and open repositories provide an open and collaborative environment for content sharing and editing.
Definition: A “Dropbox” to which any user with feature-level access may contribute content.
Default behavior: None
Recommended Use: To enable all users to contribute without restriction.
Definition: Users can view, but only those added to a given repository as an editor and have an RBAC of MANAGE_{content}_REPOSITORIES under Content Library permissions may add or edit content.
Default behavior: View-only access unless an editor is added to enable modification of content or the user has appropriate RBAC permissions.
Recommended Use: To restrict edit access to qualified individuals (copy editors) within a defined set of narrative sections. This is ideal for teams working on various projects who want to maintain their versions of narrative sections and small to mid-size teams that don’t need to restrict access to use but want to limit curation to leadership.
Definition: A repository to store narrative sections is unavailable unless a user is explicitly given read and edit permissions.
Default behavior: Users may view only (Viewer) or edit (Editor).
Recommended Use: This is a place to copy manually created sections that may contain client-specific data that needs to be sanitized, a place to work on drafts for new narrative sections not ready for general use, or a place to store final narrative sections not available for general use.
