Individual users, organisations and resellers

Who holds your licence, who can assign it, and what happens when a partner takes over an account that already exists somewhere else.

Two kinds of user

	An individual	An organisation user
What you hold	Your own licence, one per CAD system you bought	A seat on a licence the organisation owns
Who decides you may use it	Nobody — it is yours by definition	Your organisation administrator, who assigns and un-assigns seats
Where you sign in	/org/login, with the account you use in the CAD add-in — you land on My Licence, with Downloads next to it	The organisation portal, /org/login
Who answers your support requests	Your partner if one sold it to you, otherwise the SphereHarness team	The same, decided by who set your company up

The seat details are on Licences and pricing. This page is about the other half: whose books your account is on.

Placement: who your account belongs to

Every account is either global — held directly by the SphereHarness team — or placed with a partner (a reseller). Placement decides who bills you, who may act on your trial, and where your support requests land. It is a property of your account, not a guess made from your company, which is why an individual with no company can belong to a partner just as an organisation user can.

In a partner's Your users list, the Placement column says which of the two routes brought you there:

yours — the account is placed with the partner directly.
via company — the account is a member of a company that belongs to the partner.

The list also shows Name, Email, Companies and Active. Nothing here changes what you can do in the product: placement is a commercial fact, not a permission.

How a partner brings in a user Reseller

In the reseller portal, Users → Invite a user. Invite as offers three shapes:

Invite as	What it creates
Individual (own licence)	A person who holds their own licence and belongs to no company. Accepting creates the account, places it with you, and starts a trial subscription of its own.
Organisation admin	The administrator of a customer company. Under Company, pick one of yours or choose — new company — and give a New company name; the company is created under you first, then the invitation goes out. No personal trial — the company's subscription covers them.
Organisation member	An ordinary member of one of your customer companies.

Send invitation emails a link. Invitations you have sent and not yet had accepted are under Pending invitations, each with Revoke. An invitation cannot be accepted twice, an expired one is refused and marked as expired, and a partner cannot invite anybody into a company that is not theirs.

When the email address already has an account

This is the case that needs care, and the product picks the right behaviour for you — the person inviting cannot choose:

The address is unknown. A plain invitation. Accepting creates the account and places it with the partner.
The address belongs to a global user, or to another partner's user. A transfer request instead. Nothing moves until a website administrator approves it — an invitation must never quietly take somebody off another partner's books.
The address is already one of this partner's users. The membership is simply added. The placement is not changing, so there is nothing to approve.

Accepting an ordinary organisation invitation sets your placement only if you are currently global. If you already belong to a partner, joining another company gives you the membership and leaves your placement alone. A transfer request is the only thing that moves it.

Transfer requests

A transfer moves an account from global to a partner, from a partner back to global, or from one partner to another.

Who asks: the partner who wants the user. The form takes a Reason (for a transfer).
Who approves: a website administrator. Always — there is no path where one partner can take a user from another on their own say-so.
Who is told: the website administrators, when it is raised. The losing partner is told the moment the request is raised, not after the decision. On approval the user is told too.

In the reseller portal, Transfer requests lists both directions — “you asked for them” and “asked away from you” — so you can see a request about one of your users as soon as it exists.

A rejection changes nothing at all, and quotes the administrator's note back to the partner who asked.

Messages you may see

Your account has been moved — to you, when a transfer or a direct move completes. Nothing about your account changes: same sign-in, same history, same seats. Who bills you and who answers your support requests may change.
<Partner> has asked to take over <name> — to the partner who holds the user today.
Transfer request declined: <name> — to the partner who asked.
<name> is now one of your users / <name> has been moved away — to the gaining and the losing partner.

The administrator's side Website admin

Users in the admin portal carries a Placement column — global or the partner's name — and a Move… action. Moving takes a destination (a partner, or — back to global —) and a Reason, which is required. A website administrator's own move needs no approval, but it is still recorded with the reason, so “who moved this user, when and why” has exactly one answer. Moving a user to where they already are is refused.

Transfer requests is the queue: Pending or All (including direct moves), with User, From, To, Reason, Status (a direct move carries a direct badge) and Raised. Approve and Reject both take an optional note, and the note is what the partner reads.

Orders

A partner places licence orders for an individual or an organisation — the same order form either way, with the customer chosen from its own list. Orders go to a website administrator for approval, and the seats appear on the customer's subscription when they are approved. See Reseller Portal.

Support, and who sees what

Placement decides where your support requests land: a partner's customer is answered by that partner, everybody else by the SphereHarness team. One asymmetry is worth knowing: being placed with a partner does not let you read that partner's own requests. You see your own; the partner's staff see their customers'; website administrators see everything. See Support requests.

Common questions

I was invited by a partner but I already have an account. Do I lose anything? No. Your account is not recreated — your chat history, your knowledge base and your personal memory stay. Only who holds the account changes, and only after an administrator approves it.

Can I refuse a transfer? The decision belongs to the website administrator, so say so to them — a request with an unconvincing reason is rejected and nothing happens.

Can I belong to two partners? No. An account has one placement. It can be a member of more than one company, which is why the partner's list has both a Placement and a Companies column.

I am an individual. Can I use the portal? Yes. Sign in at /org/login with the account you use in the CAD add-in. You land on My Licence, which lists the CAD systems on your licence; Downloads and My Support Requests are in the sidebar. The company pages are not part of an individual account. See Downloads.