Create your organisation and invite your team

Your organisation is the container for everything Qorionix holds about your business: your Microsoft 365 connection, your posture findings, your alerts, your audit trail and your billing. Everyone who needs to see any of that has to be a member of it. Creating it takes about three minutes; getting the invitations right saves you a conversation later about why the office manager can see the privileged-access vault.

This article covers the signup wizard, the organisation URL, the invite flow, and the two mistakes that cause most of the support tickets we get in week one.

Before you start

Have three things to hand. None of them takes long, but stopping halfway through the wizard to go and find one is annoying.

• The name you want the organisation to carry. Use the legal or trading name your staff will recognise, not an abbreviation. It appears in the top bar, in emailed reports and in your evidence bundle.
• The email addresses of the people you want to invite. Work addresses on your own domain. You can paste them all at once.
• An authenticator app on your phone, if you intend to turn on two-factor authentication during signup — which you should. Any TOTP app works. See Set up two-factor authentication.

The signup wizard, step by step

After you create your login and click the link in the verification email, you land on a four-step wizard with a progress indicator reading 1. Profile — 2. Organization — 3. Security — 4. Done.

1. 1

   Profile

   Job title and phone number. Both are optional and there is a [Skip] button. The phone number is not used as a second factor; it is there so a colleague can reach the right person when an alert lands out of hours. Fill it in if you are the person who wants to be called.

2. 2

   Organization

   Two cards side by side: Create new organization and Join existing organization. If you are the first person from your firm to sign up, choose the first. If a colleague has already set Qorionix up and sent you a code, choose the second and paste the invite code, which has the shape XXXX-XXXX-XXXX. Choosing the wrong card here is the single most common signup error, because it produces a second, empty organisation that looks identical to the real one.

3. 3

   Security

   A checkbox offering to enrol an authenticator app after your first sign-in, above the line Qorionix requires multi-factor authentication for every tenant admin. Two things worth knowing. The checkbox is currently cosmetic — it is rendered but never submitted, so ticking it enrols nobody. And enrolment does not happen here in any case: you do it afterwards under Identity → MFA, which takes about two minutes. Do it the same day. If you defer it you will be the administrator without a second factor that your own first posture report flags as a critical finding. Set up two-factor authentication is the procedure.

4. 4

   Done

   A confirmation screen with a button through to the dashboard and quick links to invite team members, explore the SIEM module and configure alert policies. Nothing on this screen is load-bearing; you can close it and come back.

The organisation URL, and why you should look at it

When you type the organisation name, Qorionix generates a URL slug from it and shows it underneath the field as editable text. A firm called Acme Security BV gets this:

Organization name:  Acme Security BV
URL slug:           acme-security-bv

The slug appears in links your staff will bookmark and in the organisation switcher. Shorten it now if the generated version is unwieldy. Do not put a client name, a year or a project name in it.

What exists the moment you finish

Creating the organisation seeds three built-in roles automatically. You do not have to design a permission model to get started, and for a firm of your size you may never need to.

The exact permission behind each role is documented in Who can see and do what, including the things deliberately held back from member — credential retrieval, billing, detection-rule authoring and the audit log.

Inviting your team

1. 1

   Open Identity → Users and press Invite

   It is the primary button at the top right of the Users page, beside Refresh. The dialog is headed Invite user.

2. 2

   Fill in one person

   Email — the placeholder is [email protected] — plus First name and Last name. One address per invitation. There is no batch field and no comma-separated list; inviting eleven people is eleven passes through this dialog.

3. 3

   Pick their role

   A dropdown listing your organisation's roles by name. This is the only place in the console where a role is assigned, so choosing it correctly here saves an API call later — there is no screen that changes an existing person's role.

4. 4

   Press Send invite

   The dialog closes and a toast reads Invite sent. A failure reads Invite failed.

What the invited person does

1. Opens the invitation and creates a password. Minimum twelve characters, with an uppercase letter, a number and a special character; the requirements are shown as a live checklist.
2. Verifies the email address by clicking the link sent to it.
3. Runs the same four-step wizard you did, except that at step 2 the organisation is already resolved from the invitation, so there is nothing to choose.
4. Sets up two-factor authentication at step 3, or defers it and shows up on your posture report.

When an invitation does not work

Nothing arrived at all

Check the spam folder first, then check the address for a typo in the Users list — an invited account appears there with the status STAGED. There is no resend button, so a typo means suspending that row and inviting the correct address. Invitation email that never reaches your own domain is usually your mail filtering, not ours. If several people got nothing, look at status.qorionix.com (opens in a new tab) before opening a ticket.

An account with this email already exists

The verbatim string is "An account with this email already exists. Sign in or reset your password." The person already has a Qorionix login, perhaps from a trial. They should sign in with it rather than create a second account; then add them as a member from your Users page.

Account not provisioned. Contact your admin.

This appears after a single-sign-on login when the provider is configured not to create users automatically. Invite the person explicitly, or switch auto-provisioning on for that provider. It is not a password problem and resetting the password will not help.

The person ended up in their own empty organisation

They chose "Create new organization" at step 2 instead of "Join existing organization". Invite them again; they should join the real organisation with the code. Ask them not to keep both memberships — see the note below.

One organisation per person, for now

Active, suspended, deprovisioned

Your organisation is in one of three states. You will spend all of your time in the first one, but it is worth knowing what the other two mean before you ever see them.

Your organisation also carries a home region and is bound to it on the first write. A request arriving with a token from a different region is refused rather than quietly served. For EU customers that region is in the EU.

What to do next

1. Set up two-factor authentication if you skipped it at step 3. Two minutes.
2. Connect Microsoft 365 and read the report. This is the step that tells you something you did not already know about your own business.
3. Work through the first-week checklist in order. It is short and deliberately ordered by value.