Help

Elreda is a business system for electrical installation companies. This overview shows what you see once you have signed in, and where to find help on every page.

Everyone who works in Elreda has an account of their own. What the account may do is governed by permissions, and the role is only a set of default permissions that can be changed one by one.

The customer register keeps track of who you work for: the customer, its contacts and the properties you work in. Everything else in the system will hang on the customer.

The first time, you sign in with a link from your admin. You choose your own password and link a one-time code app to the account. After that you sign in with password and one-time code.

Signing in takes two steps: first email address and password, then a one-time code from the app on your phone. Two steps mean that a password that has gone astray is not enough to get in.

The page My account shows the ways you can sign in, and when each was last used. It lets you see, for example, whether someone else may have used your account.

When a new person is to work in Elreda, you add an account and give the person a link. You never set the password yourself — the person chooses it, and links their own one-time code app.

The account card shows an account: role, status, when the person last signed in, which ways of signing in the account has and which permissions it holds. It is also where you manage the account when someone leaves, forgets their password or loses their phone.

The role gives a default, but the assignment is what the person actually holds. Here you add or remove a permission on an account, for example when an office worker should also be able to read the access log.

A customer is added once and gets a customer number from the system. Only the name and the customer type are required; the rest can be filled in if known.

A contact is someone at the customer you talk to. A property is the building or flat you work in. Both always belong to a customer and are added from the customer card.

The access log shows who has read or changed data, when, and in which role. It is used when something has to be traced afterwards, for example who changed a permission.

The installation health page shows whether the installation is in order: which build is running, whether the database is up to date, and whether the purge of old data has run as it should. It shows no business data.