Quarrington Care Network: documents logo

Access for additional users: intake coordinators

Email thread

Quarrington Care Network: documents logo Quarrington Care Network: documents · exec

Quarrington's Privacy and Security Officer approves thirty more users on one condition: intake coordinators see referrer-level data only. Hollie Grieve replied with the control and a test before go-live. No customer reply to that answer yet.

What was said

What this says

Current to 11 Oct 26

Quarrington's Privacy and Security Officer approves thirty more users on one condition: intake coordinators see referrer-level data only. Hollie Grieve replied with the control and a test before go-live. No customer reply to that answer yet.

Ask: Marisol Vega wants written confirmation of how intake coordinators are restricted, where it is enforced and who at BB-Demo can change it, before thirty more users are added.

Customer view: She will not accept an assurance that patient data is not stored without something she can point to. Her approval is conditional, not given outright.

Reply: Hollie Grieve confirmed a separate access group applied in Quarrington's own Snowflake account, with no patient fields in scope. She promised a test login, a control note and no enablement until Marisol has seen the results.

Next: the thread shows no response from Marisol to Hollie's answer.

AI · claude-sonnet-5-5 · 11 Oct 2026

The thread

Updated 9 Oct 26
Typeexec
Messages2
First message2026-09-08
Last message2026-09-11

Messages

  1. Marisol Vega
    Marisol Vega 8 Sep 2026 15:42
    to Hollie Grieve
    Dear Hollie, Danielle has told me that Quarrington intends to add thirty more users, including the intake coordinators, and has asked me to confirm the access side before anything is switched on. I have reviewed this against our business associate agreement and our minimum necessary standard. My position is as follows. I approve the additional users on one condition: the intake coordinators must see referrer-level data only. That means the referrer, the relationship, the owning liaison and the referral activity in aggregate. No patient fields of any kind may be visible to that group, whether in pages, chat answers, search results or dashboards. I would like three things from you in writing, so that we can document the control. First, confirmation of how that restriction is applied and where it is enforced. Second, confirmation that a coordinator cannot reach patient fields by asking the brain a question that draws on an underlying source. Third, a note of who at BB-Demo can change that configuration, so that it is recorded in our audit trail. Is any PHI in scope for this group at all? If your answer is anything other than a clear no, I need to hear it before the users are added, not after. I will not accept an assurance that we do not store that data without something I can point to. I will review your reply when it arrives. Marisol Vega Privacy and Security Officer, Quarrington Care Network
  2. Hollie Grieve
    Hollie Grieve 11 Sep 2026 17:34
    to Marisol Vega, Danielle Okonkwo
    Dear Marisol, hi Danielle, Thank you for your note of 8 Sep 2026, and for being so specific about the condition. We are happy to work to it. To answer your questions in the order you asked them: 1. The intake coordinators will sit in their own access group, limited to referrer-level views. Patient fields are excluded for that group, so they do not appear in pages, chat answers, search results or dashboards. We will apply this in your Snowflake account, where the brain runs, so the restriction sits with your own data controls. 2. Because the restriction is applied to the group rather than to individual pages, a coordinator asking a question cannot draw a patient field into an answer. Before the users go live, we will test this with a coordinator test login and send you the results. 3. Changes to that configuration will be made by me or by the BB-Demo engineer assigned to your account, and each change will be logged so you have the audit trail you asked for. On your PHI question: for the coordinator group, no patient fields are in scope. If that ever needs to change, we will come to you first and nothing will move without your written approval. I will write all of this up as a short control note for your records. Jordan will handle the order form side separately with Danielle, and we will not enable the users until you have seen the test results. Kind regards, Hollie Hollie Grieve Customer Success Manager, BB-Demo

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only