====== User ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A User is a person, [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organization]], or system that interacts with or uses a system, service, or resource to achieve a purpose.

A User can interact through:

  * A user interface
  * An application programming interface
  * An [[dido:99_annexes:annex-b-terms-and-definitions:e:endpoint|Endpoint]]
  * A command-line interface
  * An automation interface
  * A service request
  * A message
  * A delegated process
  * Another supported interaction mechanism

A User can identify:

  * Its identity
  * Its name
  * Its type
  * Its associated Organization
  * Its assigned [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Roles]]
  * Its permissions
  * Its credentials
  * Its applicable authentication method
  * Its applicable authorization
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_domain|Governance Domains]]
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:p:policy|Policies]]
  * Its applicable [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Its [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A User can act in one or more Roles. The assigned Role establishes the responsibilities, permissions, and expected behaviors applicable to a particular interaction.

===== Definition =====

//person, [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organization]], or system that interacts with or uses a system, service, or [[dido:99_annexes:annex-b-terms-and-definitions:r:resource|Resource]] to achieve a purpose//

===== Source =====

Adapted from:

  * DIDO Reference Architecture
  * DIDO Reference Implementation Conceptual Model
  * DIDO-TE draft Requirements Register

===== Note =====

A User does not need to be a human. An Organization or automated system can act as a User when it interacts with or uses another system, service, or Resource.

A User differs from a [[dido:99_annexes:annex-b-terms-and-definitions:r:role|Role]]:

  * A User identifies the person, Organization, or system that interacts with or uses a capability
  * A Role identifies the responsibilities, permissions, and expected behaviors assigned to that User

A User can act in multiple Roles. Multiple Users can act in the same Role.

A User differs from an [[dido:99_annexes:annex-b-terms-and-definitions:o:organization|Organization]]:

  * An Organization is an identifiable body structured to pursue defined purposes and exercise assigned responsibilities
  * A User is an interacting or using party

An Organization becomes a User in a particular context when the Organization interacts with or uses the applicable system, service, or Resource.

A User differs from a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]]:

  * A User uses or interacts with a system, service, or Resource
  * A Node is an identifiable participant that performs one or more assigned Roles in a distributed system

The same system can act as both a User and a Node when it satisfies both definitions.

A User identity does not by itself establish permission to perform an action. The applicable Role, authorization, and Governance Policy determine the permitted actions.

===== Example =====

A person uses DIDO-TE to initiate a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_run|Test Run]].

The person is the User. The person acts in the Test Operator Role.

The Test Operator Role permits the User to:

  * Select an approved [[dido:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definition]]
  * Select an approved [[dido:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environment]]
  * Supply permitted [[dido:99_annexes:annex-b-terms-and-definitions:t:test_argument_value|Test Argument Values]]
  * Initiate Test Execution
  * Monitor the Test Run
  * View the resulting [[dido:99_annexes:annex-b-terms-and-definitions:t:test_result|Test Results]]

The User cannot approve the resulting Validation Decision unless the applicable Governance Policy also assigns the required approval Role.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>