ARCHIVED: Naming standards for report security groups

• Procedure
• Standards for friendly names
• Consumer role security naming
• Cube role security naming

Procedure

Any request for a report security group name should be created using the Business Intelligence Management (BIM) tools through Manage Access. When creating a security group name, use the guidelines below to ensure adherence to best practices.

Standards for friendly names

A friendly consumer role or cube role name is an English phrase with a specific construction and length that describes the subject matter of the data contained in the cube. Each business name comprises one or more prime words, optional modifying words, and one class word. It cannot exceed 64 characters in length. Systems developers assist end users in the construction of meaningful business names.

Friendly consumer role or cube role names should meet the following guidelines:

• As meaningful as possible
• Self-documenting
• Easily distinguishable

Consumer role security naming

Below are the security group naming standards for SSAS customers in the Enterprise Business Intelligence (EBI) environment. These guidelines have been established to provide a consistent, structured naming convention.

Naming logic definition

 BL-UITS-EDSS_EBI_SYS_R_I_S_P_XXXXX

Each bolded component of the definition is explained below:

• SYS: System (for example, SSAS, SQLDB, TAB, BIC BI Center, CBI, etc.)
• R: Role; job function or title which defines an authority level
  • PUB = Developer role access
  • CON = Consumer role access
• I: Instance
  • SND
  • DEV
  • TST
  • QA
  • STG
  • PRD
• S: Subject or organization; a person, subject area, organization, or automated agent
• P: Permissions approval or access to a resource
  • Access denied = -
  • Access granted =
  • Test = T
  • Read = R
• XXXXX: Publisher defined

Example

Here is how the naming convention applies to the Enterprise CBI Tester role:

 CBI_TESTER_PRD_IU-IUSM_T_XXXXX

• SYS: CBI
• R: TESTER
• I: PRD
• S: IU-IUSM
• P: T (Test)
• XXXXX: Publisher defined

Cube role security naming

Below are the security group naming standards for SSAS cubes. These guidelines have been established to provide a consistent, structured naming convention.

Naming logic definition

 BL-UITS-EDSS_EBI_SYS_I_O_R_S_DB_P_CU

Each bolded component of the definition is explained below:

• SYS: System (for example, SSAS, SQLDB, TAB)
• I: Instance
  • SND
  • DEV
  • TST
  • QA
  • STG
  • PRD
• O: = Organizational unit
  • DEPT
  • ENT
• R: Role; job function or title which defines an authority level
  • PUB = Developer role access
  • CON = Consumer role access
• S: Subject or organization; a person, subject area, organization, or automated agent
• DB: Database
• P: Permissions approval or access to a resource
  • Access denied = -
  • Access granted =
• CU: Cube name

Example: Departmental cube

Here is how the naming convention applies to a departmental cube:

 _SSAS_PRD_DEPT_C_IU-IUSM_IU-IUSM_READ_GL

• SYS: SSAS
• I: PRD
• O: DEPT
• R: C
• S: IU-IUSM
• DB: IU-IUSM
• P: READ
• CU: GL

Example: SR subject area cube

Here is how the naming convention applies to an SR subject area cube:

 _SSAS_TST_ENT_C_STU_SA_-PII_ENRLMNT
  _SSAS_PRD_ENT_C_STU_SA_-PII_ENRLMNT

• SYS: SSAS
• I: TST and PRD
• O: ENT
• R: C (Consumer)
• S: STU (Student)
• DB: SA (Student analytics)
• P: -PII (Access denied to Personal Identifiable Information)
• CU: ENRLMNT (Enrollment management)