The reseller portal

For partners who sell SphereHarness to their own customers: see your companies, raise licence orders, add users, answer your customers’ support requests and send them notifications.

Who this is for and how to get in

Reseller admin Sign in at /reseller/login. A reseller account exists either because the platform operator created it, or because your company applied on the website and signed the reseller agreement — signing is what creates the company and your administrator account. From then on every page in this portal is filtered to your customers only. You cannot see other partners' companies, and you have no access to the website admin portal.

The sidebar: My Tenants, Requests, Users, Team (reseller admins only), Support and Notifications.

My Tenants

Every customer company you own, with its plan, subscription status and seat count.

Reseller dashboard listing customer companies with plan, status, seats and the licence mode toggle
Reseller portal → My Tenants. Two summary cards, then one row per customer.
  • The two cards at the top count your companies and add up their seats. A company with an unlimited seat pool shows an infinity symbol in its row.
  • A company with no subscription yet shows dashes — raise a licence order for it on Requests.

Licence mode: Full or Basic

The last column carries the one setting you can change yourself, and it takes effect immediately for that customer's next chat turn:

  • Full — the plan's normal entitlements: the complete CAD tool surface, connections to external systems and messaging channels.
  • Basic (support) — a support-only licence. The assistant's tools are cut back to the support surface, connections and messaging channels are switched off, and chat answers using the standard information text you set on the Support page. This is the mode to sell to customers who bought your product, not CAD automation.

Make Basic and Make Full flip between the two. Making a company Full again restores the default entitlements for its plan — it does not restore a hand-tuned set of flags, so tell the platform operator if a customer had a custom arrangement.

Changing licence mode is not a licence order and needs nobody's approval. Seat counts and new companies do — those go through Requests.

Requests

Two request forms and their history. Everything you submit here is reviewed by a platform admin; approving is what actually applies the change.

Reseller Requests page with the licence order form, the add-user form and the two status tables
Reseller portal → Requests. Submitted items appear below with a New / Approved / Rejected badge.

Licence order

