Changes in 421d56c: Updated Roles (markdown)

				Roles.md
			
          @@ -7,7 +7,7 @@

           4. Staff

           5. FDC Educator

           5. [Finance](/Finance-Role)

          -5. Centre Admin

          +5. Centre Admin (test only at this stage)

           6. Admin - Authorised User delegation

           7. Authorised User

          @@ -65,24 +65,30 @@ For details of the specific functions accessible to this role go [here](/Finance

           A user account that has been attached to a service with **Centre Admin** rights can access both child and parent information for nominated services within an organisation. This admin role has no access to and Extracts or reports. They can be switched between Staff, Centre Admin and Admin roles if needed or revoked.

          -#### Admin - Authorised User delegation

          +#### Admin - Authorised User has delegated "submit" functions.

          -A user account that has been attached to a service with **Admin** rights can access both child and parent information and all reports. Essentially they can perform all functions within the system that involve sending information to CCMS using the They can be switched between Staff Centre Admin and Admin roles if needed or revoked.

          +A user account that has been attached to a service with **Admin** rights can access both child and parent information and all reports. Essentially they can perform all functions within the system that involve sending information to CCS. They can be switched between Staff, Centre Admin and Admin roles if needed or revoked.

          -Ultimately the **Authorised User** is legally responsible for the data submitted to CCS. Anyone with Admin role can submit to CCS, however by giving staff an admin role, the **Authorised User** has ** delegated** sending enrolment and attendance information to another person, but takes responsibility for ensuring they only do so, if that person has the skills and training to do it properly. 

          +Ultimately the **Authorised User** is legally responsible for the data submitted to CCS. Anyone with Admin role can submit to CCS. Therefore, by giving staff an admin role, the **Authorised User** has **delegated** sending enrolment and attendance information to CCS to another person, but takes responsibility for ensuring they only do so, if that person has the skills and training to do it properly. 

           An **Admin** role has therefore been given access to the various CCS **Submit** functions.

          -To become a **Delegated Admin** you must first be attached to the service as an **Admin**.

          +See below for service delegations the Admin role has as well.

           #### Authorised User

           An Authorised User is a person who has been nominated to CCS (via PRODA) as being responsible for the operation of the service and the accuracy and truthfulness of the information provided. 

          -Provided they also have a login or they have delegated responsibility to a staff member with an **Admin** role, an **Authorised User** has authority to make changes both to attendance and enrolment information and changes to details about the service, including hours of operation and financial information, and submitting these changes to CCS. 

          +Provided they have a SC login with an **Admin** role, an **Authorised User** has authority to make changes both to attendance and enrolment information and changes to details about the service, including hours of operation and financial information, and submitting these changes to CCS. 

          +

          +By granting another staff member an **Admin** role the Unthorised user has delegated these functions.

           As a result it's usually only a very small number of people who should be granted an **Admin ** role.

          -An **Authorised** user can not delegate this part of their role. By having  **MANCON** as their provider role in PRODA, they are also able to make changes to details about the service on PRODA, including extending the PRODA key every 6 months on PRODA, creating and removing B2B devices on PRODA. These last two functions cannot be done within SmartCentral, only in PRODA and only with **MANCON** access to PRODA, so it is recommended to have at least 2 staff members with PRODA provider role of **MANCON** so that if one person is away or leaves suddenly, someone else has authority to update service details.

          +An **Authorised** user can not delegate this part of their role. By having  **MANCON** as their provider role in PRODA, they are also able to make changes to details about the service on PRODA, including extending the PRODA key every 6 months on PRODA, creating and removing B2B devices on PRODA. 

          +

          +These last two functions cannot be done within SmartCentral, only in PRODA and only with **MANCON** access to PRODA, so it is recommended to have at least 2 staff members with PRODA provider role of **MANCON**, so that if one person is away or leaves suddenly, someone else has authority to update service details. If the PRODA key or device expires the service cannot query or submit anything to CCS. That includes submission of attendances and enrolments and downloading anny changes, including CCS paid.

          +

          +It is possible to be an **Authorised User** without being having an **Admin** SC login, but there is little to be gained from it as the **Authorised User** is fully responsible for all the data and therefore in practice they will have dual functions. 

          -It is possible to be an **Authorised User** without being an **Admin** but there is little to be gained from it as the **Authorised User** is fully responsible for all the data and therefore in practice they will have dual functions. Some boards and committee members are **Authorised** users with no SC login. In this case someone who has the **Admin** role, needs to also be trusted with a **MANCON** provider role in PRODA.

          \ No newline at end of file

          +Some boards and committee members are **Authorised** users with no SC login. In this case someone who has the **Admin** role, needs to also be trusted with a **MANCON** provider role in PRODA.

          \ No newline at end of file

...	...	@@ -7,7 +7,7 @@
7	7	4. Staff
8	8	5. FDC Educator
9	9	5. [Finance](/Finance-Role)
10		-5. Centre Admin
	10	+5. Centre Admin (test only at this stage)
11	11	6. Admin - Authorised User delegation
12	12	7. Authorised User
13	13
...	...	@@ -65,24 +65,30 @@ For details of the specific functions accessible to this role go [here](/Finance
65	65
66	66	A user account that has been attached to a service with Centre Admin rights can access both child and parent information for nominated services within an organisation. This admin role has no access to and Extracts or reports. They can be switched between Staff, Centre Admin and Admin roles if needed or revoked.
67	67
68		-#### Admin - Authorised User delegation
	68	+#### Admin - Authorised User has delegated "submit" functions.
69	69
70		-A user account that has been attached to a service with Admin rights can access both child and parent information and all reports. Essentially they can perform all functions within the system that involve sending information to CCMS using the They can be switched between Staff Centre Admin and Admin roles if needed or revoked.
	70	+A user account that has been attached to a service with Admin rights can access both child and parent information and all reports. Essentially they can perform all functions within the system that involve sending information to CCS. They can be switched between Staff, Centre Admin and Admin roles if needed or revoked.
71	71
72		-Ultimately the Authorised User is legally responsible for the data submitted to CCS. Anyone with Admin role can submit to CCS, however by giving staff an admin role, the Authorised User has delegated sending enrolment and attendance information to another person, but takes responsibility for ensuring they only do so, if that person has the skills and training to do it properly.
	72	+Ultimately the Authorised User is legally responsible for the data submitted to CCS. Anyone with Admin role can submit to CCS. Therefore, by giving staff an admin role, the Authorised User has delegated sending enrolment and attendance information to CCS to another person, but takes responsibility for ensuring they only do so, if that person has the skills and training to do it properly.
73	73
74	74	An Admin role has therefore been given access to the various CCS Submit functions.
75	75
76		-To become a Delegated Admin you must first be attached to the service as an Admin.
	76	+See below for service delegations the Admin role has as well.
77	77
78	78	#### Authorised User
79	79
80	80	An Authorised User is a person who has been nominated to CCS (via PRODA) as being responsible for the operation of the service and the accuracy and truthfulness of the information provided.
81	81
82		-Provided they also have a login or they have delegated responsibility to a staff member with an Admin role, an Authorised User has authority to make changes both to attendance and enrolment information and changes to details about the service, including hours of operation and financial information, and submitting these changes to CCS.
	82	+Provided they have a SC login with an Admin role, an Authorised User has authority to make changes both to attendance and enrolment information and changes to details about the service, including hours of operation and financial information, and submitting these changes to CCS.
	83	+
	84	+By granting another staff member an Admin role the Unthorised user has delegated these functions.
83	85
84	86	As a result it's usually only a very small number of people who should be granted an Admin role.
85	87
86		-An Authorised user can not delegate this part of their role. By having MANCON as their provider role in PRODA, they are also able to make changes to details about the service on PRODA, including extending the PRODA key every 6 months on PRODA, creating and removing B2B devices on PRODA. These last two functions cannot be done within SmartCentral, only in PRODA and only with MANCON access to PRODA, so it is recommended to have at least 2 staff members with PRODA provider role of MANCON so that if one person is away or leaves suddenly, someone else has authority to update service details.
	88	+An Authorised user can not delegate this part of their role. By having MANCON as their provider role in PRODA, they are also able to make changes to details about the service on PRODA, including extending the PRODA key every 6 months on PRODA, creating and removing B2B devices on PRODA.
	89	+
	90	+These last two functions cannot be done within SmartCentral, only in PRODA and only with MANCON access to PRODA, so it is recommended to have at least 2 staff members with PRODA provider role of MANCON, so that if one person is away or leaves suddenly, someone else has authority to update service details. If the PRODA key or device expires the service cannot query or submit anything to CCS. That includes submission of attendances and enrolments and downloading anny changes, including CCS paid.
	91	+
	92	+It is possible to be an Authorised User without being having an Admin SC login, but there is little to be gained from it as the Authorised User is fully responsible for all the data and therefore in practice they will have dual functions.
87	93
88		-It is possible to be an Authorised User without being an Admin but there is little to be gained from it as the Authorised User is fully responsible for all the data and therefore in practice they will have dual functions. Some boards and committee members are Authorised users with no SC login. In this case someone who has the Admin role, needs to also be trusted with a MANCON provider role in PRODA.
...	...	\ No newline at end of file
	0	+Some boards and committee members are Authorised users with no SC login. In this case someone who has the Admin role, needs to also be trusted with a MANCON provider role in PRODA.
...	...	\ No newline at end of file