User management lets institution administrators control who can access EFI and what they can see. Use this page to invite new team members, adjust their permissions, or remove users who no longer need access.
Inviting a New User
Click Add new to open the invitation form. EFI sends an email to the new user with instructions to set their password and log in.
Fill in the email, first name and last name on the left, then set the permissions on the right. All three are required, the email has to be a valid address, and it cannot already belong to another EFI user. The email address cannot be changed after the invitation.
Setting Permissions
Each permission is a single switch. A new invitation starts with all of them on — turn off the ones the user should not have. At least one must stay on unless Read-only access is enabled, which lets the user see what their permissions grant but never create, edit or delete anything.
- Administrator switches on every other permission; switching it back off leaves the rest as you set them.
- Upload data opens the Data page.
- Institution report opens the Dashboard and your own Ratings report.
- Counterparty reports is limited to the segments ticked beneath it. Switching it on ticks every segment; unticking them all switches the permission off again.
- Case management (read) lets a user open tickets without editing them.
- Case management (write) covers the due date, priority, assignee and progress fields and the audit PDF; adding a screened name to a whitelist is a screening permission, not a case-management one. Without it a user can still open tickets, comment, attach files and close or reopen them. It only applies to tickets owned by their own institution or one in its portfolio.
- Screening — level 1 is the maker role: the user can view customer data and watchlists, propose watchlist changes (in the watchlist settings or straight from a screening hit or ticket) and initiate an Accept, Block or Revert decision on a transaction, but cannot approve anything.
- Screening — level 2 is the checker role: everything level 1 can do, plus approving or rejecting what others propose — watchlist entries, configuration changes (see Monitoring Settings) and, under four-eyes, transaction decisions. Nobody can approve their own submission, even with level 2, so grant it to at least two people.
- Transaction monitoring opens the monitoring pages: the Transaction monitoring alerts tab under Alerts, the monitoring dashboard, settings and jobs pages, and the configuration-change queue on the pending approvals page — so a Screening — level 2 user needs it as well to approve configuration changes. It is offered only to institutions with the Transaction Monitoring product.
- User management lets someone invite and edit users without being an administrator. A user with only this permission reaches the page at
/user-management; it is not in the header menu. On its own it gives no screening rights: such a user sees no decision, approve or reject options unless they also hold level 1 or level 2. - Administrator includes both screening levels and Transaction monitoring.
Permissions that belong to a product your institution does not have are not offered. Any permission a user holds outside this list stays as it is when you save.
Watchlist entry approvals
Every entry on a custom watchlist — whitelist or blocklist — needs two approvals from two different colleagues before it takes effect: three people including whoever proposed it. That covers adding, editing and deleting an entry, and names added to a watchlist from a ticket.
Only users with Screening — level 2 (or Administrator) can be one of the two approvers; Screening — level 1 users can propose entries but not approve them. Nobody can approve their own entry or approve the same entry twice, and a single rejection stops it. Pending entries show their progress as pending (1/2) on the watchlist itself, under screening configuration.
Transaction decision approvals
When Elucidate has switched on four-eyes review for your institution, an Accept, Block or Revert on a screened transaction also needs a second person. A Screening — level 1 or level 2 user proposes the decision; a different Screening — level 2 user approves or rejects it. Nothing is sent to your bank system until it is approved. See Transaction Screening for the full flow.
Managing Existing Users
For users other than yourself, a Manage dropdown offers three actions:
- Edit — Reopen the permissions form to change the user's access
- Change password — Sends a password reset email to the user
- Delete — Permanently removes the user from the institution after confirmation
You cannot manage your own account from this page — this prevents accidentally locking yourself out. Contact another administrator if you need your own permissions changed.