daagwerk Documentation Creating & configuring Accounts
Chapter 2
Creating & configuring Accounts
How to create Accounts (customers/clients), configure their fields and store internal roles.
Creating & configuring Accounts
What is an Account?
The Account is the top level of the structure – your client, customer or a department. Projects hang below it, and Jobs below those (see Projects, Jobs).
How to create an Account
- In the sidebar, open Manage → Accounts.
- Click New account (or the plus/create element at the top of the list).
- Enter at least a name and confirm with Create/Save.
The new account appears in the list immediately. Clicking its name opens the account detail page.
Fields & configuration
On the detail page, click Edit to open the properties. These fields are available:
| Field | Meaning |
|---|---|
| Name | Display name of the account (required). |
| Description | Free text, optional. |
| Master data | Additional customer master data (e.g. invoicing details). |
| Hourly rate | Default rate that is inherited by projects and jobs, as long as none is set there. |
| Currency | Currency of the account (EUR, CHF, GBP, USD, SEK, NOK, DKK, PLN, CZK, HUF, RON). |
| Rounding rule | How tracked time is rounded. |
| Order number | Reference/order number at account level. |
| Status (active) | Inactive accounts are hidden but preserved. |
Internal roles (for notifications)
In the Internal roles block, you can store up to three contacts per account with name + email:
- Account manager – receives automatic notifications,
- Customer success – receives automatic notifications,
- Customer contact – contact person only, not a notification target.
Operational notifications (budget/purchase order) go exclusively to the account manager and customer success. If no email is stored, nothing is sent. Details: Notifications.
The Account at a glance
The detail page shows key figures (projects, jobs, bookings, budget utilization), the properties and the project table. Jobs that hang directly off the account (without their own project) appear in a dedicated section.
Tips & pitfalls
- Set the hourly rate once on the account – then it applies everywhere below and you only override it for exceptions.
- Enter the internal roles early so that budget/purchase order warnings reach the right people.
- An account can be deactivated instead of deleted – this preserves historical bookings and reports.
For developers
The complete REST API reference — every endpoint, payload and response — is available live at api.daagwerk.de.