19 errors across 6 companies is one row, not nineteen. Every error carries a fingerprint — a signature of the fault itself — so the same fault in different companies stacks up into a single line with a count. That count is what tells you what to fix first.

This is the one channel that reaches you from a customer's server. They write from Settings → Talk to Projexin support; it arrives here with their version and any error code. You only ever see what they chose to send — never their projects, files or messages.

This is how you reach a customer without email. Your note travels down the same secure check-in the software already makes to us — nothing new is opened, no address is needed. It shows up as a calm banner at the top of the main admin's screen the next time they open Projexin (so, the start of their working day). Only the company's main admin sees it — not their staff. You will see a ✓ here once they have read it.

Marking an order "Paid" issues (or renews) the customer's licence automatically and writes the invoice — nothing else to do afterward. The key is shown to you right here to hand over, and the customer can always find it themselves under My account → Licence once you have. Online card payment is not switched on yet, so every order today is confirmed by you after you've been paid another way.

How it works. Type the person's title, first name and last name and press Create. A private page with their name on it is made at projexin.com/invite/… (the link can't be guessed and isn't found by Google). Copy the link or the ready-made message, or e-mail it from here. When they open the page and ask for a demo, the request lands in Demo requests without any “confirm your e-mail” step — you approve it as usual, and everything that happens is kept in their record here.

These are the extras your customers see under “Anything extra?” when they order. The editions (Standard, Pro, Premium) are fixed; everything you add here — training, extra set-up help, a priority-support month — is yours to define. Give a price in US$, C$ or both: a customer only sees a product that has a price in their currency. Switching a product off hides it without deleting it; orders already placed keep the name and price they had.

The “Update ring” column is where you set who gets updates early. Change it right here, any time. Ring 2 = your volunteers, they get a new version first; Ring 3 = everyone else, they get it last, once it is proven. (Ring 1 is your own demo server, not a customer.) A customer keeps its ring until you change it. Click any row to open that customer's full record — license, billing, bugs and message history.

One person, one file. A demo request, a website account and a Demo register entry for the same person are shown together here. Their stage is how far they got: Demo requested → In a demo → Signed up → Customer (a Customer has a licence or has paid). Open anyone to see everything we hold about them, archive them, or remove them completely.

Work it from the top. The longest-waiting registration is first. No scoring — behavioural signals like time-on-screen need real usage telemetry from live demo installs, which does not exist yet (see the Trials pane). Anything you know about how a demo actually went, type it into that registration's usage note.

The space expires. The record does not. A demo login stops working after seven days and the sample data can then be cleared out — but the entry below stays for good. When somebody rings in November about the demo they took in March, you open their line and carry on from where it stopped instead of starting again.

Income is every paid invoice; expenses are what you type in. Refunded and pending invoices are listed but never counted as income. Canadian and US dollars are never added together — pick the currency at the top if you have both. This is a simple record for you and your bookkeeper, not tax advice.

Site changes are made for you, not from a form in here. Tell your assistant what to change on projexin.com — wording, a picture, the menu, a whole new section — and it edits the site's files directly and ships the update. Nothing on the site can ever reach a customer's installation or their data.

This is the console's own team — not your customers, and not their software users. Add someone here when you need help answering customers or watching the fleet. You choose exactly how much each person can touch.

Who may edit and delete people? The owner always can. For anyone else, press Allow edit & delete next to their name. It covers Customers (edit, archive), Demo requests (edit, erase) and the Demo register (edit, delete). Give it to someone whose role already shows those pages (owner or sales).