Select the right level of authorisation

ELChat allows the actions of a connector to be controlled separately. The right adjustment depends on the business impact, not just the technical capacity.

Level	To be used for	Example of a decision
Automatic	low-impact reading or frequent action	check availability in controlled perimeter
Confirmation required	action that writes, publishes, sends or engages the undertaking	send a message, create an appointment, edit a data
** Blocked**	unnecessary action, too risky or out of politics	deletion, publication or unauthorized expenditure

When confirmation is required, choose who decides: the visitor or an advisor. This distinction must correspond to the real path.

Method of decision

For each action, ask yourself:

1. Does it modify an external system?
2. Is it reversible?
3. Can she incur an expense, communication or obligation?
4. Should the applicant see the data returned?
5. Would an error be detected quickly?

Start with the most careful level, test, and then soften only the stable actions. For screen details, see Automatic, confirmation or blocking.

Example: appointment policy

For a commercial agent who uses Google Calendar:

• See availability: Automatic, because action only reads the calendar;
• create an event: Confirmation required — An advisor confirms because an invitation is sent;
• reprogram: Confirmation required — An advisor confirms because an existing appointment is changed;
• cancel: Blocked, if the ELChat course should not delete an appointment.

Test each case with a fictitious event. The expected result is an immediate reading, a request for confirmation for the entries and a refusal for cancellation. This method verifies the actual policy rather than limiting itself to the presence of the connector.