Sign in at /workspace with your own email and password. The server determines your role and service. Platform and service administrators open the Dashboard; customers and sellers open their conversation inbox. Reloading restores the session after checking it with the server. Remember me on this device keeps login across browser restarts for up to 30 days; unchecked login lasts up to eight hours in this tab. Use this option only on a private device.
The sidebar is available on desktop. On a small screen, use Open navigation; choose a page, press Escape or use Close navigation to close it. Open the header avatar to see your email, name and role, return Home, or Sign out, which revokes the current token. A failed sign-out keeps the session open for retry. Help & guides opens the public documentation in another tab.
The website uses the original blue palette, light surfaces and neutral table headers/row highlights. The console uses compact navigation, white table panels and neutral row actions. Search, refresh and creation actions sit in each directory header. On mobile, wide tables scroll within their panel. Open the avatar menu for account actions; Escape or a click outside closes it. Billing tabs retain their existing functions, with compact invoice summary cards. Status colors keep their existing meanings.
Names and ownership#
| Name in the console | Meaning | Example / technical contract |
|---|---|---|
| Service | A connected application/tenant with isolated accounts, billing, keys and conversations | Shope or Nexzan; service_id |
| Merchants & teams | Stores, sellers or support teams inside one service | A Shope store or Nexzan support team; existing provider_id |
| Accounts | People with their own login/identity and an assigned role | Existing platform_admin, admin, seller, customer role values |
The hierarchy is Platform → Service → Merchant/team → Conversations. A merchant/team is not another tenant and a service is not a seller account. The console uses these business names; integration field names and endpoints retain provider for compatibility. No new merchant ownership layer was created.
| Signed-in role | Scope and menu behavior |
|---|---|
| Platform administrator | Services, Accounts, Merchants & teams and Billing across authorized services; System status is platform-only; choose a service to open an inbox |
| Service administrator | Own Accounts and Merchants & teams; read-only Service details; own Billing, monitoring, audit and integrations under Your service / Administration |
| Merchant / team member | Own merchant/team inbox; no administrator management menus |
| Customer | Own conversations; no administrator management menus |
Service administrators cannot create/edit service registration, platform/service administrators or another service's records. Account menus and dashboard shortcuts use the same role meanings. Server permission checks remain authoritative.
Register and operate a service#
- A platform administrator opens Services → Add service and registers the connected application with a stable ID and name.
- In Accounts → Add account, create a Service administrator for that service. Deliver initial credentials privately; the interface does not email them or provide public signup.
- That administrator opens Merchants & teams → Add merchant or team inside their service, then adds Merchant / team member accounts assigned to it. Customer accounts belong to the service without a merchant assignment.
- Use Integrations for the service's server-side key and identity exchange. Keys belong to a service, not to an individual merchant. Application servers keep keys private and request scoped customer/team tokens.
- Use the inbox for participation/replies; Chat monitoring → Inspect is an audited preview, not joining, replying or marking messages read.
To add a recovery platform administrator, choose Platform administrator in Add account. No Service or Merchant/team assignment is required or submitted. Existing accounts cannot be moved between services. A successful save closes the editor and refreshes the directory; validation failures remain inside the editor.
Dashboard and conversations#
Dashboard reads actual authorized totals for conversations, saved messages, accounts, providers and services. Its seven-day chart counts saved messages by UTC date; zero activity is displayed as zero. These are saved-data snapshots, not delivery receipts, response-time guarantees or hardware monitoring. Switch Daily / Cumulative to view per-day counts or the running total within the same reporting period. The inbox donut shows current open/pending/ resolved shares; zero conversations show an empty ring. Summary cards and the workspace directory open the corresponding conversations, monitoring, accounts, providers or services page. Use Refresh for a new snapshot. Loading and failed requests have explicit states and a Try again action.
Conversations uses the same shared chat component as integrating projects. A platform administrator chooses Conversation service → Open inbox. Service administrators use their own service. Opening another service replaces the platform administrator's scoped token and reconnects the inbox. Select the conversation and Join as admin before replying under your own identity.
Chat monitoring searches server-paginated conversations by search text, status and, for platform administrators, service. Each page has 20 rows. Select Inspect to view participants and the latest 50 saved messages, including cards and image/PDF attachments. File links expire; inspect again to refresh them. Inspection is audited; it does not join the conversation or mark messages read. Open service inbox opens that service's inbox; select the conversation there to reply or load earlier history. The preview's status selector is available only when the current chat session is scoped to the same service; the shared SDK submits the change and the server independently checks permissions.
Accounts, merchants and services#
Accounts, Merchants & teams and Services are separate sidebar pages. Search filters the loaded directory and local pages contain 20 rows. These existing directory APIs return at most 200 authorized records; the screen explicitly states this limit. This search is not an exhaustive server search for larger directories. Monitoring, audit and billing use server pagination separately.
Use Add account, Add merchant or team or Add service to open the creation dialog. Edit opens the existing record in the same dialog. Use Close editor or Escape to cancel; the dialog keeps validation errors visible when saving fails. Enable/disable actions remain in the directory row. Passwords are required for a new account and optional when editing. Saving an account revokes its sessions; editing your own account returns to sign-in. Service and provider IDs remain stable, and existing records cannot move across services. Disabling blocks access without deleting saved history. See the administration guide for password and account rules. Accounts labelled Host-managed identity come from an external application's identity exchange. Only their display name and enabled access can be changed here; their email, password, role, provider and service remain host-managed.
Platform administrators manage all authorized services and create service administrators. Service administrators manage their own merchants/teams and customer/team accounts; Service details is a read-only view of their service. Browser menus do not grant permissions, and every API action is authorized by the server.
Billing#
Billing has Subscriptions, Invoices and Plans views. All amounts are BDT; plans use monthly pricing. The plan form accepts integer minor units: 100 minor units equals BDT 1.00. Empty limits represent unlimited values. Platform administrators create/edit/enable/disable plans. Service administrators can view plans and manage billing only for their own service.
Choose a service and active plan under Start a subscription. Creating a subscription produces a pending subscription and invoice. This alone does not activate service access. Enrollment replaces a service's legacy access with subscription billing, so chat requires an approved invoice afterwards; the form asks for explicit confirmation. The plan chooser loads the first 100 plans; contact the platform administrator if a required plan is absent.
For an open invoice, choose Submit reference, enter the payment method and transaction reference, optionally add a note, and Submit for review. This is a manual record of an externally made payment: the website does not debit an account or verify the payment with a bank. A platform administrator reviews the submitted invoice and explicitly Approves payment or Rejects reference. Approval is the operation that activates or renews the subscription. Check the actual payment independently before approving it.
Request renewal creates a renewal invoice; the request is unavailable while the subscription already has a pending invoice. Cancel asks for confirmation and ends the subscription at its current paid period boundary. No automatic charge or refund is performed. Unpaid access ends immediately, and outstanding invoices are voided when cancelling. An action with an uncertain network result keeps its request identifier for a retry in the same page session; reload the list before retrying after a browser reload. The backend remains authoritative for idempotency, approval eligibility and subscription state.
Audit, integrations and system status#
Audit log lists recorded management, conversation and billing events, 20 per page. Filter by source, exact action and authorized service. Event details reveals the server's safe detail fields. Operator/system events may have no signed-in actor. This view does not edit or delete audit records.
Integrations links to installation guides for Laravel, React/Next.js, Vue and plain HTML. Private packages require the documented registry/repository setup. The provider-credential controls use the separate integration contract; never put a privileged credential into browser code or a public script tag. Documentation links to public setup and user guides.
System status is visible only to platform administrators. It checks the application database connection, storage write access, cache availability and pending/failed queue records. A null count means unavailable, not zero. It does not measure CPU, RAM, disk capacity, worker uptime or WebSocket message delivery.
Troubleshooting and limits#
- An access error means the server rejected the operation. Check the signed-in account and service; do not use another person's token.
- Try again repeats a failed read. Billing forms retain entered values after a failure; inspect the latest invoice/subscription state before a new action.
- Lists can legitimately be empty, including a new service with no messages.
- Latest-message inspection is a bounded preview; use the shared inbox for earlier history and replies.
- Audit records, metrics and application checks are snapshots, not continuous monitoring or a promise of operational health.
বাংলা নির্দেশনা#
নিজের email ও password দিয়ে Sign in করুন। Server আপনার role ও service নির্ধারণ করে; admin হলে Dashboard খুলবে। ফোনে Open navigation চাপলে sidebar পাওয়া যাবে। Accounts, Merchants & teams, Services আলাদা menu; service admin শুধু নিজের service-এর অনুমোদিত কাজ করতে পারে। Directory-তে সর্বোচ্চ ২০০ record আসে; search ওই record-গুলোর মধ্যে কাজ করে।
এখানে Service মানে Shope/Nexzan-এর মতো connected application। তার অধীনে দোকান বা support team হলো Merchants & teams। Service admin-এর কাছে Service details শুধু দেখার জন্য থাকে; অন্য service তৈরি/সম্পাদনা বা platform admin তৈরি করা যায় না। Platform admin Accounts → Add account → Platform administrator দিয়ে recovery admin তৈরি করতে পারে; সেখানে Service লাগে না। Host-managed identity account-এর শুধু নাম ও enabled access বদলানো যায়; email, password, role ও service বাইরের application নিয়ন্ত্রণ করে।
Dashboard-এর সংখ্যা ও UTC দিনের chart database-এ সংরক্ষিত তথ্য দেখায়। Chat monitoring → Inspect দিয়ে সর্বশেষ ৫০টি message দেখা যায়; এই দেখা audit হয়, কিন্তু conversation-এ যোগ দেওয়া বা message read করা হয় না। Reply দিতে Open service inbox চাপুন, conversation বেছে Join as admin করুন। আপনার নিজের admin পরিচয়েই reply যাবে।
Billing-এ subscription তৈরি হলে invoice হবে। বাইরে payment করার পর method ও transaction reference দিন। Subscription billing-এ enrollment করলে পুরোনো legacy access বদলে যায়; invoice approve না হওয়া পর্যন্ত chat চালু থাকে না। Submit for review করুন। এতে service চালু হয় না; platform admin বাস্তব payment যাচাই করে Approve payment করলে চালু বা renew হবে। Reject reference ভুল reference ফিরিয়ে দেয়। Cancel করলে চলতি paid period শেষে subscription বন্ধ হয়; স্বয়ংক্রিয় টাকা কাটা বা refund নেই।
Audit log-এ অনুমোদিত event দেখা যায়। System status শুধু platform admin দেখে; এটি application connection পরীক্ষা করে, server CPU/RAM monitor নয়। কাজ ব্যর্থ হলে error পড়ুন, Try again/Refresh করুন, আর payment action পুনরায় করার আগে invoice-এর সর্বশেষ অবস্থা যাচাই করুন।
Accounts / Merchants & teams / Services-এ নতুন record-এর জন্য Add account / Add merchant or team / Add service চাপুন। Form dialog-এ খুলবে; Edit দিয়ে পরিবর্তন করুন। Close editor বা Escape দিয়ে বন্ধ করুন। Save ব্যর্থ হলে dialog-এর ভিতরেই error দেখা যাবে। Mobile-এ table ডানে-বামে scroll করে সব column দেখা যায়।
Account navigation#
Home and documentation show My account when your session has been verified by the API. Workspace buttons then say Open my workspace and return to the existing workspace without another login. After logout, public navigation shows Sign in. Verification shows Checking account…; an unreachable API shows Reconnect, opening the connection retry screen without discarding the login.
Remembered login/logout updates other tabs, including public pages. Unchecked login stays in its own tab. With browser storage blocked, navigation between home, docs and workspace retains login in that tab; reload or closing the tab requires another login.