Your reseller agreement names the CAD systems you sell — the ones you listed when you applied, and the page says which. You can order and assign licences for those CAD systems only; any other one is refused with its name. To add a CAD system, ask the SphereHarness team to change your agreement.

  • Pick a Kind: Add CAD seats, Remove CAD seats or New company, and the CAD system (only your agreement's are listed).
  • For a new company, type the company name; for a seat change, pick an existing company from your list. Submitting without either is refused.
  • Enter the number of seats to add or remove and press Submit.
  • The order appears in the table below as New. When a platform admin approves it, the seats are added to or removed from that CAD system's licence and the badge turns green; a rejection turns it red. The company's administrator then assigns the seats to people. Seats that are assigned cannot be removed until they are released.

Add user to a tenant

  • Pick the company, enter the user's email address and choose a role — Member or Org Admin.
  • Press Request. On approval the person is given a membership of that company with the role you asked for.
  • The address must belong to a registered SphereHarness account. Ask the customer to sign up first; a request for an unknown address cannot be approved.

Make at least one person in each new company an Org Admin. That is what unlocks their own Messaging Channels, Connections and RAG Provider pages, so they can configure their company without going through you.

You order for an individual as well as for a company. A customer who works alone holds licences of their own and belongs to no company; the order is the same form, aimed at the person instead of the organisation. Which of the two a customer is, and what changes for them, is on Individual users, organisations and resellers.

Team Reseller admin

Open /reseller/team (sidebar Team, also the Employees card on My Tenants). A reseller admin invites their own staff by e-mail as Employee (sees your customers and requests) or Admin (also manages the team). An address without an account gets one, placed with you, with the CAD software you tick and a set-password e-mail; an address that already has an account is simply added. Remove takes staff off the team. Employees see the list only. Customers and their companies are not invited here but on Users.

Users

Invite a user brings somebody onto your books. Invite as decides the shape:

  • Individual (own licence) — a person with their own licence and no company. Accepting creates the account, places it with you and starts a trial of its own.
  • Organisation admin — under Company, pick one of yours or choose — new company — and give a New company name; the company is created under you first.
  • Organisation member — an ordinary member of one of your companies.

Send invitation emails the link. Your users lists who you hold, with Name, Email, Placement (yours when the account is placed with you directly, via company when it comes through one of your companies), Companies, CAD software and Active. For a person with a licence of their own, CAD software has one box per CAD system: tick to give it, un-tick to take it back (it takes effect within four minutes). A CAD system outside your agreement is shown but disabled, marked not in your reseller agreement. A member of one of your companies gets CAD seats from the company's administrator, so the cell only shows what they hold. Pending invitations holds the ones not yet accepted, each with Revoke.

If the address you invite already has an account, the product raises a transfer request instead of an invitation and asks for a Reason (for a transfer). Nothing moves until a website administrator approves it, and the partner who holds the user today is told the moment you raise it. Transfer requests shows both directions — you asked for them and asked away from you. Inviting somebody who is already one of your users simply adds the membership, because their placement is not changing. Full detail: Individual users, organisations and resellers.

Support — your customers' requests

Every request raised by a user of one of your companies lands here: from their desktop agent, or from My Support Requests in their own portal. You answer on the same thread they see.

The three levels of visibility

  • A user sees their own requests, and nothing else.
  • You see the requests raised by your customers and by your own staff. A request from somebody placed with you but belonging to no company reaches you too — the routing follows the account, not only the company.
  • The SphereHarness team sees everything.

Handing a request to the global pool changes who answers, not who may read it: it stays visible to you with every reply on the thread. One asymmetry is deliberate — a user placed with you cannot read your company's own requests, only their own. See Support requests.

The queue

Three buttons at the top filter the list, each with a count:

  • My queue - requests from your companies, yours to answer.
  • Handed to global - the ones you passed to the SphereHarness team (see below). They stay in your list so you can follow what was said.
  • All - both.

Each row carries the number, the company, the requester, the subject, the status (New, Updated, Answered, Closed), which queue it is in, the last activity, and a New column counting messages you have not read. A request the customer has added to comes back as Updated, which is your cue that something moved.

The thread

Open shows the whole conversation, oldest first, with every file either side attached. Send reply adds your message, and you can attach files to a reply the same way the customer can. Replying sets the request to Answered and notifies the customer, whose bell in the desktop agent picks it up within a minute.

Attachment limits are the customer's too: 25 MB per file, 100 MB per request across the whole thread.

Close request finishes it. The customer can close their own as well. Close window just puts the thread away and changes nothing.

Assign to the global pool

When a request is not yours to answer - a product defect, something you need a second opinion on - Assign to global pool hands it to the SphereHarness team. Two things stay true after you do it:

  • You keep seeing it. The request stays in your list, flagged as global, with every reply on the thread. You do not lose sight of your own customer's problem.
  • The customer does not have to do anything. They are on the same thread and keep the same request number.

Forward to your own helpdesk

If you run your own helpdesk mailbox, have the traffic sent there automatically. Under Forward to your own helpdesk set:

  • Helpdesk email - the address to send to.
  • Email when a request is created.
  • Email on every new message.

Then Save forwarding. The subject carries the request number, so your helpdesk threads them together, and the body carries the message text and links to the attachments. Turn both switches off, or leave the address blank, and support stays in the portal only.

Forwarding is a copy, not a handover. The request still lives here and is still answered here - replying to the forwarded email does not reach the customer.

Your external support system

Separately from the queue above, this is where you configure what a basic-licence customer's own assistant tells them, and whether their requests are also created in a helpdesk product you already run.

Reseller Support page with the provider selector, credentials and standard information text
Reseller portal → Support. Pick a provider, store the credential once, and set the text customers are told.

Provider

  • Portal only — requests live in this portal and nothing leaves the platform. A good starting point, and the default.
  • Zendesk — enter your Zendesk subdomain, the email address of the agent who owns the API token, and the API token. Tickets are created with your customer as the requester.
  • HubSpot — enter the base URL (the default is fine for most accounts) and a private-app token.
  • My own support system (API) — every active reseller can connect a system of its own through a small API you implement. See Support connector API.

The push happens only for a customer whose plan includes basic support, and it is a second copy: the request is still answered here. The credential is encrypted at rest and used only on the server; the box reads (stored - blank keeps it) once one is saved, which is how you change the standard text without re-pasting the token. Your customers never see and never need this credential.

Standard information

A block of fixed text shown to basic-licence customers. Their assistant is allowed to repeat this and little else, so put the things you are happy to say to everyone in it: support hours, the email address or phone number to use, escalation rules, links to your own documentation. Keep it current — it is the entire self-service answer for those customers.

What the external provider did with a request

Open a request and the reference your provider returned is shown beside its number. If an opened request shows no reference, the external call did not complete - check the credential and the subdomain. Nothing is lost when that happens: the request is recorded here either way, and you answer it here either way.

Notifications

Send a short message to a company or to one person. It appears on the bell in their desktop agent, raises a tray balloon, and stays in their list until they read it. Use it for the things nobody opens a support request about: planned maintenance, a version you want them on, a change to your support hours.

  • Send to: A whole company or One user, then pick which.
  • Type a Title and the Message. Link (optional) is a page the notification opens when it is clicked, for example /org/support.
  • Send notification. It reaches people who are signed in within a minute, and everyone else the next time they sign in.
You can only notify your own companies and their users. A target outside your customer list is refused. Platform-wide announcements are the SphereHarness team's to send.

Common mistakes

  • Waiting for a seat change that was never approved. Orders sit as New until a platform admin acts. Check the badge before telling the customer.
  • Requesting a user who has not signed up. The add-user request needs an existing account.
  • Leaving a support customer on Full. A basic-licence customer on Full mode gets the whole CAD tool surface. Flip the toggle on My Tenants.
  • Empty standard information. With nothing in that box, a basic-licence customer's assistant has nothing useful to tell them.
  • Treating a forwarded email as the thread. Forwarding is a copy. Replying to it reaches your own mailbox, not the customer; answer on the request.
  • Assigning to the global pool and then going quiet. The request stays in your list on purpose. The customer is still yours.

See also