Manage an organisation in Synthreo Certified
For partner admins in Synthreo Certified: the Organisation sheet - create a customer, rename an organisation, grant or revoke admins, claim or release a domain.
About this guide
Section titled “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
Section titled “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
Section titled “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
Section titled “Create a customer”Available on your own MSP organisation.
- 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.
- 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.
- 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.
- 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
Section titled “Rename an organisation”Available on an MSP or customer organisation.
- 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.
- 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
Section titled “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
Section titled “Claim a domain”Available on an MSP organisation. A claim attaches to the MSP; customers get their domain when they are created.
- 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.
- 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.
- 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.
Troubleshooting
Section titled “Troubleshooting”- 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.
- 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.

