Snowflake Access Control by Jessica Megan Larson

Author:Jessica Megan Larson
Language: eng
Format: epub
ISBN: 9781484280386
Publisher: Apress

She can see all four of the roles she has access to, in addition to the default role granted to all users, PUBLIC. This is when naming conventions become very important – we should name the parent roles in such a way that it is clear to the end user which one to use since all child roles will also be available to them.

Naming Conventions

When we use role inheritance to create roles, we will necessarily create a multitude of roles, and at the same time, most users will have many roles at their disposal as well. As we covered in the previous section, end users will need to know which roles to use, and if we name our roles properly, the name alone should indicate that. The easiest option is to name our child roles that are directly granted privileges with names that indicate that they should not be used, and to name our composite or parent roles a name that corresponds with job functions or team names.

For child roles directly granted privileges, I recommend using a naming convention that indicates the types of privileges the role has. We’ve seen this throughout the book as well as in roles such as SALES_TOOL_READ. We could make this role even clearer by naming it something like DIRECT_SALES_TOOL_READ. Ideally, the corresponding role that a user should assume would have a name like SALES_ANALYST or SALES_TEAM. The words DIRECT and READ make the name of the role harder for less technical users to immediately decipher, which makes them less likely to reach for that role when roles with simpler, more relevant names are available that may match their team name or their job title.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.