SME banking app · 2026

Inviting and managing team members in business banking

A user management module for companies where more than one person works in the bank app: inviting new users, editing, blocking and removing them, with multi-signature approval built into every action.

Role

UX/UI Designer — Mobile, Web

Team

Product owners, analysts

Status

Designed & handed off · not shipped

SME banking app · 2026

Inviting and managing team members in business banking

A user management module for companies where more than one person works in the bank app: inviting new users, editing, blocking and removing them, with multi-signature approval built into every action.

Role

UX/UI Designer — Mobile, Web

Team

Product owners, analysts

Status

Designed & handed off · not shipped

SME banking app · 2026

Inviting and managing team members in business banking

A user management module for companies where more than one person works in the bank app: inviting new users, editing, blocking and removing them, with multi-signature approval built into every action.

Role

UX/UI Designer — Mobile, Web

Team

Product owners, analysts

Status

Designed & handed off · not shipped

Two mobile banking screens: the SME home screen with an operation to authorise, and the users list with roles and statuses

In short

Problem

Companies couldn’t add or manage users in the app themselves; bank employees had to do it for them.

What I did

Designed the whole user module on mobile (add, edit, delete, block, unblock) and adapted it for the corporate web app.

Result

Approved by the product owner and handed off to development. The module was later deprioritized, so it didn’t ship.

In short

Problem

Companies couldn’t add or manage users in the app themselves; bank employees had to do it for them.

What I did

Designed the whole user module on mobile (add, edit, delete, block, unblock) and adapted it for the corporate web app.

Result

Approved by the product owner and handed off to development. The module was later deprioritized, so it didn’t ship.

In short

Problem

Companies couldn’t add or manage users in the app themselves; bank employees had to do it for them.

What I did

Designed the whole user module on mobile (add, edit, delete, block, unblock) and adapted it for the corporate web app.

Result

Approved by the product owner and handed off to development. The module was later deprioritized, so it didn’t ship.

01 · Context

The bank’s mobile app has a retail profile and an SME profile, and people can switch between them. Companies with more than one user couldn’t add or manage people on their own: bank employees did it for them in their internal tools. The goal was to let companies handle it themselves in the app, which also takes work off the bank’s staff. The module had to follow the company’s approval rules (multi-signature) and legal checks of who can represent the company. Time and resources were limited, so we kept only what was essential for the first release.

01 · Context

The bank’s mobile app has a retail profile and an SME profile, and people can switch between them. Companies with more than one user couldn’t add or manage people on their own: bank employees did it for them in their internal tools. The goal was to let companies handle it themselves in the app, which also takes work off the bank’s staff. The module had to follow the company’s approval rules (multi-signature) and legal checks of who can represent the company. Time and resources were limited, so we kept only what was essential for the first release.

01 · Context

The bank’s mobile app has a retail profile and an SME profile, and people can switch between them. Companies with more than one user couldn’t add or manage people on their own: bank employees did it for them in their internal tools. The goal was to let companies handle it themselves in the app, which also takes work off the bank’s staff. The module had to follow the company’s approval rules (multi-signature) and legal checks of who can represent the company. Time and resources were limited, so we kept only what was essential for the first release.

02 · Adding a user

The process is split into steps so a long form doesn’t feel overwhelming: personal details → documents (only when needed) → role and account access → limits → summary.

02 · Adding a user

The process is split into steps so a long form doesn’t feel overwhelming: personal details → documents (only when needed) → role and account access → limits → summary.

02 · Adding a user

The process is split into steps so a long form doesn’t feel overwhelming: personal details → documents (only when needed) → role and account access → limits → summary.

Documents only when they're needed

Representatives and registered proxies are usually listed in official registers (KRS, CEIDG), so the system checks them automatically and asks for documents only if the check fails. Attorneys aren’t in these registers, so they always upload a power of attorney. This way most people never see this step.

Documents only when they're needed

Representatives and registered proxies are usually listed in official registers (KRS, CEIDG), so the system checks them automatically and asks for documents only if the check fails. Attorneys aren’t in these registers, so they always upload a power of attorney. This way most people never see this step.

Documents only when they're needed

Representatives and registered proxies are usually listed in official registers (KRS, CEIDG), so the system checks them automatically and asks for documents only if the check fails. Attorneys aren’t in these registers, so they always upload a power of attorney. This way most people never see this step.

