Manage an organisation in Synthreo Certified

About this guide

This guide is for partner (MSP) admins and customer admins using the new People screen in the Synthreo Certified admin console. It covers the Organisation sheet: one place to change an organisation itself, as opposed to the people in it.

The People screen is switched on per partner. If your console still shows the Organizations and Members panels, this guide does not apply yet; see Managing your team instead.

Who this is for

• Partner admins, for their own organisation and each customer under it.
• Customer admins, for their own organisation.

You see only the actions you may take. An action you may not take is not shown greyed out; it is not there.

Before you start

• Sign in at docs.synthreo.ai/certification and open the admin console.
• On the People screen, find the organisation in the tree on the left. Each organisation has an ellipsis button beside its name; that button opens the Organisation sheet. On an MSP, pressing the plus key while the node is focused opens the sheet on Create a customer.

Create a customer

Available on your own MSP organisation.

1. Open the Organisation sheet on your MSP and choose Create a customer. You see the parent shown as a label reading “Parent: your MSP”; there is no control to change it.
2. Enter the customer’s name and its email domain (for example contoso.com); people at that domain who belong to no other organisation resolve into the customer once it exists. As you type, the Review sentence updates to “Name will be created as a customer of your MSP, with sign-in for domain”, and the button reads “Create Name under your MSP”. While either field is missing, the button stays disabled and Review lists what is needed.
3. Press the Create button, by click or with Enter or Space while the button itself is focused; the Ctrl+Enter and Cmd+Enter shortcuts never commit. The sheet closes and a toast confirms “Name created under your MSP”; the new customer appears in the tree. People with an address at that domain who belong to no other organisation resolve into it once it exists.
4. If anyone is waiting to be placed and they fit in one placement, the sheet reopens as Place people into the new customer, with the destination locked. If more people are waiting than one placement can carry, the confirmation says so and you place them in batches from the Waiting group. Nobody is placed silently. If the Waiting list could not be loaded, the toast says so; open Place from the Waiting group instead.

Rename an organisation

Available on an MSP or customer organisation.

1. Choose Rename and type the new name. The Review sentence reads “Old name will be renamed New name. Nothing changes for its N people”, and the button reads “Rename Old name to New name”. While the name is unchanged or empty, the button stays disabled and Review says why.
2. Press the Rename button. The sheet closes, the tree shows the new name, and a toast offers Undo, which puts the previous name back. If someone else renamed the organisation after you opened the sheet, the rename is refused inside the sheet and you are told the current name rather than overwriting theirs.

Grant or revoke admin

Available on an MSP or customer organisation. This is the only place a partner or customer admin grant is made; the legacy Invite an admin form is not shown with the People screen. (Synthreo platform admins keep that form, because it is the only place a platform admin can be granted.)

• Every box starts unticked. Tick Revoke beside a current admin to remove their admin grant on this organisation; their placement, tier and courses are unchanged. Someone who also administers a parent organisation keeps access to this one through that grant; revoke it there to remove it.
• Your own row has no control. Another admin has to change your access.
• To grant, type an address and press Add; repeat for several people. Read the sentence before the button: a new admin receives a sign-in link. Someone with no organisation yet is placed in this one by the grant. For a partner admin, someone placed in another of your organisations moves into this one, and an address managed outside your organisations is refused; a Synthreo platform admin’s grant leaves an existing placement alone.
• If the sign-in link could not be sent, the grant still stands and the console says so; the person can sign in at the certification page.

An admin of an organisation can place, move, set tier, assign courses and remove its people, and sees nothing outside it.

Claim a domain

Available on an MSP organisation. A claim attaches to the MSP; customers get their domain when they are created.

1. Choose Domains. Type the domain and an address at that domain that will receive the verification link. The Review sentence reads “Your MSP will claim domain, pending until the link sent to address is opened”. If the address is not at the domain, Review says so and the button stays disabled: the proof must arrive at the claimed domain.
2. Press the button. The sheet closes and a toast confirms the claim; reopening Domains shows it with a pending badge. It grants nothing until the link is opened, and a pending claim never matches anyone.
3. A pending claim can be removed here by ticking Remove beside it; the sentence then reads “domain is released”. A verified claim shows a verified badge and no Remove; removing the organisation it backs is the way to release it.

Allocate seats

Available on a customer, for any admin of it or of its MSP, and on an MSP for Synthreo only. Seats bound how many people an organisation may hold. Every member of an MSP or customer organisation holds a seat, because membership itself confers the licensed tier. An organisation with no allocation has no bound, which is how every organisation starts.

