3.3 Users

The Users section of the admin panel provides an overview and management interface for all registered users at the investment platform — these are the individuals who can browse published units, connect their wallets, and purchase or hold tokens.

3.3.1 List of users

Each entry in this list represents an investor registered on the platform. This section allows staff to view user details, monitor their token holdings and transaction history, manage verification status, and take necessary administrative actions.

3.3.1.1 Search & Filtering

• Column sorting: Small arrows to the right of the column name can be used to sort by the column content; pressing the icon again will sort in the opposite direction. There are different types of sorting for different columns:
  • alphabetically (A–Z / Z–A) for text columns such as Email and Full name
  • by date (from earliest to latest and back) for Registration time and Last online
  • by status order for the Status column
• Column Filters: each table column supports its own filter or input field to narrow down results:
  • ID – free text input for Users’ IDs.
  • Email – free text input for admins’ email addresses.
  • User wallet – free text input for blockchain wallet address
  • Full name – free text input for admins’ full names.
  • Country – free text input for the user’s selected country
  • Registration time – date range picker for filtering by the registration time.
  • Last online – date range picker for filtering by last online date.
  • Status – dropdown filter for statuses like Active, Blocked, Archived, Invited, or Invitation expired.

3.3.1.2 User Data Table

Each row represents one user and includes the following columns:

3.3.1.3 User Statuses and Actions

In the Tokenizer Estate admin panel, each user has a status that reflects their current state and access level within the platform. There are four distinct user statuses:

1. New

• Assigned automatically when a user leaves their email on the frontend website, or the admin manually creates their account through the admin panel.
• After the user has left their email on the platform, an OTP (one-time password) is sent to their email.
• Before the user enters the verification code from the email, their status is New.
• Can be:
  • Blocked (from the list and detailed view)
  • Archived (from the list and detailed view)

2. Active

• Indicates that the user has completed the initial registration and profile setup by entering the code sent to their email address on the website.
• May or may not be verified.
• Can be:
  • Verified: to perform this action, all fields in the user’s profile must be filled; the admin can verify only from the detailed user view.
  • Blocked: (from the list and detailed view)
  • Archived: An admin restricts user access

3. Blocked

• An admin restricts user access.
• Cannot interact with token-related functionality on the frontend, cannot log into the account.
• Can be:
  • Unblocked (restoring the previous status, typically Active, from the list and detailed view)
  • Archived (from the list and detailed view)

4. Archived

• The user has been permanently removed from the system.
• Can be Unarchived
• All actions are disabled for this status.

These statuses help admins manage the user's journey through registration, verification, activity, and potential deactivation, ensuring clear and consistent system behavior.

3.3.2 Create a new user

Typically, users create their own accounts through the platform. However, administrators can also manually add new users via the admin panel when necessary.

To add a new user manually:

1. Go to the Users section in the left menu.
2. Click the green Create User button in the top-right corner.
3. A modal window titled Create User will appear.

You must fill in the following fields:

• Email – required, used for login (sending an OTP) and communication.
• First name – required, needs to be filled in as in official documents.
• Last name – required, needs to be filled in as in official documents.

Click Create User to complete.

Once created, the new user will appear in the user list with a Not Verified tag. The user can log into the platform using the provided credentials and update their details as needed.

Manual user creation may be useful in these scenarios:

• Adding pre-approved investors or partners ahead of the platform launch.
• Creating test accounts during the onboarding and QA processes.
• Assisting users who encounter registration issues on the frontend.

3.3.3 User Detailed View

From the Users section, click on any user’s email (first column) in the list to open their full profile. The view contains multiple tabs:

• Profile (default active tab)
• Portfolio
• Transactions
• Ticket
• Activity
• Notifications
• System logs

Above the tabs in the right corner of the screen, there is an Actions Block with various buttons, providing the ability to modify the user’s status or verification stage.

3.3.3.1 Actions Block

The Actions Block in the user’s detailed view allows admins to manage user lifecycle operations: block, unblock, verify, and archive users. These buttons dynamically reflect available actions depending on the current status of the user.

On the investor platform, verification is performed by the Sumsub platform, but in the admin panel, admins can verify users manually, predominantly for testing purposes. 

Each action triggers a modal confirmation window with Yes/No options to prevent accidental changes. These appear for:

• Blocking
• Unblocking
• Verifying
• Archiving

3.3.3.2 Profile Tab Overview

The Profile tab contains editable and read-only user information grouped into the following blocks:

• Editable Profile Fields
  • Email — a required field after registration, needs to be formatted as an email (e.g., john.doe@example.com).
  • First name — a required field after verification.
  • Last name — a required field after verification.
  • Wallet address — a required field after verification, and to perform actions with tokens on the platform.
  • Country — a required field after verification, choose one country from the drop-down list with flags.
