Question 1

Per-tenant isolation

Accepted Answer

Every record belongs to a team, and requests are scoped to the caller's team by middleware rather than by each individual query remembering to filter. A user cannot read another tenant's entries by changing an id.

Question 2

Role-based access

Accepted Answer

Three roles (member, team admin, and platform admin) gate what each person can see and do. Prompt and policy configuration is restricted to platform administrators.

Question 3

Audit logging

Accepted Answer

Administrative actions are written to an append-only audit log with the acting user, and are reviewable by administrators.

Question 4

Microsoft and Google SSO

Accepted Answer

Your team can sign in with their existing Microsoft or Google identity, so BeeBillable does not become another password to manage. SAML for enterprise identity providers is available on request for Enterprise plans.

Question 5

Two-factor authentication

Accepted Answer

Any user can add authenticator-app (TOTP) two-factor authentication, with one-time backup codes. Team admins can require it for their whole team; adoption is visible on the Team Management page. MFA secrets are encrypted at rest.

Question 6

Password storage

Accepted Answer

Where a password is used, it is hashed with bcrypt at cost factor 12. Passwords are never stored or logged in plain text, and changing or resetting a password invalidates existing sessions. New passwords are screened against known breach corpora via the HaveIBeenPwned k-anonymity API. The password itself never leaves our server.

Question 7

Brute-force protection

Accepted Answer

Failed sign-ins are throttled per-IP and per-account with progressive lockouts, and the account owner is emailed when their login is locked. Sign-ins from a device we haven't seen before also trigger a notification email.

Question 8

Session controls

Accepted Answer

You can see every active session on your account and end any of them, or all of them at once, from Account Settings. Platform-administrator sessions expire after 24 hours, and destructive admin actions require re-entering credentials even within a valid session.

Question 9

Extension tokens

Accepted Answer

The browser helper authenticates with a token that is stored only as a SHA-256 hash on our side, expires after 90 days, and can be revoked.

Question 10

It writes only where you put the cursor

Accepted Answer

The helper reads the text your tech selects on the ticket plus the ticket number, to use as context. It writes in exactly one situation: your tech clicks into a note field and taps “Fill from BeeBillable”. It has no API access to your PSA, it cannot save a time entry, change a ticket, or take any action on its own.

Question 11

Scoped to your PSA

Accepted Answer

It only runs on ConnectWise, Autotask, HaloPSA and Syncro domains. It is not active on the rest of the web.

Question 12

Nothing is submitted silently

Accepted Answer

The rewritten note is returned to your tech to review, edit and paste. Suggested steps are proposals that a person has to confirm, the tool never asserts work on their behalf.

Question 13

What we measure about usage

Accepted Answer

We record when a technician opens the BeeBillable panel and which PSA product they opened it in, so we can tell whether the tool is actually being adopted. We do not record the page address, the ticket, or anything else on the screen.

Question 14

Who processes the text

Accepted Answer

Scoring and rewriting are performed by Anthropic's Claude models via the Anthropic API. The text of the time entry, and any ticket context your tech selects, is sent to that API to produce the score and the rewrite.

Question 15

It does not invent facts

Accepted Answer

The rewrite is written from what your tech typed and the ticket text they highlighted. It will not add a confirmation, a root cause, or a named person that is not present in the source. An honestly thin note scores low rather than being padded. The one thing it fills in is how the work was accessed (remote, onsite, phone), and only when you have set that as your team default; turn the default off and it will not assume even that.

Question 16

Keep client data out of it

Accepted Answer

Time-entry notes should not contain credentials or secrets. Teams can require that sensitive data is excluded, and administrators can see when that setting is changed.

Security and data handling