Administration overview

These pages are for in-house administrators and partners who set up and maintain invoiceR. They can be technical: setting names, tables and JSON examples appear throughout.

Where is what configured?

invoiceR’s configuration lives in three places.

In the user interface: Administration menu

Users with the right permissions see the Administration entry in the main menu. This is where you maintain everything that changes in day-to-day operation:

• Organization Units: the tree of your tenants. Each organization unit carries its rules: assignment rules, approval rules, escalation rules, import, export and expense options.
• Roles and Users: who may do what. See Permissions.
• Settings: tenant-wide settings, for example under Other Settings.
• Job-Ausführung and Hangfire dashboard: monitor and start background jobs.
• Further entries such as Languages, Audit Logs or Maintenance, depending on permissions.

Note

In the user interface the tree is called Organization Units. In invoiceR practice and older documents it is usually called the tenant. Both mean the same thing: a node in the tree that carries rules, forms and permissions.

In the appsettings.json file

The backend service’s appsettings.json file contains the basic settings such as host names and the database connection. Many invoiceR behaviour settings also take their default value from there. A setting with the internal name App.WorkflowManagement.FourEyeForcer.Priority, for example, reads its default from this section:

{
  "WorkflowManagement": {
    "FourEyeForcer": {
      "Priority": "10"
    }
  }
}

A value stored in the database for a tenant (table dbo.AbpSettings) takes precedence over the default from appsettings.json. After changing appsettings.json, restart the service.

In database tables

Some parts cannot (yet) be maintained in the user interface, only through entries in the configuration tables (schema conf), for example accounting forms, transitions or additional buttons. The pages concerned name the table and give an example.

Caution

Only work in the configuration tables if you know what you are doing, and test the change on a test system first. Some entries are cached and only take effect after a service restart or after the cache is cleared.

Process and permissions

Page	Content
Assignment for accounting	Assignment rules: who does the accounting for a new document
Approvals	Approval rules: who has to approve a document
Approval scripts	Complex conditions for approval rules using a script
Accounting	Accounting forms and behaviour of the accounting step
Accounting fields	Showing and hiding fields, dependencies between fields
Accounting buttons	Additional buttons, for example an Excel import
Transitions	Program logic when moving between two process steps
Manual approval request	Requesting additional approvers directly during accounting
Absences	How absences and deputies work technically
Permissions	Roles, permissions and visibility of other users’ tasks
Expenses	Expense forms, categories and fields
Tooltips	Adding your own help texts to fields
Data editor	Editing master data tables directly in invoiceR

Document intake and operation

Page	Content
Sending and importing e-mail	invoiceR e-mails and document intake by e-mail
Mailbox connection	Connecting mailboxes for document intake
Setting up document capture	Importing documents by upload
Document storage and archive	Where invoiceR stores documents
Recurring jobs	Scheduled background jobs
Users and login	Creating users, logging in with the company account
App registration in Microsoft Entra ID	Preparing login through Microsoft Entra ID
Installation on your own server	Basic installation
Updater	Updating invoiceR
Access from the internet	Access from outside the company network
Maintenance page	Notice page during maintenance work
Database	Structure of the invoiceR database