Platform and evolution · Technical
How PHOENIX Native works
The building blocks of PHOENIX Native, workspaces, roles, an approval-gated workflow and a client portal, and how this differs from the earlier ClearDesk model.
Diagram: ClearDesk to Native as a staged evolution
PHOENIX Native is one dedicated platform with a staff app, a client portal and an accounting ledger. This page explains the ideas underneath, without infrastructure details.
The building blocks
| Block | What it does |
|---|---|
| Workspace | Holds one company’s requests, suppliers, deals, files and accounts. One workspace never reads another’s records |
| Roles | Owner, staff and client. The role decides what a person can open, change, approve and release |
| Five places | Today, Requests, Deals, Suppliers and More are the owner and staff navigation |
| Workflow with approvals | The deal path from request to invoice. Steps that matter need an approval, and only the owner can approve and release |
| Client portal | Clients see their own requests, quotations, orders and invoices, without supplier names or costs |
| Comments, attachments, history | Each record keeps its comments, files and a history of what happened |
| Notifications | In-app notifications when something a person follows is updated |
| Accounting | Invoices and balanced journals. A posted journal cannot be edited |
| Languages | Six languages, with Arabic shown right to left |
| Assistant | Read-only guidance. It cannot create, change, approve or send anything |
Real PHOENIX Native screen (synthetic demo data)
Diagram: each company works in its own workspace
What stays separate
| Kept apart | How |
|---|---|
| One company from another | Workspace separation |
| Staff from clients | Roles and checks on the server, not only hidden buttons |
| Supplier economics from clients | Supplier names, factory prices, costs, margins and rebates are never sent to the portal |
How the earlier ClearDesk model differed
ClearDesk ran each customer on its own ERPNext and Frappe site. PHOENIX Native is a platform designed for the sourcing workflow, with workspace separation inside it. Existing ClearDesk customers continue through a controlled, staged transition, and the ClearDesk guides remain online as historical pages. See ClearDesk.
Where to go next
| Need | Page |
|---|---|
| The deal path | Sourcing workflow |
| Roles and permissions | Users and roles |
| What clients see | Client portal guide |
| Security | Security |
Related pages
-
Users, roles and permissions
PHOENIX Native has three roles: owner, staff and client. What each can do, what clients never see and how people are added.
-
Sourcing Workflow
How a deal moves in PHOENIX Native, from the client's request to RFQ, supplier quotations, landed costing, pricing, approval, order, quality control, shipping and invoice.
-
Client Portal Guide
What your clients see on the PHOENIX Native portal, how they are invited, what stays hidden from them and how comments, attachments and notifications work.
Still have a question?
Ask the PHOENIX assistant in the chat at the bottom right (read-only guidance), or send us a message. We reply within one business day.
The self-service trial creates a ClearDesk-generation cloud site today. To see PHOENIX Native, talk to us.