Repository and object model
A repository is the shared home of your enterprise model. It holds reusable objects — processes, resources, risks, strategies, and many more — together with the diagrams, files, and reports that describe them, all arranged in one tree.
Overview
Open a repository through Model in the navigation rail. The left side shows the repository tree; selecting an entry opens its page on the right, with tabs for the item's content, relationships, properties, cycles, history, and permissions. If you have access to several repositories, switch through the user menu's Change Repository entry.
Above the item's page, a breadcrumb tracesTrace The ordered sequence of activities executed for a single case. Grouping cases by identical traces produces variants. its place in the tree; you can switch it to show your recent history instead of ancestors, and turn breadcrumbs on or off in My Profile. You can drag a breadcrumb entry onto an item's Relationships tab to create a relationship.
The top level of the tree is fixed: each object family has its own root folder.
- Strategies
- Capabilities
- Products
- Business Services
- Processes
- Journeys
- Requirements
- Controls
- Risk Catalog
- Opportunity Catalog
- Work Products
- Classes
- Glossaries
- External Agents
- Resources
- Interfaces
- DashboardsDashboard A configurable view in Process360 Live that aggregates KPIs, charts, and filters across one or more processes for stakeholders to monitor performance.
- Reports
- Shape Libraries
A repository administrator can hide the root folders your organization doesn't use.
Items that aren't bound to a family — folders, diagrams, external files, web addresses — live directly under the repository or in a folder you create there. They can't go inside a root folder or anything beneath it. A shortcut goes wherever its target could go.
Below the roots, you organize content with folders. Which item types you can create inside a given parent depends on that parent: a Process folder offers processes, while the repository root offers diagrams, files, and other family-independent types. The full type list is in the Enterprise object catalog.
Objects are reusable: one Resource or Process exists once and is referenced everywhere it matters — by diagram shapes that describe it, by relationships to other objects, and by reports that query the model. That's what makes the repository a connected model rather than a document store.
Key concepts
- Item — any entry in the tree: an object, folder, diagram, or file.
- Enterprise object — a modeling object such as a Process, Resource, Risk, or Capability that represents part of your business.
- Root folder — the fixed top-level folder of an object family. You can add subfolders and objects beneath it, but not new top-level families.
- Check-out / check-in — diagrams, IGX documents, external files, and Reports are edited through an exclusive check-out and build a version history on check-in.
- Approved version — items can run cycles; readers without the See Unapproved permission see the latest approved version.