The multi-user repository uses check-in/check-out controls and submodeling so teams can work on different entities, attributes, or domains at the same time. Each change is tracked and validated against the shared architecture, preventing overwrites and silent conflicts.
Every update is stored with author, timestamp, comments, and rollback capability. Users can compare revisions side by side, review detailed history, and restore previous versions if needed. This gives teams a complete audit trail of all modeling activity.
Submodels let teams isolate and check out specific sections of a larger model, such as regional structures or domain-specific layers. Each submodel stays connected to the enterprise architecture, allowing teams to move in parallel without blocking one another or causing architectural drift.
The repository supports role-based permissions that define who can view, edit, approve, or publish changes. This helps organizations assign responsibilities, protect sensitive structures, and ensure only authorized users modify key components of the model.
Model updates can be published to Team Server, where business stakeholders, stewards, and reviewers can browse changes, see version history, and participate in discussions. This improves visibility and helps non-technical users stay aligned with ongoing modeling decisions.