1. Choose Allocate seats. The sheet shows the ceiling, how many seats are in use and how many are free, then a number to change. The count in use is the number of people in the organisation right now, invited people included; it is never a stored figure that can drift.
2. Raising the number, or setting one for the first time: the Review sentence reads “organisation will have N licensed seats (was M)”. Press the button. The sheet closes and a toast confirms it, with Undo, which puts the previous number back.
3. Lowering the number below the number of people: the sheet lists everyone holding a seat, people invited but not yet signed in included, and asks you to choose exactly as many as no longer fit. If the organisation changed while the sheet was open, it asks you to choose again on the current list. Nobody is removed silently. The button reads “Remove N, then allocate M seats”. Those people leave the organisation first, as one batch you can undo from the People screen; they keep their account and wait to be placed. The allocation follows. If the allocation is then refused, the removals are undone before the sheet reports why.
4. A partner admin allocates a customer’s seats from the MSP’s own pool when Synthreo has set one: the customers’ allocations together cannot exceed it, and the sheet says how many are left when they would. Only Synthreo changes an MSP’s own ceiling. When Synthreo sets one, every customer under the MSP that had no ceiling is given one equal to the people it holds that day, and a customer created under the MSP afterwards starts with a ceiling equal to the people its domain already resolves, usually none, and is refused if the pool cannot hold them; so the pool always adds up.

Once an organisation is bounded, Move, Place, Invite and Set tier show its seat meter and refuse to bring in more people than there are free seats. When no seat is free, Licensed is disabled with the reason before you can pick it. Admin grants respect the bound too. Two admins committing into the same organisation at once cannot overshoot: every commit counts the organisation’s members again under a lock after writing, and the one that would exceed the ceiling is refused with the same sentence the preview shows. Undo is held to the same bound.

Retire an organisation

Available on a customer, for any admin of it or of its MSP, and on an MSP for Synthreo only. Retiring takes an organisation out of the tree without deleting its people, its history or its domain: they are set aside, and Synthreo can bring it back. One thing is not kept: an MSP’s domain claims still awaiting verification are cancelled, and the sheet says so before you confirm.

1. Choose Retire. The sheet says what happens: the organisation leaves the tree and stops signing anyone in, because its email domain is set aside. If it still has customers, the sheet says so and the button stays disabled: retire or move them first.
2. If people are in it, they go to Waiting first, as one batch you can undo. They keep their accounts and can be placed elsewhere from the Waiting group. To merge them into another organisation instead, move them there from the People screen first, then retire the empty organisation.
3. Tick the confirmation and press the button. The sheet closes and a toast confirms it, with Undo: the organisation comes back first, then its people.

Once retired, the organisation is not offered anywhere: not in the tree, not as a destination, not to sign-in, and its licence, if it held one, is set aside with its domain. Its seat allocation, if any, no longer counts against its MSP’s pool, so bringing it back must fit the pool again. If more people would return than its ceiling holds, because people signed in at its domain while it was retired, the ceiling is raised to hold them and the toast says so.

Move a customer under another MSP

Synthreo only. Moving a customer between partners changes who can see its people and their progress, so a partner admin cannot do it.

1. Choose Move under another MSP. Pick the MSP, or Synthreo directly to make it a direct customer.
2. Read the sentence: the customer moves with its people, admins and courses; the new MSP’s admins gain access to it and the current MSP’s lose it. Placement history recorded before the move stays with the previous MSP’s ledger; only what happens afterwards is recorded under the new one. A verified claim on the customer’s domain moves to the new MSP’s custody (to the customer itself when it becomes a direct customer), so the former partner no longer sees it. If the new MSP has a seat pool, the customer must fit in it: at its own ceiling, or at the people it holds when it has none, in which case it is given that ceiling on arrival. If it does not fit, the move is refused with the numbers.
3. Press the button. A toast confirms it, with Undo, which moves the customer back unless somebody moved it again since. If the move gave the customer a ceiling on arrival, Undo takes that ceiling away again, unless the original parent now has a seat pool (every customer in a pool keeps a ceiling) or somebody changed the ceiling meanwhile; then it is kept and the toast says so.

Troubleshooting

• Retire says this grant is your only route to the organisation. You administer it directly and nothing above it, so after retiring it you could not bring it back. Ask your MSP admin or Synthreo to retire it; they can undo it.
• The ellipsis button is not there. The node is not an organisation you may change (for example a personal account), or you are not an admin of it.
• Create is missing on your MSP. Your account does not administer an MSP tenant; ask Synthreo.
• Allocate seats says the seats were changed by someone else. Another admin set the number after you opened the sheet. Open the organisation again; the sheet reads the current figures afresh.
• Allocate seats refuses to remove a customer’s ceiling. The customer sits under an MSP with a seat pool, and the pool only adds up while every customer keeps a ceiling. Lower it instead.
• Move, Place, Invite or Set tier says the organisation has no free seat. Its allocation is full. Allocate more seats, or take people out of the batch. Membership of an MSP or customer organisation is what confers the licence, so there is no “unlicensed” way in.
• Retire is disabled and the sheet names customers. The organisation is an MSP with live customers under it. Retire or move each customer first.
• Retire says the organisation still has people. Somebody was placed in it after the sheet opened. Open it again; the sheet moves everyone it finds to Waiting before retiring.
• Retire says you are a member of the organisation. Your admin grant is on this organisation alone, and moving its people out would take your access with it. Move yourself out first, or ask your MSP admin or Synthreo to retire it.
• Undo after a retire says the domain now belongs to another organisation. A new organisation claimed that domain in the meantime, so the retired one cannot take it back. Ask Synthreo.
• The sheet says the change did not commit. The message is the server’s own reason; fix the draft and press the button again. When several steps were requested and one fails, the sheet names what already happened and keeps only the remaining steps in the draft.