# Naming Standards & Validation Rules ## Role Name A Role Name uniquely identifies an application role used for access control and responsibility management. #### Validation Rules

Property	Value
Blank Allowed	No
Minimum Length	Minimum 1 alphabetic character
Maximum Length	45 characters
Allowed Characters	Alphabets (A–Z, a–z), Numbers (0–9), Underscore (_), Hyphen (-)
Disallowed Characters	Spaces and all other special characters
Validation Notes	Spaces are not allowed. Only alphanumeric characters, underscore (_), and hyphen (-) are supported.

#### Valid Examples * DataSteward * Admin\_User * Role-Manager * User123 * Governance\_Admin #### Invalid Examples * Data Steward → Contains space * Admin\@User → Contains special character * Role#1 → Contains special character * User Name → Contains space #### System Behavior * Prevents saving the Role Name if validation fails * Displays a validation error message #### Best Practices * Use meaningful and concise role names * Maintain consistent naming conventions * Use underscore (\_) or hyphen (-) instead of spaces * Avoid unnecessary abbreviations ## User Name A User Name uniquely identifies a user within the application and is used for authentication and access control. A User ID cannot be reused after creation, even if the corresponding user account is deleted. #### Validation Rules

Property	Value
Blank Allowed	No
Minimum Length	Minimum 3 characters with at least 1 alphabetic character
Maximum Length	255 characters
Allowed Characters	Alphabets (A–Z, a–z), Numbers (0–9)
Disallowed Characters	Spaces and all special characters
Validation Notes	Only alphanumeric characters are allowed. Spaces, underscores, hyphens, dots, and special characters are not supported.

#### Valid Examples * User123 * Admin01 * JohnDoe * DataUser2024 #### Invalid Examples * User Name → Contains space * User\@123 → Contains special character * John\_Doe → Contains underscore * Admin-01 → Contains hyphen #### System Behavior * Prevents saving the User Name if validation fails * Displays a validation error message * Prevents reuse of deleted User IDs #### Best Practices * Use simple and unique identifiers * Avoid spaces and special characters * Maintain consistent naming conventions * Use a combination of alphabets and numbers for uniqueness ## Team Name A Team Name identifies a group of users responsible for governance, stewardship, or operational activities within the application. #### Validation Rules

Property	Value
Blank Allowed	No
Minimum Length	2 characters
Maximum Length	50 characters
Allowed Characters	Alphabets (A–Z, a–z), Numbers (0–9), Underscore (_), Hyphen (-), Dot (.)
Disallowed Characters	Spaces and all other special characters
Validation Notes	Spaces are not allowed. Only alphanumeric characters, underscore (_), hyphen (-), and dot (.) are supported.

#### Valid Examples * DataTeam * Data\_Team * Data-Team * Data.Team * Team123 #### Invalid Examples * Data Team → Contains space * Team\@123 → Contains special character * Data#Team → Contains special character * Team Name → Contains space #### System Behavior * Prevents saving the Team Name if validation fails * Displays a validation error message #### Best Practices * Use clear and meaningful team names * Use underscore (\_), hyphen (-), or dot (.) instead of spaces * Maintain consistent naming conventions across teams * Avoid unnecessary abbreviations *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ovaledge.com/administration/users-and-roles/users-and-roles-management/naming-standards-and-validation-rules.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.