Organization Admin Guide

Running SphereHarness for your company: the org portal, the AI your people use, messaging channels, external connections and your knowledge base.

The org portal

Sign in at /org/login with your SphereHarness account. Everyone sees their downloads, support requests and feedback; organization admins also manage seats, Connections and the rest of the organisation settings. The pages for the server-hosted AI (Chat History, Knowledge, My Memory, My AI Key, Messaging Channels, RAG Provider) are not offered and show a notice if opened. If you should be an admin and don't see the admin pages, ask us to set your membership role.

Everyone who uses SphereHarness needs a seat — you included. In an organisation that pays, a member without a seat gets no access: no trial, and their own AI key does not help. They are told to ask you. Assign seats on Org portal → Licences per CAD system by ticking a member's box under a CAD system, and tick your own row if you use it too. See Licences and pricing.

The AI your people use

By default SphereHarness runs no AI on its servers and includes no AI tokens: each person chooses the AI in the desktop agent on their PC. Where it is offered, a third choice is the SphereHarness server AI, with a token allowance per person (how it works). Your own choices:

  • Their own API key — from OpenAI, Anthropic, Google, xAI, DeepSeek or any compatible provider, including one your company hosts. The key is stored encrypted on that PC. A company that wants one account can hand out keys from its own provider account.
  • A coding agent on the PC — a coding agent installed and signed in on the PC, such as Claude Code, Codex or Gemini CLI, under the person's or the company's own agreement with its vendor.

Your AI provider bills you directly, and prompts go from the PC straight to it: What goes where. Setting it up: The Desktop Agent.

Messaging channels

Teams: the SphereHarness Teams app. Your Teams admin uploads the app package once; each person switches it on in the desktop agent. Messages are relayed through SphereHarness to each person's own PC and never stored. On the org portal's Teams panel you may claim your Microsoft 365 tenant, so that only your members can use it, and switch it off for the tenant: Microsoft Teams: the SphereHarness app. WhatsApp and Telegram run on each person's PC or on your own organisation server, not in the portal: Channels & Messaging. The list below describes the former company channels, for organisations that run their own SphereHarness server.

Channels let your users message their CAD workstation from Telegram, Microsoft Teams or WhatsApp. On a server with hosted services switched on, a channel goes live the moment you save its credentials on Org portal → Messaging Channels:

  • Telegram — message @BotFather in Telegram, send /newbot, choose a name, and paste the token it gives you (123456:ABC-…).
  • Microsoft Teams — an IT admin registers an app in Microsoft Entra ID and creates an Azure Bot pointing at our server; you enter the app's client ID, tenant ID and secret. Users signed in with their work account are linked automatically.
  • WhatsApp — a Twilio account with a WhatsApp-enabled number; you enter the Account SID, the number and the auth token, and point Twilio's inbound webhook at our server.

Full walkthrough with the exact endpoints: Channels & Messaging. Users connect their own account from the CAD add-in's Settings or the tray Agent — that self-connect option is on by default and can be turned off on the same page.

Connections — let SphereHarness use your ERP, CRM or email

A connection is a named external system your users can drive from chat:

Look up item 1000 in the ERP and put its description on the drawing title block

Connections are set up and kept on your company's side, not on the SphereHarness website: in the connections store that comes with your organisation's document-index service (or on the user's own PC for a single user). A connections admin adds them in the desktop agent under Settings → Knowledge → Company connections, from templates for SQL Server, PostgreSQL, Business Central, Dataverse, Salesforce, HubSpot, Microsoft 365 mail, Google Sheets and generic REST. Each user's desktop agent connects directly from the PC; secrets are released sealed for one call and never pass through SphereHarness. The old Org portal → Connections page now only offers an export of your earlier connections (without secrets) and deletes the secrets we still hold. Full guide: Connections.

Knowledge base

Documents SphereHarness can cite in answers — design guidelines, standards, part libraries — are indexed by a service on each user’s own PC by default, so they never leave it. To share one index across the company, run the same service on your own server and set it on Org portal → Admin → Document Index: the address and whether people sign in with their Windows login, Microsoft Entra ID or a shared key. The page stores no secret, and the documents go from each PC straight to your server. Setup: Document Index: IT Setup. The portal’s Knowledge and RAG Provider pages belonged to the server-hosted AI and are not offered. See Knowledge Base.

Watching usage

Each user sees their own consumption in the chat (/usage), counted on their PC. SphereHarness does not receive it, so your AI provider's own billing is where the organisation-wide cost is.

Getting your team started

  1. Install the add-in for each CAD system (Getting Started).
  2. Decide which AI your people use: their own keys, keys from a company account, or a coding agent.
  3. If people should reach their PCs from Teams, have your Teams admin upload the SphereHarness Teams app (how).
  4. Connect your ERP/CRM/email if chat should reach them.
  5. Point everyone at Chat Basics and — before results feed real decisions — Verifying Results.