Skip to content

Qubeq

What is in place, and what is not.

Staff records, salaries and client money live in here. This is the honest list, and it is kept up to date with the product.

The list.

In place

  • Permissions are checked on the server on every request. Hiding a button is never the control.
  • Each permission reaches their own records, their team's, their clients' or everything.
  • Payroll, roles, finance and settings ask for the password again, with two-step sign-in once it is set.
  • Nobody can give a role stronger than their own, or reset the password or two-step sign-in of someone above them.
  • A client's portal is confined to that client. Another client's record does not exist for them.
  • Every uploaded file is stored encrypted, and so are bank details and saved passwords.
  • Ten one-time backup codes for two-step sign-in, for the day the phone with the authenticator app is lost.
  • Sign-ins, role changes, password reveals, corrections and every look at a work diary are written to an audit trail. Owners and admins read it on one screen, by person, action and day, and export it.
  • Anyone on the team can sign out every other phone and browser they are signed in on. Sessions also end on a password change, an email change or leaving.
  • Eight wrong passwords lock an account for fifteen minutes.
  • Each workspace is backed up on a schedule its owner sets, daily or as often as every hour, with an optional off-site copy.
  • Uploads can be virus-scanned before they are kept.

Not in place yet

  • No SOC 2 or ISO 27001 certification.
  • No sign-in through a company directory: no SAML or SCIM.

Ask the awkward questions on the call.

We'd rather you heard the limits from us than found them in week two.