Ask AI

Settings tab

🟥 Make project-specific settings

🟥

This text is a reference. What types of text are there?

The "Settings" tab is the place to individually configure a project in Leadtime. These settings relate not only to task management, but also to documentation, invoicing and the distribution of roles in the team. Settings is divided into 5 areas via a vertical menu.

Basic settings of a project

The "Basic settings" menu item is the starting point. All basic information and project-related options can be found here in a clearly structured form.

Page structure

Notion image

The page has a two-column structure:

  • Left: A vertical menu with all available settings areas.
  • Right: The currently selected area - in this case the basic settings - in the form of a clearly structured form.

Project status

The current status of the project can be selected at the top. This is particularly relevant for individual projects, as they typically go through different phases - from the sales phase to implementation and acceptance.

Example status values:

  • Sales
  • Implementation
  • Billing
  • Completed

The available project statuses can be adjusted in the workspace settings under Project settings > Project phases.

Deadline

The Deadline field defines the project deadline - i.e. the planned delivery date or the desired handover date. This information is used in several places in the system, for example for planning and in quotation and billing documents.

Basic information

Basic project details can be maintained here:

  • Icon - for visual recognition of the project
  • Name - the official project name
  • Type - choice between:
    • Single project (clearly defined scope, deadline, budget)
    • Ongoing project (ongoing support, e.g. support)
  • Value group - classification according to economic importance, e.g:
    • Direct value-adding activity (typical for customer projects)
    • Indirect activity (e.g. internal product development)
  • Category - used to group similar projects (e.g. "Setup", "Web development"). Categories can be defined in the workspace settings under project categories.
  • Project description - a longer free text to describe the aim, content and scope of the project. This description serves as a "preamble" in offer documents and the specifications.

Task options

Notion image

The behavior of the integrated ticket system for this project is controlled here.

Activate express quotes

A toggle button activates or deactivates the option to send express quotes to customers from tasks. The feature is particularly suitable for support or change requests with a clear scope.

Task types

All task types that should be available in the project can be activated in this field. Examples

  • Feature
  • Bug
  • management
  • Security requirement

Activities

Here you define the work activities to which times can later be booked. Typical activities:

  • Development
  • Research
  • Training
  • testing
  • Project management

Project responsibility

A standard person responsible can be defined here - such as a project manager or account manager. The person entered is named in automatically generated documents (such as contracts or specifications) and linked to the project throughout the system.

Members and access rights

In the last section, you control who has access to the project.

External access

A toggle button determines whether guest users (e.g. customers) should also have access to the project. If access is activated, external users with the appropriate authorizations can work on tasks via the customer portal.

Internal members

Projects can either:

  • be assigned toindividual users or
  • entire teams to make it easier to control access.

Document settings

In the Settings tab of a project, under the Document settings menu item, you will find several options that determine how automatically generated documents (such as specifications, quotations or contracts) are to be formatted and structured in the respective project. These settings are project-specific and overwrite - if desired - the default values that have been stored for the entire organization.

Notion image

Title page

Here you specify whether all documents generated in this project should contain a title page. There are three options to choose from:

  • Yes: All documents receive a title page.
  • No: No title page is generated.
  • Use organizational standard: The central standard stored in the organization settings is used.

Table of contents

As with the title page, you can also specify here whether an automatic table of contents is inserted:

  • Yes: The table of contents is generated by default.
  • No: No table of contents in the document.
  • Use organization standard: The organization setting is adopted.

Heading style

Notion image

The Heading style option determines how headings should be numbered within the documents - an important detail, especially for structured, longer documents with many sections. The following options are available:

  • Without numbering: The headings (H1, H2, H3...) appear without numbers.
  • Sequential numbering from the first level: Each H1 is numbered as "1.", "2.", "3." etc., followed by nested numbering such as "1.1", "1.1.1" etc.
  • Sequential numbering from second level: The top heading level (H1) remains unnumbered. Numbering starts at H2.
  • Sequential numbering from second level with § prefix: As above, but with § character before each number (e.g. § 1.1).

💡 Important: This automatic numbering is particularly useful because documents in Leadtime often contain conditional sections that are shown or hidden depending on certain form responses. Only dynamic numbering can guarantee a consistent and logical structure - regardless of which sections are visible in the specific case.

Standard contact person

In this field, you can enter a person from the customer organization as the default contact person. This person is automatically entered as the recipient or addressee in all generated documents - e.g. in the quotation, specifications or contract. This saves time during creation and ensures consistent communication.

General billing settings

