How to configure role-based access for different teams
Ticketclosed
Brimscombe Energy · How to configure role-based access for different teams
Nikhil asks how to configure restricted access for collections team: contracts and payments only. Bethan clarifies options; Nikhil tests role hierarchy method and reports success. Confirmed as supported pattern. Clean resolution.
What happened
What this says
As at Fri 9 Oct 2026Nikhil asks how to configure restricted access for collections team: contracts and payments only. Bethan clarifies options; Nikhil tests role hierarchy method and reports success. Confirmed as supported pattern. Clean resolution.
Nikhil is configuring least-privilege access for a new team, focusing on table-level permissions in the brain's schema. He self-diagnoses the solution using the documentation and Bethan confirms it's a supported approach.
Handling: Efficient back-and-forth; Bethan asks clarifying questions, Nikhil tests independently, reports success.
Watch: None. Good signal of customer's technical capability and confidence with the platform.
Details
Updated 9 Oct 26Trail
created · Nikhil Rao 21 May 2025 10:06We're onboarding our collections team to the brain but they need restricted access: only customer contracts and payment history, not call recordings or account metrics. I've read the role creation docs but the schema relationship isn't clear. Should I use Snowflake role hierarchy or set table-level permissions in the brain schema? I've checked our user provisioning on the Snowflake side and it's correct. Which approach is recommended? Nikhil- Public reply · Bethan Lister 21 May 2025 12:35Hi Nikhil, just so I've got this right, you want to create a custom role for collections staff limited to contracts and payments. A couple of quick questions: are you building the role in the brain's schema or in your workspace? And would you prefer role-based dashboard restrictions or table-level access? Both are supported. Can you try that and tell me which approach fits your audit needs? Thanks, Bethan
- Public reply · Nikhil Rao 22 May 2025 15:43In the brain's schema. Table-level is what we need, least-privilege from the database. I checked the permissions doc but it doesn't show nested roles (collections team under data team). Should I use Snowflake's hierarchy directly or does the brain handle that? Nikhil
- Public reply · Nikhil Rao 23 May 2025 14:23I tested the hierarchy method from the docs and it's working as expected now. Can you confirm this is a supported pattern? Nikhil
- Public reply · Bethan Lister 23 May 2025 15:26Perfect. Yes, role hierarchies are the supported pattern for structured teams like yours. You're good to roll this out. Reach out if you hit any snags. Thanks, Bethan
- Status change · 27 May 2025 23:59