Follow-up from kickoff: access, roles and next steps
Email thread Brimscombe Energy · cs
Callie Brennan asked Brimscombe Energy for a Snowflake role, a source list and user names. Nikhil Rao replied on 23 Jan 2025 with a read-only role, but the complaints schema is held back pending the CISO's sign-off.
What was said
What this says
Current to 13 Oct 26Callie Brennan asked Brimscombe Energy for a Snowflake role, a source list and user names. Nikhil Rao replied on 23 Jan 2025 with a read-only role, but the complaints schema is held back pending the CISO's sign-off.
Ask: Callie asked Nikhil for a scoped role and warehouse, the first-wave source list, the security review needs and the first user group. She said no connector would start without written access.
Customer view: Nikhil created the role with read access on customer, site and contract data only. He held the complaints schema for Oluwaseun Bamidele and put billing last because its export is not stable.
Gap: Oluwaseun and Siân Pritchard did not reply in the thread. Nikhil also asked which BB-Demo role needs access, so he can scope it.
Next: the complaints schema and the user names remain open, and production changes avoid Fridays.
The thread
Updated 9 Oct 26Messages
Callie Brennan 21 Jan 2025 08:39Hi all, Thanks for your time at kickoff. Here is the plan as I understood it, so please correct me where I have got it wrong. What I need from your side is the following, before we switch on the refresh: - Nikhil: a dedicated role and warehouse in the Snowflake account for the brain, with the role scoped to the schemas we agree. I will not start any connector until I have access in writing. - Nikhil: the list of source systems for the first wave, in the order the key-account, collections and complaints teams care about. From the call that was the CRM, the call recorder and the helpdesk first, then billing. - Oluwaseun: confirmation of what the security review needs from us, and whether you want the access model documented before or after the first load. - Siân: the names of the people who will be in the first group of users. The licence covers 180 users, but I would rather start small and widen once the first answers look right. On our side I will send a setup note covering the field mappings once I have checked them against a sample of your data. That maps cleanly for the customer and site records from what I saw on the call, but I have not yet seen the complaints data, so I am not going to promise anything there. Daniel is copied so that he has the full picture and can pick up anything commercial or about adoption. Could you come back to me with the role details and the source list by the end of the week? Happy to jump on a short call if it is easier to talk it through. Thanks, Callie
Nikhil Rao 23 Jan 2025 14:17Callie, Role and warehouse are created in the Snowflake account. Read access only on the schemas for customer, site and contract data. Complaints schema is not included yet, that needs Oluwaseun's sign-off first. I will not send credentials by email. You will get an invite through the platform and I will confirm the role grants separately. Which role has access on your side? I need the name so I can scope it properly. Source list: CRM, call recorder, helpdesk, then billing. The billing export is a schema change on our side and is not stable yet, so leave it last. Nothing goes into production tomorrow. Friday is a no. Monday at the earliest for the first load. I checked the load history and the nightly jobs finish well before the morning, so we have room. Oluwaseun, please reply on the complaints schema and the access documentation. Nikhil