Skip to content
Join the waitlist

Help Centre

Account Security and Roles

You sign in to QueryRev with your email and a password, or with Google. QueryRev checks new passwords against known breaches, emails you when your account is used on a new device, and keeps every workspace’s data apart in the database itself. Roles decide what each member of a workspace may see and do.

By QueryRev AIPublished Updated3 min read

Key takeaways

  • A password has at least 12 characters and is refused if it has appeared in a data breach.
  • Keep me signed in lasts 30 days from your last visit, and never more than 90 days.
  • QueryRev emails you after a sign-in from a new device and after your password changes.
  • Each workspace’s data is kept apart by the database, and a test suite tries to break that on every change.

Signing in

Sign in with your email and password, or choose Continue with Google. One account reaches every workspace you belong to. If you were invited to a workspace, sign in with the address the invitation was sent to.

A new password has at least 12 characters. QueryRev refuses one that has appeared in a data breach, one that contains your name, your email or the word QueryRev, and one that is easy to guess, and it says why. Length matters most: symbols, digits and capitals are not needed.

After too many attempts in a short time, sign-in asks you to wait a minute. The message for a wrong email and for a wrong password is the same, so the form never reveals whether an address has an account.

Forgotten passwords and confirmation links

  1. Choose Forgot password? on the sign-in page and enter the address of your account.
  2. Open the link in the email. It goes only to an address that has an account; if nothing arrives, try the address you signed up with, or the one you use with Google.
  3. Choose a new password. You are signed out everywhere else, then you sign in with the new one.

Confirmation and reset links work once and expire. An expired or used link says so and offers a new one in one step.

Sessions and security emails

Keep me signed in on this device keeps a session for 30 days from its last use, renewed as you use it, up to 90 days from when you signed in. Without it, the session ends when you close the browser, and after a day at most. Sign out is in the account menu.

QueryRev emails you when your account is signed in to from a device it has not been used on before, with the device, how you signed in and the time, and when your password is changed or reset. If it was not you, the email’s button leads to resetting your password, which signs you out on every device. QueryRev never asks for your password by email.

Roles in a workspace

Each member of a workspace has one role. A Founder chooses it when inviting someone, and can change it later under Workspace, then Members.

What each role may do in a workspace.
  • Founder

    Sees
    Everything, money figures included
    May
    Approve changes, set and loosen the policy, add sites, invite members and change roles.
  • SEO Manager

    Sees
    Everything, money figures included
    May
    Approve and start changes, add sites, connect sources, tighten the policy, create reports.
  • Specialist

    Sees
    The sites assigned to them, with limited money figures
    May
    Work on decisions assigned to them and create reports for their sites; not approve.
  • Developer

    Sees
    The figures relevant to technical work
    May
    Work on the technical decisions assigned to them; not approve.
  • Viewer

    Sees
    Read only
    May
    Read decisions and reports; change nothing.

A workspace always keeps at least one Founder: the last one cannot leave or be removed until another member is made a Founder. A member who is removed loses access at once, and what they did stays in the history.

How workspaces are kept apart

Every row of a workspace’s data carries the workspace it belongs to, and the database itself only returns rows of the workspace a member is signed in to. A query cannot reach another workspace’s data even if the code that sends it has a mistake. An automated suite tries to read across workspaces on every change of the code, and the build fails if one attempt succeeds.

Google access is read-only. Only its refresh token is stored, encrypted and bound to its workspace and connection, and the web app cannot read it at all. Security has the full picture: the providers QueryRev uses, where data is stored, and how a deletion is carried out.

Cite this article

A suggested citation. Its link goes to this page, whose address does not change.

QueryRev AI. “Account Security and Roles.” QueryRev AI, 7 Nov 2026. https://queryrev.com/docs/account-security

Read next