A repository is basically a big "bucket" used to store all the assets needed for a project or a group or a campaign. Repository administrators can set up as many repositories as needed for different asset management projects.
Consider different departments in your company, such as sales, finance, and marketing. All these departments have their own teams of people working on content. Content from the finance department may not be relevant (and sometimes not even accessible) to people in the sales department, at least during part of the content life cycle. Content used by the marketing department can be accessible to teams working for other departments, but restricted only to review and not to modify or to publish.
Your organization could create separate repositories for each department or context and assign their respective teams as users of that repository with specific rights. When users sign in to Oracle Content and Experience, they are assigned to relevant repositories, and access privileges are granted to them for repositories to allow for contribution, review, or approval. Some users might be involved with more than one department and may need access to content in multiple repositories.
If you have the appropriate privileges, you can create repositories in the Oracle Content and Experience web interface under Administration > Content.
All aspects of the content life cycle—including management, workflow, publishing, and revision tracking—are available in the context of repositories that assets are part of. To that end, each repository has taxonomies, content types, publishing channels, and localization policies associated with it.
Repositories are silos, which means that assets from one repository can’t be seen or referenced by another repository. It must be copied into another repository. On the other hand, assets from multiple repositories can be published to the same channel. This means that even though assets in repositories are managed in silos, they can be consumed together in clients.