TeranoveCore is made of a handful of simple pieces that fit together. Here's what each one is — not how it's built inside, just what it does for you.
A function is one specific thing the software can do — record a payment, schedule a work order, log a reading. Functions are the smallest unit of capability; everything you can do in TeranoveCore is a function somewhere.
There are two sides. Customer functions — messaging a company, booking a work order, paying an invoice, managing a connection — are standard on every account. Employee functions run the work: every company starts with the Universal System Functions, then adds specialised ones by buying subfields.
For customers — every profile has the core functions for dealing with any company it's connected to:
For companies — every company starts with the Universal System Functions before it adds anything. Field-independent operational basics:
On top of that baseline layer, the specialised employee functions are organised into fields (broad areas like Accounting or Dispatch) and, inside those, subfields (a focused slice like Accounts Payable). A subfield is the thing a company adds — one price, and every function under it is unlocked.
Your first subfield is included for every company. After that it's a flat monthly rate, with discounts that stack.
A connection is a link between two parties that both sides agree to — a customer and a company, a company and its supplier, or two companies. Both sides see the same link and its status, and either can end it. What each side is to the other is up to that side: a Customer Connection is someone you do work for, a Vendor Connection is a place you buy from, and a Mutual Connection is a place where it goes both ways — you can do work for each other, or one buys and does work.
Requesting, accepting and ending a connection are part of the core customer functions above — standard on every account. Connections used to be called contracts. Managing customers, pipeline and service agreements on top of them is the CRM field.
A workspace is a screen built around one job. A dispatch workspace has everything you need for dispatch in one place. Workspaces are assembled from page tiles, one per function's worth of content.
If you don't have access to a function, its tile simply isn't shown and the workspace reflows around the gap. The same workspace looks fuller or leaner depending on what you can do.
Your at-a-glance view. A dashboard is a collection of dashboard tiles, each one rolling up a few related functions into a summary — counts, totals, recent activity. Dashboards are yours or your company's, can be pinned, archived, reordered, and shared with specific people.
Every account is a profile. There are four kinds:
Personal — an individual's own identity. · Company — an organisation. · Family — a household. · Employee — the identity a person holds inside a company, separate from their personal profile.
One person can have a Personal profile and be an Employee at one or more companies at the same time — the two never mix.
A title is a company's saved definition of a role. It names one or more subfields and carries a short description. What a title grants is worked out live: it gives the workspaces and dashboard tiles for those subfields, and the description narrows which ones. Change the description and the access changes with it — nothing to keep in sync by hand.
Title: AP Clerk → subfield Accounts Payable, description "enter and match invoices" → grants just the workspaces and tiles about entering and matching invoices, not the whole subfield. A title can span more than one subfield when a role genuinely needs it.
The pieces connect in one direction:
In the Store — or someone requests them and a purchaser approves.
Subfield plus a description, one per role it wants.
They get an Employee profile at that company.
One title per person. Their workspaces, dashboard tiles and functions appear immediately — exactly what that title grants, across every subfield it names.
Anyone can ask for a new subfield or automation — whoever can purchase for the company reviews that queue. Asking for a specific function or title change goes to a different, closer reviewer: whoever's above you in your own reporting line, not whoever can purchase.
These pieces make up the Portal itself. Four more real parts of the ecosystem sit alongside it: TNC Cloud (your files, wherever you choose to keep them — in the app or right in your browser), TNC Swarm (pairing your own devices into one private, encrypted swarm — still in development), TNC Community (a place you earn standing in, separate from the platform itself — the website is up, most of its own sections are still "coming soon"), and the Hub (connecting outward to the other software your company already runs).
Walk through what the onboarding process looks like, step by step.
See the onboarding flow