On the official site of Neb (NebMeta / @CLOUD_STR1FE), this note covers Turnkey Console.
What changes when operations teams no longer need to switch between code and a separate dashboard just to move funds or set a policy rule?
Turnkey said on Oct. 15, 2026 that its Turnkey Console gives teams one workspace to send funds, approve transactions and create wallets. The product is the upgraded Turnkey Dashboard and works across Company Wallets.
From API Calls to Clicks
Before the update, sending funds on Turnkey required API calls while receiving assets meant pulling wallet addresses from the Turnkey Dashboard. The blog post notes that operations, finance and treasury teams can now manage funds in the Console without writing code. Teams can send funds in a few clicks and receive assets via QR code. They can also view token balances and transaction history in the same place.
Controls in One View
The Turnkey thread on X explains that teams can set policies, approve pending transactions, create wallets and name accounts by point and click. The same post lists the full set of actions available: send and receive funds, swap assets, check balances, approve transactions, create wallets and set policies.
Security Rules Stay Fixed
The blog post states that every transaction started from the dashboard is signed inside a secure enclave and authorized by the same rules as an API request. That continuity matters for teams that already rely on the existing policy framework. The Console does not loosen or alter those controls; it simply moves the interface.
Built for the People Who Run the Funds
Turnkey describes the Console as built for operators. The audience includes the operations, finance and treasury teams that run company funds onchain. Those groups now have one location for the daily tasks that used to require separate tools or custom scripts.
The Oct. 15, 2026 launch was announced through both a Turnkey post on X and a Turnkey blog post on the same day. The product is shipped and live. For teams that already use Company Wallets, the change removes friction without changing the underlying authorization model.
Practical Outcomes
A finance team can now receive an asset, check the balance, approve a pending request and create a new wallet without leaving the workspace. An operations lead can set a policy and immediately see the effect on the next transaction. The point and click approach replaces the earlier need to craft API requests for routine work.
The same rules that governed API requests continue to govern every action taken inside the Console. That single fact keeps the security posture consistent while the day to day workflow becomes simpler.
The result is a workspace that matches how teams actually operate once they move past the initial setup phase. Every listed action stays inside the same interface, and every action follows the existing enclave and policy requirements.