Skip to main content

Why is REQQA invite-only?

REQQA does not have an open sign-up button. You cannot create an account, land on a pricing page, and start using the product on your own. Access is granted deliberately — either by requesting access and being approved, or by being invited by someone already inside an organisation. This page explains why, and how a prospective user actually gets in.

The short answer​

REQQA is a multi-tenant application: every requirement, story, mission, glossary term, and analysis result is scoped to an organisation, and an organisation is the unit of access (and, in time, of billing). A user who exists but belongs to no organisation can see nothing and do nothing — so uncontrolled self-registration would only ever produce orphaned accounts and a confusing first experience.

We are also onboarding clients one at a time during the trial period. Keeping the front door controlled lets us provision each new organisation by hand, get the configuration right, and talk to the people behind each request — rather than leaving strangers to set themselves up with no context.

note

"Invite-only" does not mean "invisible". The front door is discoverable — there is a public Request Access form. What's removed is self-service registration: you can ask to be let in, but you cannot let yourself in.

The three ways in​

There is exactly one path that creates login credentials (registration), and it is reached only after access has been granted. In practice, a new user arrives by one of three routes.

1. Request access (cold prospect)​

If you've heard about REQQA and want to try it, you fill in the public Request Access form at /requestAccess. It asks for four things — your name, your email, your organisation, and a short reason (your use case). No account is created at this point; submitting the form simply records your request and notifies the REQQA team so they can review it.

After you submit, you land on a confirmation page that acknowledges the request without echoing your details back. Behind the scenes your request is stored with the status new, ready for an administrator to triage.

2. Approval (what happens to your request)​

A REQQA administrator reviews each request and applies one of four outcomes: approved, declined, or spam (a request starts as new). When a request is approved, REQQA does several things automatically:

  • creates a brand-new organisation for you, named after the organisation you entered;
  • gives that organisation a first application, pre-filled with a starter mission;
  • creates an invitation tied to your email address and sends you an invite email.

That invitation is your way in. You become the sole member — the de facto owner — of your own new organisation. (If you want to join an existing organisation instead, you don't request access — a colleague already inside invites you; see route 3.)

tip

Approval is also where billing will eventually attach. Today "approve" is purely a status change that provisions an organisation and sends an invite; in future it becomes the point where a subscription or trial is started. Nothing about the request you submit needs to change for that — it's a single seam, deliberately kept clean.

3. Team invitation (joining an existing organisation)​

If your colleagues already use REQQA, the simplest route is for one of them to invite you directly into their organisation. You receive an invite email, follow the link, and accept it. If you don't yet have REQQA credentials, accepting the invite is where you create them — the Sign Up step is reached through the invitation, not from the login page.

This is the normal way teams grow once they're established, and it's covered in detail in How to invite your team.

Why not just open registration?​

A few reasons, all pointing the same way:

  • Data is org-scoped. Without an organisation, a logged-in user has no requirements, no application, nowhere to be. Open registration produces accounts with nothing attached to them — a poor first experience and a tenant-isolation hazard.
  • Onboarding is still manual. During the trial we provision each organisation by hand via the access-request flow, so we can configure it correctly and stay in contact with each new client.
  • Billing is deferred but designed for. There is no payment engine yet. Rather than bolt one on hastily, the approval step is kept as the single place where billing will later drop in. Controlled access keeps that future change small and additive.
caution

Because access is curated, an account on its own grants nothing — membership of an organisation is what confers access. If you've created credentials (for example by following an invite) but still can't see your work, you may be signed in to an account that isn't yet attached to the right organisation. Ask whoever invited you to confirm the invitation was for the correct email address.

How sign-in works once you're in​

Once you have access, REQQA supports signing in with email and password and, where an organisation has it configured, single sign-on via an external identity provider. The invite-only stance applies regardless of how you sign in: an external identity is only honoured if it matches an email that has been invited, so there is no back door around the front gate. For more on data handling once you're inside, see Your data and privacy.