Xedul's entities and how they connect
Concepts and data model
Understanding how Xedul organises information makes everything else predictable: where a document ends up, why a task appears in a list, what a colleague can see.
The hierarchy
Organisation (the practice) ├── Users roles and permissions ├── Clients records and fiscal data │ ├── Contacts people linked to the client │ ├── Cases work containers │ │ ├── Tasks things to do, with due dates │ │ └── Documents files in the case's context │ └── Documents files at client level └── Reference data states, priorities, sectors
Every row of every table carries the organisation it belongs to. That is the mechanism keeping practices separate from one another.
Organisation
The organisation is the practice. It's the root entity: no data exists outside an organisation, and no query can cross its boundary.
User
A user belongs to exactly one organisation and holds a role that defines their scope. See Users and permissions.
Client
The client is the principal subject of the professional relationship. It carries registry details, fiscal data, referent and contact information, and acts as the starting point for reaching linked cases, tasks and documents.
Contact
A contact is a person connected to the commercial or operational journey — including leads not yet converted into clients. It lets you track where a relationship came from and how it developed before it became a client proper.
Case
The case is the work container. It gathers tasks, documents and history around a single line of work, and carries a progress state that says where things stand.
In client-facing communication it pays to pick one term and keep it: "case" reads more naturally for tax and legal practices, "project" for advisory contexts. Xedul supports both language settings.
Task
The task is the minimum unit of work: it has a title, an assignee, a priority, a status and — almost always — a due date. It can be linked to a client and a case, and it's what feeds lists, Kanban and the calendar.
Priorities
Priorities use fixed colours throughout the application, so meaning never changes between screens:
| Priority | Colour |
|---|---|
| Low | Emerald green |
| Normal | Sky blue |
| High | Violet |
| Critical | Rose/red |
Document
A document is a file filed in the context it belongs to: a case, a client or a task. There is no generic "documents" folder disconnected from the work.
Reference data
Some lists are shared and configurable at practice level: case and task states, sectors, lead sources, company sizes. Defining them once prevents each person from inventing their own classification.
How things connect
The value of the model is in the links, not the individual tables:
- From a client you see every open and closed case, and every document.
- From a case you see the tasks, the files and the history of what happened.
- From a task you get back to the client and case in one click.
- From the calendar you reach the task, and from there the rest of the chain.
This is what makes it possible to answer "where are we with this client?" without opening three different tools.
Glossary
- Practice / organisation — the entity using Xedul as its dedicated environment.
- Client — the principal subject of the professional relationship.
- Contact — a person linked to the commercial or operational journey, including leads.
- Case / project — a work container tied to a client or subject matter.
- Task — a single thing to do, with assignee, priority and due date.
- External user — someone outside the practice with limited access.