Please note that this is notes in progress, doesn't mean that i necessarily is the final requirements. It's just a space to park notes or discussions.

2025-12-16 

At the moment the organization setting is stored in a JSON file in an organization blob. Uncertain if this is something that we already have in place. 

An organization that is signing an agreement with EG Flow need to be setup in EG Flow for this to work. Some general setting on the organization need to be setup. What that general information is, is not decided yet.

Initial thought

If this is a SaaS solution there should be EG that administrate some organization settings, and the easiest way for this to handle should be to have a UI where the settings can be changed. Some of the settings that should be possible to change is:

• Organization information: name, organization ID, organization ID in EG Flow
• What type of XML schema to be used
• Priority setup for invoices
• Integration to Kivra
• If EDI invoices should be used
• What template EG Flow should use for different type of invoices.
• Priority setup for dispatches (letter, email, text message)
• What template that EG Flow should use for different dispatches.
• Time for email and text messages to be send

Other settings that is connected to the organization

• Users and permissions