---
title: How does a codebot work in practice?
tags: codebots/library
id: 510
keywords:
- codebot
- development-workflow
---

The documentation that is provided to a codebot comes in the form of three diagrams:

1. Entity,
2. UI,
3. Security

The [entity diagram](../500) is where we define the data within our application (as business objects or entities), and the relationships between different entities. The entity diagram relates to the achitecture of the application and, as such, many related behaviours can be applied here. More details on the entity diagram can be found in [Entity Diagram Basics](../141).

The [UI diagram](../179) is where we define our user interface pages and their contents. Behaviours which relate to UI elements can be applied here through the concept of a **tile**.

Finally, the [Security diagram](../180) is where we define our groups and permissions, giving us full control over what groups can access what business objects.

These three diagrams combine and are provided as input into our codebot which then provides the code as output.


As the output code has a direct relationship with the input digrams, we can continually change these diagrams to keep updating our code. This can be done many times within a few minutes if required.


**Key concepts**

- [What is an entity diagram?](../500)
- [Entity Diagram Basics](../141)
- [The User Interface Diagram](179)
- [Using the Security Diagram](../180)
- [Controlling the diagrams](../182)