Two steps of adding a user: documents confirming power of attorney, and uploading documents confirming authorisation

Role and account access on one screen

• Each role (Administrator, Editor, Viewer) has a one-line description right in the picker, so it’s clear what the person will be able to do • Accounts are grouped, with “Select all” for companies that have many of them • Automatic access gives the user every new account the company opens. Without it, an admin would have to edit every user by hand each time a new account appears — and edits often need multi-signature approval

Role and account access on one screen

• Each role (Administrator, Editor, Viewer) has a one-line description right in the picker, so it’s clear what the person will be able to do • Accounts are grouped, with “Select all” for companies that have many of them • Automatic access gives the user every new account the company opens. Without it, an admin would have to edit every user by hand each time a new account appears — and edits often need multi-signature approval

Role and account access on one screen

• Each role (Administrator, Editor, Viewer) has a one-line description right in the picker, so it’s clear what the person will be able to do • Accounts are grouped, with “Select all” for companies that have many of them • Automatic access gives the user every new account the company opens. Without it, an admin would have to edit every user by hand each time a new account appears — and edits often need multi-signature approval

Role and account access screen with role descriptions, grouped accounts and automatic access
Limits step with transfer initiation and approval limits
Summary of the new user before sending the invitation

03 · The invitation

The new user gets a code by e-mail and text message. The code is valid for 7 days. The same code is shown to the inviter, so they can pass it on personally. Two days before it expires, the invitation’s status changes, a banner appears, and both the inviter and the invited person get a notification. Expired invitations are removed, and the inviter is notified when the new user registers.

03 · The invitation

The new user gets a code by e-mail and text message. The code is valid for 7 days. The same code is shown to the inviter, so they can pass it on personally. Two days before it expires, the invitation’s status changes, a banner appears, and both the inviter and the invited person get a notification. Expired invitations are removed, and the inviter is notified when the new user registers.

03 · The invitation

The new user gets a code by e-mail and text message. The code is valid for 7 days. The same code is shown to the inviter, so they can pass it on personally. Two days before it expires, the invitation’s status changes, a banner appears, and both the inviter and the invited person get a notification. Expired invitations are removed, and the inviter is notified when the new user registers.

Decision 01

Resend button left for post-MVP

A “Resend invitation” button was considered, but we kept it for post-MVP to ship the core flow with minimal effort.

Decision 01

Resend button left for post-MVP

A “Resend invitation” button was considered, but we kept it for post-MVP to ship the core flow with minimal effort.

Decision 01

Resend button left for post-MVP

A “Resend invitation” button was considered, but we kept it for post-MVP to ship the core flow with minimal effort.

Confirmation that the invitation was sent, with the invitation code
Invitation details with status and code

04 · Users list and statuses

The list shows the essentials first: who the user is, their role and status — Active, Invitation sent, The invitation will expire soon, Awaiting approval 1/3, In progress or Blocked. “Awaiting approval” is yellow, so approvers can see it still needs them.

Users list with role tags and statuses: awaiting approval, invitation expiring soon, active, in progress and blocked

04 · Users list and statuses

The list shows the essentials first: who the user is, their role and status — Active, Invitation sent, The invitation will expire soon, Awaiting approval 1/3, In progress or Blocked. “Awaiting approval” is yellow, so approvers can see it still needs them.

Users list with role tags and statuses: awaiting approval, invitation expiring soon, active, in progress and blocked

04 · Users list and statuses

The list shows the essentials first: who the user is, their role and status — Active, Invitation sent, The invitation will expire soon, Awaiting approval 1/3, In progress or Blocked. “Awaiting approval” is yellow, so approvers can see it still needs them.

Users list with role tags and statuses: awaiting approval, invitation expiring soon, active, in progress and blocked

05 · Multi-signature approval

When a company needs several approvers, sending an invitation becomes a separate operation with its own details screen: what it is, who has to approve it and where each approver stands. Approvers find it in a notification or in “Operations to authorise” on the home screen, and it’s tracked in Authorised operations under Pending, Approved and Rejected. Approval needs everyone, but one rejection is enough to cancel the whole operation.

05 · Multi-signature approval

When a company needs several approvers, sending an invitation becomes a separate operation with its own details screen: what it is, who has to approve it and where each approver stands. Approvers find it in a notification or in “Operations to authorise” on the home screen, and it’s tracked in Authorised operations under Pending, Approved and Rejected. Approval needs everyone, but one rejection is enough to cancel the whole operation.

