Skip to content

Users and access

This page is for administrators. All screens are under Settings, Users and access.

A person can have several roles. An account without a role sees nothing. The names match those in the role selector of the user management.

Role Purpose Can
Administrator setup and operation everything, including users, companies, payments and deleting. Excluded are the parts that only eelik has: the operations diagnostics with usage and costs and the setup of the fineelik AI
Accountant daily work review and complete invoices, manage vendors, accounts, employees, expenses and travel, create the bank file
Approver business approval approve or reject invoices, expense receipts, trips and the matching conditions of contracts, ask questions
Payment approver second gate before the money approve invoices for payment and the bank file
Employee (expenses) self-service enter their own expense receipts and see only their own
Employee (travel) self-service enter their own trips and see only their own
Submitter submitting documents submit documents on the web and in the app and see only their own, with status and questions. Changes nothing and sees no vendors, master data, users, settings or payments
Viewer read access view invoices, vendors, master data, approvals, payments, companies, settings and users, change nothing. Viewers do not see employees, expenses, trips, the operations page and the handover to the tax advisor
Operator support by eelik operations page and diagnostics, read invoices and settings, manage users (without administrators and operators, not their own roles) and set up the fineelik AI. The operator does not edit invoices

A role only takes effect if the matching module is booked. Without the Approval module there are no approval tasks for invoices; approvers approve contracts with the Contracts module. Without Expenses or Travel the employee roles do nothing, and without Payments there is no payment run. More under Modules: what you need for what.

The accountant approves nothing: neither invoices nor payments nor the bank file. This is intentional. Up to the transfer there are three approvals: the business approval of the invoice, “Approve for payment” for each invoice and the approval of the bank file. Whoever creates a bank file cannot approve it themselves, as long as the four-eyes principle is switched on (see Company settings). It is on by default and can be switched off per company. For the same reason the accountant does not change the contracts’ Invoice matching (default tolerance, automatic approval, maximum amount, sample). Like the Approval rules, only the Administrator may do that, see Contracts.

You do not assign the Operator role by hand. It applies only to eelik and only through Support access for eelik, which you grant for a limited time and can end at any moment. More under Operations and support. Only an administrator manages the accounts of administrators and operators.

The Submitter is for people who only hand in documents: for example the clients of an accounting office, or colleagues who pass on invoices. As their view, give them only the companies they submit for.

  • After signing in they land on My receipts. There they drag documents into the field or select them, and they see the list of their documents with the status: “Being read”, “Being reviewed by accounting”, “Question”, “Done” or “Rejected”. View document opens their file.
  • If accounting asks a question during the review, it appears at the top of My receipts and they answer it right there. In the fineelik app they find it under the account.
  • They do not see other people’s documents, not even in the same company. Vendors, master data, users, settings, payments and the invoice list stay closed to them, and they cannot connect an AI assistant.
  • They do not see the setup assistant, and they do not need a second factor.
  • For clients of an accounting firm there is Invite client: a submitter with access only to the client’s company, language selectable, optionally also approver. See For accounting firms.

Administrator and Accountant (professional users) as well as Employee (travel) and Employee (expenses) are paid. Every account counts once, in its highest tier. Approvers, payment approvers, viewers, submitters, operators and accounts without a role are free.

At the top, each paid tier shows “used of allowed”. If a tier is full, you can neither assign the role nor reactivate a deactivated account of that tier. That is only possible once an account of that tier is deactivated or the licence is extended. Existing accounts keep working. More under Modules: what you need for what.

There are two ways.

  • Invite: Click Add user and enter name and email. Under “Sign-in” choose whether the person signs in With password or With Microsoft, and the language of the invitation. If the four-eyes principle is off in a company and the new person gets an approval right, fineelik asks after the invitation whether to switch it back on.
    • With password: The person receives an email with a link where they set their own password. The link is valid for 3 days.
    • With Microsoft: This works as soon as the organisation is connected. The first sign-in with Microsoft links the account. The invitation is also valid for 3 days.
    • Send invitation: In the account you can send the invitation again at any time. An earlier link expires in the process.
    • Set password: If no email arrives or no email route is set up, assign a password in the account and hand it over in person. The person has to replace it with one of their own at the first sign-in.
  • With Microsoft: Whoever signs in with Microsoft for the first time is created without a role and appears in the list as “Awaiting approval”, and you receive an email. Assign a role and companies, or deactivate the account.

Assign one or more roles to each person and set the view: which companies they see, all companies or a selection. Administrators always see all companies.

The first account of the instance gets the roles Administrator and Approver when it is created. The supplied approval rules go to the Approver role, so the first account sees the first approvals right away. If other people should approve, give them the Approver role and take it away from the first account if needed. The assignment is listed under “Changes to access rights”.

The “Microsoft sign-in” card is always there. If eelik has not yet enabled Microsoft sign-in for your instance, it says “Not set up”. eelik enables it on request.

  1. Open the “Microsoft sign-in” card.
  2. Enter the domain of your Microsoft address.
  3. Sign in once with your own Microsoft account.

Afterwards the sign-in page shows “Sign in with Microsoft”, and only accounts of your organisation get in. If Microsoft requires administrator consent, send the link from the card to your IT (a text to copy is next to it). Everything for your IT is on Microsoft consent.

Colleagues who use a password link Microsoft themselves in the user menu via “Link with Microsoft”. This only works in the first 10 minutes after signing in. After that they sign in again.

With Disconnect on the card you end the connection. Whoever has only a Microsoft account and no password can only get in again once the organisation is connected again.

On the “Sign-in” card you set when fineelik signs people out automatically. This applies to all users of the instance.

  • Sign out after minutes without activity: default 60, 5 to 480 are possible.
  • Maximum session duration in hours: default 12, 1 to 24 are possible.

Two minutes before signing out, a notice with “Stay signed in” appears. Activity means using the mouse, keyboard or touch. Pages refreshing in the background do not count. After the maximum duration a new sign-in is required, even in the middle of work. Shorter values apply immediately, a longer maximum duration from the next sign-in.

Click a row and the drawer of the account opens.

  • Correct name and email: for example after a typo or a new surname. The email is also the sign-in with password and stays unique.
  • Deactivate: ends all sessions. You cannot deactivate your own account, and at least one administrator must stay active. If the person still had approvals assigned to them personally, fineelik names the number. Reassign them.
  • Reset second factor: if someone has lost their phone and has no backup code left. The person then sets it up again.
  • Delete account: only for an account without traces (never signed in, edited nothing, not entered anywhere). Your own account and the first account can never be deleted.
  • Anonymise now: for a deactivated account. Name and email become placeholders; sign-in methods, roles and keys disappear. Documents, approvals and history stay. Without any action from you, fineelik anonymises deactivated accounts after the retention period (default 90 days).

The “Changes to access rights” card shows who changed the roles or companies of a user, and when.

Anyone who signs in with a password and may create payment runs, mark invoices as paid outside, approve invoices for payment, manage users or permanently delete invoices needs it after the trial. This concerns administrators, accountants, payment approvers and the operator. Approvers, viewers, submitters and employees do not need it.

During the trial it is optional. If you have switched from the trial to a paid licence, a period of 14 days applies. After that fineelik is locked for these people until they have set up the second factor. More under Set up a second factor.

For machines (for example the ELO component) you create API keys under Settings, Integrations. See Integrations and the API reference.

To hand over contracts from ELO the key needs the rights agreements.integration_write and agreements.integration_read. They belong only to the Administrator role.