• Uneditable profile details
  • Verification status — status of verification of this particular user, either verified or not. If a user is verified, they can purchase tokens.
  • Block — shows whether the user is blocked or not.
  • Language — shows the user's currently selected interface language.
  • Registration time — date and time when the user first registered on the website.
  • Verification time — date and time when the user has passed the verification.
  • Last online — date and time when the user was online last.
  • Internal User ID — a unique ID that can be used to quickly identify a user.
• Notifications
  The Notification Preferences section in the user’s detailed profile provides granular control over how and where the user receives updates related to platform activities. It is displayed as a matrix of notification categories versus delivery channels, enabling administrators to view and manage notification preferences on a per-user basis.

There are several categories of notifications:

1. System emails (required)
   • Includes: sign-in codes, password changes, purchase confirmations, and compliance-related messages (e.g., KYC/AML status updates).
   • Delivery: Both platform and email required.
2. Payouts & earnings
   • Includes rent accruals, payout notifications, and earnings report availability.
3. Marketplace updates
   • Alerts for new property listings, price changes, and secondary market activity.

Checkboxes allow toggling each category’s delivery method (platform/email). Selections are saved per user and persist across sessions. All the permissions can only be defined by users themselves on the investor backoffice side.

• UTMs
  • This panel displays the UTM tracking information associated with a user session or registration, typically captured from the URL parameters during initial access to the platform. These parameters are essential for marketing attribution and campaign performance analysis.

After successful verification user can only edit their mobile number or country at the investor backoffice; other fields are locked. To edit them user will need to contact the support of the website, and the admin can assist them by editing the user’s profile via the admin panel.

After the email, if the first or last name was modified, the user will need to verify their account again. Use the Edit Profile button to apply and save changes.

3.3.3.3 Portfolio Tab Overview

The Portfolio tab of the user's detailed view provides a visual and analytical summary of the user's investment activity on the platform.

Main Metrics at the Top:

• Portfolio balance — the total current value of all units the user has invested in.
• Projected annual value growth — an estimate of expected portfolio appreciation over the course of a year.
• Units — the total number of tokenized property units the user holds.

Charts and Visualization:

• Balance history graph — a time-based line graph that displays the user’s portfolio balance growth across months.
• Tokens distribution pie chart — shows how the user's tokens are spread across different real estate units listed on, the platform.
  • Each slice corresponds to a specific unit and is labeled with its name and total token value.

Units Section (bottom half):

• Each unit card contains:
  • Name of the real estate unit
  • Date and amount of the first and most recent transaction
  • Total investment made into the unit
  • Number of tokens owned
  • Growth percentage
• These cards help administrators and analysts understand user preferences and how diversified their portfolio is.

Empty State: If a user has not made any investments yet, the portfolio tab displays an empty state message: “The user has not started trading yet”. No units, charts, or projections are shown in this case.

This tab is especially useful for tracking investor behavior, engagement, and estimating their lifetime value within the platform.

3.3.3.4 Transactions Tab Overview

The Transactions tab under the user's profile provides a comprehensive list of all token transactions associated with that specific user. This view allows admins to review, track, and validate both payment activity and token delivery status for each transaction.

• Column sorting: Small arrows to the right of the column name can be used to sort by the column content; pressing the icon again will sort in the opposite direction. There are different types of sorting for different columns:
  • alphabetically (A–Z / Z–A) for text columns such as From user or To user
  • by date (from earliest to latest and back) for Transaction time
  • by status order for the Status column
• Column Filters: each table column supports its own filter or input field to narrow down results:
  • Unit- free text input for Units'
• From user - free text input for senders' email addresses, full names, or IDs.
• From address - free text input for senders' blockchain wallet address.
• To user - free text input for recipients' email addresses, full names, or IDs.
• To address - free text input for recipients' blockchain wallet address.
• Type - dropdown with a list of transaction types.
• Payment transaction hash – free text input for blockchain hash of the payment operation.
• Tokens transaction hash – free text input for the hash for the actual token issuance or transfer.
• Transaction time  – date range picker for filtering by the timestamp of the blockchain event.
• Status – dropdown filter for statuses like Pending, Completed, Failed

Each transaction entry includes:

At the bottom of the table:

• Rows per page selector – Adjusts how many entries are displayed (default is 10).
• Navigation controls – Allow browsing through multiple pages of history.

This tab is especially useful for:

• Auditing user activity
• Troubleshooting failed transactions
• Verifying payment/token delivery sync across systems

3.3.3.5 Tickets Tab Overview

The Tickets tab provides a chronological history of the user’s communication with support, giving administrators a transparent record of all user requests.