05 · Multi-signature approval

When a company needs several approvers, sending an invitation becomes a separate operation with its own details screen: what it is, who has to approve it and where each approver stands. Approvers find it in a notification or in “Operations to authorise” on the home screen, and it’s tracked in Authorised operations under Pending, Approved and Rejected. Approval needs everyone, but one rejection is enough to cancel the whole operation.

Flow diagram of multi-signature approval: the operation is approved only when every approver accepts, and one rejection cancels it

Decision 02

Operation, invitation and user are three separate things

The operation approves the invitation. The invitation exists only once it’s sent. The user exists only after accepting the invitation and completing onboarding. Keeping them apart made every status unambiguous.

Decision 02

Operation, invitation and user are three separate things

The operation approves the invitation. The invitation exists only once it’s sent. The user exists only after accepting the invitation and completing onboarding. Keeping them apart made every status unambiguous.

Decision 02

Operation, invitation and user are three separate things

The operation approves the invitation. The invitation exists only once it’s sent. The user exists only after accepting the invitation and completing onboarding. Keeping them apart made every status unambiguous.

Operation details for approvers with required signatures, next to the list of authorised operations

06 · Managing users

The same logic works for editing, deleting, blocking and unblocking.

06 · Managing users

The same logic works for editing, deleting, blocking and unblocking.

06 · Managing users

The same logic works for editing, deleting, blocking and unblocking.

Swipe actions

Delete and block by swiping in the list, reusing a pattern already in the app.

Limited editing

Only the role, permissions and account access can change. Personal details were already verified when the user was added.

Changes-only summary

The edit summary shows only what changed, to focus attention on it and keep the screen short.

Combined statuses

Active + In progress, with a banner on the user card that links to the pending operation.

Swipe actions

Delete and block by swiping in the list, reusing a pattern already in the app.

Limited editing

Only the role, permissions and account access can change. Personal details were already verified when the user was added.

Changes-only summary

The edit summary shows only what changed, to focus attention on it and keep the screen short.

Combined statuses

Active + In progress, with a banner on the user card that links to the pending operation.

Swipe actions

Delete and block by swiping in the list, reusing a pattern already in the app.

Limited editing

Only the role, permissions and account access can change. Personal details were already verified when the user was added.

Changes-only summary

The edit summary shows only what changed, to focus attention on it and keep the screen short.

Combined statuses

Active + In progress, with a banner on the user card that links to the pending operation.

Decision 03

One operation model for all five actions

Inviting, editing, deleting, blocking and unblocking all work the same way. Once people learn how approval, statuses and rejection work, everything behaves predictably.

Decision 03

One operation model for all five actions

Inviting, editing, deleting, blocking and unblocking all work the same way. Once people learn how approval, statuses and rejection work, everything behaves predictably.

Decision 03

One operation model for all five actions

Inviting, editing, deleting, blocking and unblocking all work the same way. Once people learn how approval, statuses and rejection work, everything behaves predictably.

User card with management actions, next to the edit summary that shows only the changes

07 · Corporate web app

The bank also has a separate web app for corporate clients. I adapted the same process to it: the logic stays the same — steps, multi-signature, statuses — but what takes two screens on mobile fits into one on desktop.

07 · Corporate web app

The bank also has a separate web app for corporate clients. I adapted the same process to it: the logic stays the same — steps, multi-signature, statuses — but what takes two screens on mobile fits into one on desktop.

07 · Corporate web app

The bank also has a separate web app for corporate clients. I adapted the same process to it: the logic stays the same — steps, multi-signature, statuses — but what takes two screens on mobile fits into one on desktop.

Corporate web app: adding a user on one screen and the approval screen

08 · Results

The product owner reviewed and approved the solution, and it was handed off to development. The bank later deprioritized the module due to limited capacity, so it wasn’t released.

08 · Results

The product owner reviewed and approved the solution, and it was handed off to development. The bank later deprioritized the module due to limited capacity, so it wasn’t released.

08 · Results

The product owner reviewed and approved the solution, and it was handed off to development. The bank later deprioritized the module due to limited capacity, so it wasn’t released.

© 2026 Dzmitry Shkutnik

Designed in Figma · Built in Framer