Skip to content

Collaboration in Devici

Devici enables distributed teams to collaborate on threat modeling in real time.

Threat modeling is most effective when it includes perspectives from engineering, security, architecture, and product teams. Devici’s collaboration features make it possible for multiple contributors to work together.

Overview

Collaboration in Devici allows multiple users to work on the same threat models simultaneously or asynchronously.

These capabilities help teams:

  • Share ownership of threat models
  • Capture input from multiple disciplines
  • Reduce bottlenecks during reviews
  • Maintain a clear record of changes and discussions

Access and Participation

When an organization is set up in Devici:

  • Administrators invite users to the platform
  • Access to collections and threat models is controlled through collections, teams, and permissions
  • Multiple users can access the same threat model based on their assigned permissions

Collaboration is governed by the access rules defined in the Administration section.

Real-Time Collaboration

When multiple users open the same threat model at the same time:

  • Active collaborators are displayed in the top-right corner of the screen
  • Each user’s cursor is visible on the canvas
  • Changes are reflected in real time as users work

This allows teams to model threats together during design reviews, working sessions, or security workshops.

Asynchronous Collaboration

Devici also supports asynchronous collaboration.

Users can:

  • Log in at different times
  • Make updates to the same threat models
  • Leave comments and notes for other collaborators
  • Review changes made by others

This enables collaboration across time zones and schedules without requiring everyone to be online simultaneously.

Tracking Contributions

As users interact with a threat model:

  • Edits to elements, flows, and attributes are recorded
  • Comments and updates are visible to other collaborators
  • Activity provides context for ongoing discussions and decisions

These signals help teams understand how a model has evolved and who contributed to specific changes.

Best Practices for Collaboration

  • Involve multiple roles early in the modeling process
  • Use collections and teams to manage access cleanly
  • Collaborate in real time for complex design discussions
  • Use comments and reviews to support asynchronous input

Effective collaboration ensures threat models reflect shared understanding and remain accurate as systems evolve.