Web Forms in Ailance: External Collaboration Without Platform Access

Web Forms in Ailance: External Collaboration Without Platform Access

Governance processes rarely fail because there is insufficient internal documentation. More often, the problem is that the necessary information is generated outside the governance system.

The department is familiar with the planned AI use case. The supplier has the details regarding its technical and organizational measures. The data processor is familiar with the details of a Processing. The model owner can explain how an AI model is used. A customer or data subject would like to submit a data protection request.

However, many of these individuals do not work directly at Ailance—and are often not supposed to have full access there.

Then the familiar back-and-forth begins: Emails are sent, Excel files are exchanged, PDFs are filled out, and custom forms are created. Information is missing, versions are unclear, and follow-up questions become necessary. In the end, someone has to review the information, organize it, and manually enter it into Ailance.

Ailance Webforms eliminate this very media discontinuity.

They make it possible to capture information outside the platform and import it directly as structured Ailance data.

What are Ailance Webforms?

Ailance Webforms are forms that can be used externally and are based on existing asset templates in Ailance.

A Solution Builder can publish a suitable template as a web form. This turns an internal Ailance form into a controlled entry point for people who do not have regular access to the platform.

The external user receives a clearly defined form and enters the required information there. The Solution Builder determines which questions are displayed, which fields are required, and which entries are permitted.

Among other things, the following can be used:

• Required fields
• Input Validation
• defined field types
• Options
• Help Texts
• multilingual content
• Public Form IDs
• Verified publication statuses

This means that the external user does not work in a separate form outside the system. Their information is already entered in the same structure in which it will subsequently be needed in Ailance.

External input is transformed into governance data that can be used immediately.

What problem do Webforms solve?

In virtually every company, there are governance processes that require information from people who are not regular Ailance users.

Typical examples include:

• A department reports a new processing operation.
• An employee submits a new AI use case.
• A model owner adds information about an AI model.
• A data processor provides information about a Processing.
• A supplier answers questions about Data protection and information security.
• A customer or data subject submits a data protection request.
• An employee reports an incident.
• A whistleblower submits a report in a structured manner.

Without a direct interface to the governance system, workarounds are often used instead: Microsoft Forms, SharePoint lists, Excel files, email templates, or custom-developed portals.

At first glance, these solutions seem simple. In the long run, however, they create additional work:

• Data is stored in multiple systems.
• Required information is missing.
• Information must be entered manually.
• Inquiries and processing times are on the rise.
• Versions and responsibilities become unclear.
• It's hard to find documentation later on.
• Shadow processes are emerging alongside the governance system.

The real problem, therefore, is not the absence of a form. It is the disconnect between the form and the subsequent governance process.

Ailance Webforms bridge this gap.

What can Webforms be used for?

With Webforms, Solution Builders can specifically open up intake processes to external users without having to develop a separate portal.

These processes are particularly well-suited for situations in which external parties or those with limited involvement are expected to make a clearly defined contribution.

Record of Processing Activities

A department, a subsidiary, or a data processor may provide information regarding a Processing provide.

Instead of sending the information by email to the Data protection team When data is submitted, it is recorded using a predefined structure. Required fields and validation checks ensure that the data is as complete and consistent as possible right from the moment it is received.

AI Governance

Employees can submit new AI ideas, AI tools, or specific AI use cases.

The Solution Builder determines what information is needed for the initial review. This may include, for example:

• Purpose and Planned Use
• Designated Business Owner
• AI tool or model used
• Data Types Used
• possible Processing personal data
• third-party provider
• affected Processes or groups of people
• Known Risks
• Desired area of application

The report can then be reviewed and supplemented in Ailance and forwarded to the designated review and approval processes.

Data Protection Inquiries

Customers, employees, or others affected Individuals can submit data protection requests using a structured web form.

The required information is requested in a targeted manner. This ensures that the request is received by Ailance in its entirety and can be assigned, processed, and documented there immediately.

Supplier Management