• Column sorting: Small arrows to the right of the column name can be used to sort by the column content; pressing the icon again will sort in the opposite direction. There are different types of sorting for different columns:
  • by date (from earliest to latest and back) for Time opened, Time resolved
  • by status order for the Status column
• Column Filters: Each table column supports its own filter or input field to narrow down results:
  • ID – text input for ticket IDs.
  • Type – dropdown with a list of issue types.
  • Messages – dropdown with options: unread and read.
  • Status – dropdown with a list of statuses.
  • Time opened – date range picker.
  • Time resolved – date range picker.

Each row includes:

At the bottom of the table:

• Rows per page selector – Adjusts how many entries are displayed (default is 10).
• Navigation controls – Allow browsing through multiple pages of history.

3.3.3.6 Activity Tab Overview

The Activity tab provides a chronological log of key user actions performed within the system, offering administrators a transparent history of user behavior. This includes registrations, logins, updates, and identity verifications.

• Column sorting: Small arrows to the right of the column name can be used to sort by the column content; pressing the icon again will sort in the opposite direction. There are different types of sorting for different columns:
  • alphabetically (A–Z / Z–A) for text columns such as Action.
  • by date (from earliest to latest and back) for Time
• Column Filters: Each table column supports its own filter or input field to narrow down results:
  • ID – free text input for actions' ID.
  • Time – date range picker for the time when the action occurred.
  • Action – Dropdown with a list of actions

Each row includes:

At the bottom of the table:

• Rows per page selector – Adjusts how many entries are displayed (default is 10).
• Navigation controls – Allow browsing through multiple pages of history.

Typical use cases include:

• Tracking suspicious activity (e.g., multiple failed logins from the same IP).
• Monitoring successful user onboarding.
• Auditing profile changes for compliance.

3.3.3.7 Notifications Tab Overview

The Notifications tab provides admins with a centralised interface to manage and track all notifications sent to a specific user. This includes system messages, investment alerts, payout confirmations, platform news, and more.

The Notifications tab displays all messages sent (or pending) for the selected user.

• Column sorting: Small arrows to the right of the column name can be used to sort by the column content; pressing the icon again will sort in the opposite direction. There are different types of sorting for different columns:
  • alphabetically (A–Z / Z–A) for text columns such as Headline.
  • by date (from earliest to latest and back) for Timestamp
• Column Filters: Each table column supports its own filter or input field to narrow down results:
  • ID – free text input for the Notifications' ID.
  • Timestamp – date range picker to display activities only within that period.
  • Category – dropdown filter for notifications' category.
  • Unit – free text input for the name of the real estate asset involved.
  • Headline – free text input for the title of the message
  • Text – free text input for message body.
  • Status – dropdown filter for statuses.

Each row includes:

At the bottom of the table:

• Rows per page selector – Adjusts how many entries are displayed (default is 10).
• Navigation controls – Allow browsing through multiple pages of history.

Click the Create Notification button to open the modal window for composing a message. The following fields must be filled out:

1. Category (Dropdown)
   Choose from predefined categories like:
   • System
   • Unit updates
   • Payout & Earnings
   • Marketplace updates
   • Platform News
2. Notification Title (Text)
   Appears as the headline in the notification.
3. Notification Description (Textarea)
   The main body of the message. Rich HTML is supported for formatting purposes, but malformed HTML may render visibly in the message (e.g., <!DOCTYPE html> artifacts), so input should be validated and sanitized if entered manually.
4. Create Notification (Button)
   Dispatches the message to the user. Once sent, the status will update accordingly (e.g., from Pending to Sent).

3.3.3.8 System Logs Tab Overview

The System Logs tab provides a detailed, chronological record of administrative actions and system events performed in relation to a specific user. It serves as a transparent audit trail that allows administrators to monitor user-related changes, identify potential risks, and maintain compliance with security and governance policies.

• Column sorting: Small arrows to the right of the column name can be used to sort by the column content; pressing the icon again will sort in the opposite direction. There are different types of sorting for different columns:
  • alphabetically (A–Z / Z–A) for text columns such as Performed by.
  • by date (from earliest to latest and back) for Time.
• Column Filters: Each table column supports its own filter or input field to narrow down results:
  • ID – free text input for the log's ID.
  • Time – date range picker to display activities only within that period.
  • Performed by – free text input for an admin's Full name, Email, or ID (depending on the admin's permissions) who triggered this action.
  • Action – dropdown filter for type of action (e.g., Permissions Update).
  • Type – dropdown filter to choose the type of action (Regular, Alert, System).
  • IP Address – free text input for IP address.
  • Info – free text input for searching across additional details included in activity metadata.

Each row includes:

At the bottom of the table:

• Rows per page selector – Adjusts how many entries are displayed (default is 10).
• Navigation controls – Allow browsing through multiple pages of history.