diff --git a/cairis/config/architectural_pattern.dtd b/cairis/config/architectural_pattern.dtd
index 3df7d7c57..6c055fbb6 100644
--- a/cairis/config/architectural_pattern.dtd
+++ b/cairis/config/architectural_pattern.dtd
@@ -43,7 +43,7 @@
 
 <!ELEMENT role (description)>
 <!ATTLIST role name CDATA #REQUIRED>
-<!ATTLIST role type (Stakeholder | Attacker) #REQUIRED>
+<!ATTLIST role type (Stakeholder | Attacker | Data Controller | Data Processor | Data Subject | Machine) #REQUIRED>
 <!ATTLIST role short_code CDATA #REQUIRED>
 
 <!ELEMENT asset (description,tag*,significance,interface*,security_property*)>
diff --git a/cairis/config/cairis_model.dtd b/cairis/config/cairis_model.dtd
index 8d601ab6b..84801ad07 100644
--- a/cairis/config/cairis_model.dtd
+++ b/cairis/config/cairis_model.dtd
@@ -87,7 +87,7 @@
 <!ELEMENT riskanalysis (role*,asset*,vulnerability*,attacker*,threat*,risk*,response*,asset_association*)>
 <!ELEMENT role (description)>
 <!ATTLIST role name CDATA #REQUIRED>
-<!ATTLIST role type (Stakeholder | Attacker) #REQUIRED>
+<!ATTLIST role type (Stakeholder | Attacker | Data Controller | Data Processor | Data Subject | Machine) #REQUIRED>
 <!ATTLIST role short_code CDATA #REQUIRED>
 
 <!ELEMENT tag EMPTY>
diff --git a/cairis/config/riskanalysis.dtd b/cairis/config/riskanalysis.dtd
index 0e6536aad..2122ddc6a 100644
--- a/cairis/config/riskanalysis.dtd
+++ b/cairis/config/riskanalysis.dtd
@@ -22,7 +22,7 @@
 <!ELEMENT riskanalysis (role*,asset*,vulnerability*,attacker*,threat*,risk*,response*,asset_association*)>
 <!ELEMENT role (description)>
 <!ATTLIST role name CDATA #REQUIRED>
-<!ATTLIST role type (Stakeholder | Attacker) #REQUIRED>
+<!ATTLIST role type (Stakeholder | Attacker | Data Controller | Data Processor | Data Subject | Machine) #REQUIRED>
 <!ATTLIST role short_code CDATA #REQUIRED>
 <!ELEMENT description (#PCDATA)>
 
diff --git a/cairis/sql/init.sql b/cairis/sql/init.sql
index edc46b0bc..44624f2fb 100755
--- a/cairis/sql/init.sql
+++ b/cairis/sql/init.sql
@@ -4482,6 +4482,7 @@ INSERT INTO role_type(id,name) values(1,'Attacker');
 INSERT INTO role_type(id,name) values(2,'Data Controller');
 INSERT INTO role_type(id,name) values(3,'Data Processor');
 INSERT INTO role_type(id,name) values(4,'Data Subject');
+INSERT INTO role_type(id,name) values(5,'Machine');
 INSERT INTO behavioural_variable(id,name) values (0,'Activities');
 INSERT INTO behavioural_variable(id,name) values (1,'Attitudes');
 INSERT INTO behavioural_variable(id,name) values (2,'Aptitudes');
diff --git a/docs/roles.rst b/docs/roles.rst
index e3c439968..b25ed2851 100644
--- a/docs/roles.rst
+++ b/docs/roles.rst
@@ -3,7 +3,7 @@ Roles
 
 Roles represent the abstract classes representing human agents; these also encapsulate behaviours and responsibilities.
 
-CAIRIS supports 5 types of role:
+CAIRIS supports 6 types of role:
 
 =============== ================================================================================================= ===============
 Role            Description
@@ -13,6 +13,7 @@ Attacker        Human agents behaving maliciously.
 Data Controller The entity that determines the purposes, conditions and means of the processing of personal data. GDPR
 Data Processor  The entity that processes data on behalf of the Data Controller.                                  GDPR
 Data Subject    A natural person whose personal data is processed by a controller or processor.                   GDPR
+Machine         Software agents that behave with some level of autonomy.
 =============== ================================================================================================= ===============
 
 Adding, updating, and deleting a role
@@ -51,4 +52,4 @@ By changing the environment name in the environment combo box, the
 responsibility model for a different environment can be viewed.
 By clicking on a model element, information about that artifact can be viewed.
 
-For details on how to print responsibility models as SVG files, see :doc:`Generating Documentation </gendoc>`.
\ No newline at end of file
+For details on how to print responsibility models as SVG files, see :doc:`Generating Documentation </gendoc>`.