Naming conventions for users

It’s important you follow our naming conventions for users. This lets us understand what account/subscription the group members need access to. It also tells us what level of permissions and roles they have.

You must follow our naming conventions, even if you have your own organisational one you usually use.

AWS naming conventions

Naming conventions for AWS must have, in this order:

1. Platform name (AWS)
2. Environment type (live or dev)
3. Cloud Platform Service (CPS)
4. Your organisation’s name
5. Your workload name
6. Your environment name
7. The role or permission set

Example:

AWSLive_CPS_organisation_workload_environment_role/permission

AWSLive_CPS_SP_ScotPayments_AppDev_Admin

Naming conventions for Azure

Naming conventions for Azure must have, in this order:

1. Platform name (Azure)
2. Environment type (Live or Dev)
3. Cloud Platform Service (CPS)
4. Your organisation’s name
5. Your workload name
6. Your environment name
7. The role or permission set

Example:

AzureLive_CPS_organisation_workload_environment_role/permission

AzureLive_CPS_TS_PAG_DEV_CorpOwners

Azure OKTA admin groups

For Azure OKTA admin groups, we use:

1. Platform name (Azure)
2. Cloud Platform Service
3. Your workload name
4. Okta Group Admin

Example:

Azure_CPS_<CustomerOrg>_<Workload>_OktaGroupAdmin