Your team starts each day from one ranked list and one inbox, and your clients work in a portal that carries your brand and speaks their language. Operators lose time visiting every area of the Console to find their next step, and an institution that wants its investors on a front end of its own has had to build one. 3.2 gives the Console a Dashboard and an Actions inbox, and adds the Investor portal: a separate app for your clients, in your theme, on your domain and in ten languages.
The Console opens on what waits for your team, and the Investor portal puts your brand in front of your clients
Operators, issuers and compliance staff work in the Console. Investors sign in to the Investor portal, accept your terms, fill in the KYC profile you define and follow their holdings there.
- Approvals
- One Actions inbox
- Each write
- Followed until it completes
- Investor portal
- On your domain, in your theme
- Languages
- Ten, Arabic right to left
Before and after
Before 3.2: the Dashboard showed portfolio charts, and the work waiting on a person was spread across approval queues, settings pages and role screens, so a stuck wallet or a failed submission went unnoticed until someone asked. Investors had no front end of their own, so an institution either let them into the operator Console or built a portal itself. The Console read in four languages.
With 3.2: the Dashboard ranks what waits on each person, the Actions inbox gathers the new approvals with the actions it already listed, and the Submissions tray follows every write until it completes. Investors sign in to the Investor portal at your address, in your theme and their language, accept your trading terms and risk disclosure, and fill in a KYC profile whose sections you define. The Console and the portal read in ten languages.
A client onboards in your branded Investor portal, and your team decides from one Actions inbox while the Submissions tray follows each write.
Start the day from what waits on you
The Dashboard ranks everything that waits on the signed-in person, most urgent first, in one “Needs attention” list. Failed operations, approvals, pending launches, KYC profiles awaiting review, low-gas wallets and invitations each become a row, and the queues a person's roles own feed the same list. Operators also see key figures with a seven-day trend, the health of the platform parts they depend on, what changed since their last visit and the views they pinned. Holders see their portfolio, and until their identity is registered, the steps that remain. A Compliance officer signs in and reads “3 KYC profiles await review” at the top, with the link that opens them.
The Actions inbox puts everything that waits for you in one list.
Assets, offerings, trading venues and votes each have an Insights tab with key figures against the previous period, a “Needs attention” section, how the total breaks down, how it moved and where it sits by country. Each holding shows its unrealised gain or loss, total return and 24-hour change, and the portfolio shows its value over the last 7 days. A source the Dashboard cannot read shows as one unavailable row with “Try again”, never as an empty list.
Decide approvals from one inbox
The approvals 3.2 adds, for privileged changes, withdrawals, held deposits, held prices and filings, sit in the Actions inbox next to the settlements, bond payments, custody approvals and KYC updates it already listed. An operator opens “Actions” and sees “Needs you”, the rows they can act on, and “Waiting on others” below it, which names who each row waits on and why. Each action opens in a sheet that explains it before anything is written, and the count on the “Pending” tab, the sidebar badge and the top bar are the same number. Investors have their own “Actions” in the Investor portal. Email goes out only when mail is set up, and only for some kinds, such as held prices, custody allow list reviews, multisig, checker and corporate-action approvals.
A person who works for several subjects picks who they act for under “Working as”. Switching never adds authority, because the on-chain roles still decide what the chosen participant may do. While someone works as another participant, “Portfolio”, “Activity”, search and role checks use that participant's wallets alone. An API call that names the participant in X-Participant reads the same wallets. Signing on a multisig is the one exception: a member keeps opening and approving a multisig through their own seat whoever they work as.
Follow each write until it completes
The Submissions tray follows each write through its phases: “Preparing”, “Awaiting approval”, “Sign in wallet”, “Submitting”, “Confirming on-chain”, “Indexing” and “Complete”. An operator who submits a mint and moves to another page finds it in the tray at the same phase, in every open tab and after a page refresh. Lists, Dashboard tiles and the pending-action count update as the work lands, so nobody refreshes a table to see whether a mint went through. An operator who sees a mistake can undo a write that offers “Undo” while it is still on its way. Undo is offered until the write is submitted, and never while a custody provider holds the request. A request the platform stopped waiting for that can still go through now reads “May still go through” in the Console and Investor portal trays, says to check it before trying again, and shows the platform's reason, instead of “Confirming on-chain”.
Give your clients a portal in your own brand
The Investor portal is a separate app for your investors, with its own sign-in, showing only the areas an investor can use. It sends every platform call to its own address, so it runs on your domain and its session belongs to that domain. It refuses to load inside a frame, so it cannot be embedded in a page of your online banking or another site. An Organisation owner sets the logo, fonts and colours on the Console's Theme page, and the same theme brands the Console, the portal and the browser tab titles. Platform emails use the theme's name, logo and colours, and report PDFs print the organisation's legal name, disclaimer and logo. The owner publishes trading terms and a risk disclosure under “Terms and risk disclosures” in the General settings, ticking “Require participants to accept this version again” for a change that every participant must accept.
An investor signs in at the bank's portal address, sees the bank's logo, accepts the new version and only then reaches Portfolio. The acceptance record holds the participant, the version, the time, the client address and the browser, and Export acceptances downloads it. On a deployment several organisations share, the sign-in page shows the global theme or the default look, because the portal learns the investor's organisation only at sign-in.
Onboard clients through the KYC profile you define
An investor who holds no wallet in the organisation yet sets up in the portal in two steps, “Wallet type” and “Your wallet”. They choose from the custody options your organisation offers investors, such as an embedded wallet, a browser wallet or a managed account, and an investor who brings their own key signs a message that proves it is theirs. The investor then fills in their KYC profile: name, country, national ID and the fields your profile sections add. An administrator builds those sections under “Organisation participants” › Profile sections, choosing each field's type, whether it is required and whether the investor or an identity manager fills it in. A bank adds a tax residency section that the investor completes and an internal risk tier that its identity managers fill in. Every save is a new version. The investor submits it, and an identity manager approves it field by field or uses “Request update”, which opens an action for the investor. The person who submitted a version cannot approve it, and each version stays in the history. Once people have answered a field, its meaning is locked, so the history of what was collected stays readable.
Work in the language your market uses
The Console and the Investor portal read in ten languages: English, German, Arabic, Japanese, French, Dutch, Malay, Indonesian, Thai and Korean. An Organisation owner chooses which ones its people can pick under Languages in the General settings, and English stays on. An investor in Riyadh picks العربية, and the portal opens right to left, with addresses, symbols and amounts kept left to right inside the Arabic text. In the Console, a failure message the platform sends in English keeps its own left-to-right direction too, so its sentence ends where it should. The names of the compliance templates, asset classes and instrument templates DALP ships appear in the chosen language, invitation and approval emails follow it, and amount fields accept digits typed the local way. Names your organisation typed itself, such as its own template names, stay as they were typed.
Upgrading
The Console changes take effect on upgrade. Every organisation starts with all ten languages on, so an owner turns off the ones its people should not see. The Investor portal is its own app: the operator deploys it on a public address of its own, as Deploy browser apps with user sessions describes. Investor sign-in is on for every organisation unless the operator switches it off for the deployment or the organisation opts out, one of the choices when you decide which capabilities your deployment runs. Once an owner publishes trading terms and a risk disclosure, every participant accepts them before trading or withdrawing, and accepts again when the owner requires it for a new version, in the portal and on the Console order ticket.
Why it matters
- Banks: investors deal with the bank on its own domain and under its own brand, and the KYC profile collects the facts the bank's policy asks for.
- Exchanges, CSDs and market infrastructures: participants accept the published trading terms and risk disclosure before they trade, and the acceptance record exports per version.
- Regulators: each acceptance names the participant, the version and the time, and each KYC version names who submitted it and who reviewed it.
- Partners: A partner without a client front end puts the portal in front of its clients in their institution's theme and language, on an address of its own.