Suppliers may provide information regarding data protection, information security, certifications, subcontractors, points of contact, or technical and organizational measures.

The information does not end up in different email inboxes or spreadsheets, but rather in a uniform, analyzable structure.

Incident and Whistleblower Systems

Incidents or reports can be logged using a controlled form without granting the reporter full access to the platform.

The Solution Builder defines what information is required for the initial assessment, assignment, and possible escalation.

The common denominator is always the same:

The information is entered outside of Ailance, but is already created within Ailance in the correct structure.

How does a web form work in Ailance?

The process consists of seven steps.

1. The Solution Builder selects the intake process

First, a decision is made regarding which process should be made available to external individuals or those who do not work regularly in Ailance.

Not every internal form needs to be published as a web form. A web form is particularly useful when a person is expected to make a clearly defined contribution: a Processing report an issue, submit an AI use case, add information about a supplier, or submit a request.

2. A suitable asset template is prepared

The web form is based on an asset template in Ailance.

In it, the Solution Builder specifies what information is required and how the form is structured. This includes fields, sections, selection options, required fields, help texts, and validations.

This means that the data structure is not created only after the form is submitted. It is already part of the form.

3. The texts for external use are determined

Next, the text that external users see when filling out the form is maintained.

These include, in particular:

• Headline and Explanations
• Field labels and help texts
• Label for the "Send" button
• Success message after submission
• Error message when an operation fails Transmission

In international proceedings, this content may be provided in multiple languages.

4. The web form is published

After configuration, the Solution Builder publishes the WebForm.

Ailance generates a controlled publication status and provides the necessary information for calling or embedding the form. The web form can be uniquely identified using its public form ID.

For example, the form can be made available via a link or integrated into an existing website, intranet, or service portal.

5. The external person fills out the form

The user opens the web form without needing full access to the Ailance platform.

She sees only the questions and input fields intended for this process. Required fields and validation checks help ensure that the necessary information is entered completely and in the correct format.

The form is then submitted.

6. The information is entered into Ailance in a structured format

The submitted data is not sent to Ailance as an unstructured email or attached file. It is imported in the structure defined by the asset template.

This eliminates the need for manual data entry from a separate form system.

The information can be reviewed, supplemented, assigned to the appropriate individuals, and processed further within the designated governance process in Ailance.

Depending on the solution, this may be followed by, for example:

• technical review
• Data Protection Review
• Risk assessment
• Approval
• Follow-up Question
• Division of Responsibilities
• Escalation
• Reporting
• Audit-Documentation

7. Changes are published in a controlled manner

If the intake process changes, the Solution Builder can adapt the underlying template.

New required fields can be added, wording can be improved, validation rules can be changed, or additional language versions can be added. The changes are then intentionally published as an updated version.

If the form is no longer needed, it can be withdrawn.

This way, the external intake process remains manageable without every internal change immediately and unnoticed affecting the published form.

Why Web Forms Improve Data Quality

The quality of a governance process depends largely on the quality of the information it receives.

When people voluntarily submit their information via email, they decide for themselves what information they consider relevant. As a result, the very details needed for an assessment or decision are often missing.

With an Ailance Webform, the Solution Builder defines the information requirements in advance.

Required fields ensure that essential information is not omitted. Validation checks prevent inappropriate entries. Drop-down menus ensure consistent values. Explanatory notes help those filling out the form to understand the questions correctly.

This reduces:

• Incomplete submissions
• misleading information
• manual post-processing
• Questions
• inconsistent data
• Transmission errors

This means that data quality is not improved only during the internal review; it is controlled right from the point of data entry.

The difference from ordinary web forms

A typical web form collects responses.

An Ailance web form generates governance data.

With a separate form, the real work often doesn't begin until after it has been submitted. The information must be reviewed, organized, categorized, and transferred to the governance system.

An Ailance web form, on the other hand, is an integral part of the solution. It is based on an asset template and uses the structure defined therein. Required fields, validations, and translations can be used immediately. The form is published under controlled conditions and has a unique public form ID.

