Configuring the channel and forms

1. Regulatory Concept & Core Standards

In this video we will work through a concrete decision: create a form that collects useful information without unnecessary identification. The aim is to explain the criterion used and apply it to a workplace situation. We will start with the concept, move to the procedure and finish with a case to solve. This course presents a configuration method, not an assertion about the functions of a particular UNOVOX account. Each setting should be linked to the procedure and tested with fictional information. A technical change can affect access, confidentiality or time calculations and therefore needs verification.

The form should help users describe facts: what happened, when, where and what material may help. Excessive fields create barriers and increase data collection. The choice between identification and anonymity must match the channel and the law. Do not make names mandatory in a route presented as anonymous or require users to know the legal classification of the situation.

Apply the following rule: Article 7 allows anonymous reports. The procedure defines the chosen approach, subject to specific provisions. Later identification and retaliation do not exclude protection where Article 6 conditions are met. Confidentiality restricts disclosure to unauthorised persons; it is not a promise that identity can never lawfully be disclosed in proceedings. User information must match the channel’s actual functions.

2. Practical Implementation & Procedure

Start with a title and a short explanation. Configure essential and optional fields, attachment limits and help messages. Use neutral wording, such as people mentioned instead of guilty parties. Test unidentified submission, the readability of the privacy notice and the follow-up mechanism. Check whether hidden fields or integrations introduce data that users would not expect. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.

3. Case Study & Compliance Action

The form requires an identity-document number and the legal provision allegedly breached. The user knows the event but not the article. The team removes unjustified requirements and makes factual description easier. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.

The exercise is as follows: Should every field convenient for the administrator be mandatory? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.

No. Necessity follows the purpose and law, not convenience. Check whether the task can be performed with less personal information.

One mistake to avoid is: requiring personal details that are unnecessary to assess the report.

Now apply the national rule to a second decision. The form always requires a name and an identity-document copy although the page promises anonymity. What must change?

Check the adopted approach under Article 7 and the channel’s actual functions. Do not collect an unnecessary identity copy for technical convenience. Correct the form and public information together. Explain anonymous versus confidential reporting. Assess information already received under necessity and the applicable deletion process.