Account roles
Review the demo roster for buyer, seller, business seller, hub staff, support, trust, finance, and operator responsibilities before live account systems are connected.
Buyer Profiles
- Buyer accounts show saved items, bids, purchases, offers, reports, reviews, delivery preferences, and alert settings.
- High-value bids, pickup release, reports, and appeals can ask for stronger verification state before action.
- Public profile details stay separate from private delivery, identity, support, and security data.
Seller Profiles
- Seller accounts show storefront, inventory, order tasks, return settings, seller rating, response time, and category permissions.
- Seller limits connect to listing quality, support cases, fulfillment history, verification state, and finance readiness.
- Business sellers add team roles, approval flow, bulk edits, finance review, and service commitments.
Hub Staff
- Hub staff see intake tasks, item checks, custody notes, packing proof, pickup windows, release codes, and exception paths.
- Release overrides need item match, order match, staff reason, buyer-facing status, and audit history.
- Hub permissions stay scoped to assigned locations, accepted categories, and active work queues.
Support and Trust
- Support staff see case ownership, documentation needs, response targets, customer notices, and escalation paths.
- Trust reviewers handle restricted items, report patterns, bid integrity, message safety, seller limits, and appeals.
- Private notes, customer messages, and decision history need role boundaries and review reasons.
Finance and Operator
- Finance review covers fee tables, seller statements, payout readiness, refund impact, chargeback review, tax records, and export controls.
- Operators see launch gates, route coverage, service health, policy approvals, rollback posture, and owner decisions.
- Live money movement remains outside this static demo and needs approved services before release.
Role Change Audit
- Role changes need requester, approver, affected user, scope, reason, expiration, rollback path, and customer-safe notice state.
- Temporary access should expire automatically and preserve action history for owner review.
- Launch review should prove every role can do its work while private data remains minimized.
Buyer Account
Bids, purchases, saved searches, reports, reviews, and alerts.
Seller Workspace
Inventory, offers, auctions, orders, handoff tasks, and seller score.
Business Seller
Team access, approvals, bulk operations, finance review, and commitments.
Staff Queue
Support, trust, seller operations, hub issues, evidence, and next actions.
Employee Accounts
Staff roster, role assignments, queue ownership, access boundaries, shifts, training, and deactivation.
Hub Staff
Counter setup, staff roles, custody, pickup release, packing, and events.
Access & Audit
Permissions, staff actions, approvals, privacy boundaries, and launch review.
Account Security
Recovery, device sessions, suspicious activity, role changes, and rollback.
Operator Console
Route coverage, workflows, finance, launch, trust, supply, and hub operations.
Current demo state
Role coverage is represented with guided accounts.
The demo shows buyer, seller, business seller, hub staff, support, trust, finance, and operator responsibilities using seeded profiles and static review paths.
Future platform state
Live roles need enforceable account services.
Launch needs authentication, organization membership, staff roles, scoped permissions, approval records, audit logs, access expiration, customer notices, and owner review.