Platform and evolution · Overview
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.
Diagram: owner, staff and client responsibilities
Every person who signs in has one role in a workspace. The role decides which screens they see, which records they can open and what they can change.
The three roles
| Role | What they can do | Typical person |
|---|---|---|
| Owner | Full access: read, write, approve and release. Can invite owners, staff and clients | Business owner |
| Staff | Read and write. No approve and no release. Can invite staff and clients | Sourcing desk team |
| Client | The portal only: its own requests, quotations, orders and invoices | Buyer at your customer |
There is no separate manager role. Manager review is a business perspective, not a role in the software.
Where each role works
| Role | Navigation |
|---|---|
| Owner and staff | Today, Requests, Deals, Suppliers, More |
| Client | The client portal. A client cannot open the staff workspace |
What clients never see
| Hidden from the portal | Why |
|---|---|
| Supplier names | Your supply network stays yours |
| Factory prices and costs | Your cost base stays yours |
| Margins, rebates and earnings | Your deal economics stay internal |
| Other clients’ records | Each client sees only its own company |
These rules are enforced on the server, not only by hiding buttons. See Client portal guide.
Adding people
| Who | How |
|---|---|
| Staff | An owner or staff member invites them by email from workspace administration under More |
| Clients | Create the client company, then invite its buyers to the portal |
| Another owner | Only an existing owner can invite an owner |
Approval
Staff prepare quotations and orders. The owner approves and releases them. This keeps a second pair of eyes on prices and releases. See Sourcing workflow.
The assistant and permissions
Ask PHOENIX works within the role of the person asking. It cannot change records, and it refuses requests to do so. See Ask PHOENIX.
Earlier ClearDesk roles
ClearDesk used its own logins and roles. They belong to the earlier generation and do not apply to PHOENIX Native. See ClearDesk.
Related pages
-
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.
-
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.
-
Getting Started
How a PHOENIX Native workspace is organised and the first steps for an owner: your team, suppliers, clients and your first request.
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.