In the General billing settings submenu, you define how the selected project is to be billed in Leadtime. These are central default settings that affect the invoicing for this project - in particular with regard to mixed or separate invoices and the selection of the project version to be used for invoicing.

Notion image

Invoice settings

Here you define the basic logic according to which invoices are created:

  • Mixed invoices
    • If activated, different items - such as tickets, project work or product prices - can be combined in a joint collective invoice.

  • Split invoices
    • With split invoices, each billing unit - e.g. an express offer, a product or a subscription - is handled in a separate invoice. This creates more separation and transparency for more complex projects with many billing-relevant modules.

Standard invoice recipient

In this field, you specify to whom invoices should be addressed by default. This is a person from the organization to which the project is linked. This contact is automatically pre-assigned when the invoice is created, but can be overwritten manually if required.

Project version to be invoiced

A particularly important point for individual projects:

As several quotation versions are often created during project preparation, you must define which of these versions forms the basis for invoicing. Leadtime offers you two separate selection options for this:

  • Main billing version (single project billing)
    • Determines which version of the project is used as the basis for invoicing for the project . This version contains all components, items and expenses that have been contractually agreed and are now to be invoiced.

  • Subscription billing version
    • If the project contains products that trigger a recurring payment (subscription) - e.g. SaaS products or hosting packages - you can optionally define a separate project version on the basis of which these subscriptions are billed. This enables stable subscription invoicing even if the project status changes continuously.

Subscription billing

Notion image

Subscription billing in Leadtime makes it possible to efficiently manage regularly recurring services within a project - ideal for SaaS products, maintenance contracts or modular service packages. All settings for this can be found in the Settings > Subscription billing tab of a project.

Two subscription types that can be created manually

Leadtime offers two options for configuring subscriptions individually and freely. You can create these via the "Add new" button in the top right-hand corner.


1. fixed-price subscriptions

Notion image

A fixed-price subscription defines a recurring fixed amount that is billed at a certain interval (e.g. monthly).

Typical application: Monthly basic fee for hosting, support or license.

Configurable fields:

  • Title: e.g. maintenance fee
  • Frequency: e.g. monthly, quarterly, annually
  • Price: Fixed amount
  • Active from / to: Term of the subscription

Example:

A customer pays €100 every month from 01.11.2024 to 30.11.2025.

2. variable priced subscriptions

Notion image

With this variant, a price is charged per unit - for example, per active user, per API access or per module used. The unit is entered manually during billing.

Typical application: User or transaction-based SaaS packages.

Configurable fields:

  • Title: e.g. price per user
  • Frequency: e.g. monthly
  • Price per unit: e.g. €15
  • Active from / to: Term

Note: The unit (e.g. number of users) is specified manually for each invoice.

Automatically generated subscriptions from products

In addition to manually maintained subscriptions, automatically generated subscriptions can also appear. This happens when you add a product from the product catalog to a project that has a subscription pricing model. In this case, the subscription is automatically entered in the third block of this page.

Advantage:

If you have clearly defined your services in the product catalog, there is no need to enter them manually. The pricing logic of the product is automatically adopted.

Start of billing for individual projects

Important: For individual projects, the billing of subscriptions - whether created manually or generated automatically - only begins from the time the project has reached the "Billing" status. This ensures that no premature subscriptions are invoiced during the project term.

Summary of subscription types

Type
Basic
Attachment
Billing start
Fixed-price subscription
Fixed amount
Manual
From project status "Billing"
Variable subscription
Price per unit
Manual
From project status "Billing"
Subscription from product catalog
Price logic from product definition
Automatic
From project status "Billing"

Payments on account

In the Advance payments submenu, you can manage payments that are invoiced before the final project billing - such as down payments or partial invoices, which are common for larger projects.

Notion image

What are advance payments?

For extensive projects, it is often useful (and common) to agree interim payments with the customer. For example:

A project costs €20,000. It is agreed that 50% of the sum - i.e. €10,000 - will be due as an advance payment at the start of the project.

The advance payments module is designed precisely for scenarios like this.

How do advance payments work in Leadtime?

Notion image

When you add a new advance payment, you create an entry with:

  • Title (e.g. "50% advance payment")
  • Description (e.g. "50% of the agreed project amount is due in advance upon conclusion of the contract")
  • Amount (e.g. € 2,000)

This payment then appears as a separate item in the project view under advance payments.

At the same time, a corresponding invoice is automatically prepared in the billing area. The recorded payment is deducted from the subsequent total invoice - it is therefore included directly in the final invoice.

This ensures that:

  • the customer only pays the remaining amount,
  • the receipt of payment is correctly documented
  • and no manual invoice correction is necessary.
Did this answer your question?
😞
😐
🤩