This allows the Solution Builder to maintain control over the process.

It is not the external party who decides what information to provide and in what format. The Solution Builder determines what information is required and the structure in which it is submitted.

Why Versioning Is Important

Intake processes are changing.

New required fields will be added. Questions will be rephrased to make them easier to understand. Validation rules will be adjusted. Additional languages will be added. Fields that are no longer needed will be removed.

If such changes were to affect a public form immediately and in an uncontrolled manner, it would be nearly impossible to determine later which version of the form was used for a specific submission.

Versioning therefore separates the internal editing of the template from the published version.

The Solution Builder deliberately decides when a change is communicated externally. This ensures that it remains clear on what basis information was collected.

This oversight is essential for governance, inspection, and audit processes.

Multilingual Web Forms for International Processes

Governance processes rarely stop at national borders.

A central data protection process can affect companies and employees in various countries. Suppliers are located in different regions. AI use cases are submitted by international business owners. Data protection requests may be received in multiple languages.

With translatable web forms, there's no need to set up a separate process for each language.

The subject matter remains the same. Only the language used in the questions, explanations, and feedback will be adjusted.

This increases the reusability of centralized solutions and reduces the number of custom local forms. At the same time, the incoming data remains comparable and can be further processed within a shared governance process.

Web form or access to an external platform?

Web forms and external platform access serve different purposes.

A web form is a good choice when a person needs to submit information without having to continue working in Ailance afterward.

Controlled external access is useful when a person is expected to perform additional tasks, repeatedly update information, view the status of tasks, or regularly participate in a governance process.

Depending on the use case, Ailance can use additional access models for this purpose, such as:

• Domain-User Access Patterns
• Token-Based Task Completion
• Microsoft Entra ID Integration
• Limited external permissions

The Solution Builder therefore does not merely decide what information is needed; it also determines what form of participation is appropriate.

A one-time submission does not require a complete user account. Ongoing collaboration, however, may require controlled and clearly defined access.

Automatic User and Contact Provisioning

If individuals regularly participate in governance processes, their roles and responsibilities must be accurately reflected in Ailance.

These include, for example:

• Process Owner
• Business Owner
• Model Owner
• Reviewer
• DPO
• Departments
• Supplier Contacts
• more responsible or persons involved

With automatic user and contact provisioning, users and contacts can be created or updated based on Microsoft Entra ID, group memberships, and defined attributes.

This feature is not part of the Web Forms system itself. It complements Web Forms in situations where a one-time submission leads to ongoing collaboration involving clearly assigned individuals and responsibilities.

The real benefit: a seamless flow of data

Web forms don't just change the user interface. They change the entire data flow.

Without Web Forms:

Information arrives via email, Excel, or PDF. It must be searched for, verified, requested, copied, and manually entered into Ailance.

With Ailance Webforms:

Information is collected via a controlled form and is entered directly into Ailance in a structured format. There, it can be reviewed, supplemented, and used for workflows, approvals, analyses, reports, and audits.

This reduces manual work and, at the same time, improves:

• Data Quality
• Processing Speed
• Traceability
• Process Control
• international reusability
• Auditability
• Collaboration with External Stakeholders

Ailance thus becomes more than just a platform for internal processing. It also serves as a controlled entry point for information from business units, group companies, suppliers, customers, and other external stakeholders.

Conclusion

Ailance Webforms is not just another form tool.

They are a building block for end-to-end governance processes.

Solution Builders can open up selected intake processes to external users without having to develop separate portals and without granting full platform access to every person involved.

From the very beginning, incoming information adheres to the required Ailance structure. Required fields, validations, translations, and versioning ensure that external contributions are verified and arrive in a format that is ready for immediate use.

For businesses, this means less email chaos, less spreadsheet maintenance, fewer shadow processes, and less manual Data Transmission.

For Solution Builders, this means greater control over data quality, processes, and further processing.

It's not about gathering as much information as possible in any way you can. It's about systematically organizing the right information into the right structure.

ailance-dsb-1-im