Why is the email sys_glide_object not visible in the baseline instance?

[SPeshek]

I see instructions referenced in the community in numerous posts on how to modify the sys_glide_object write ACL to allow admin override, then update the email sys_glide_object record to mark it visible.  This so you can add a custom field of email type.  

My question is why is this disabled in the baseline instance?  Is there a reason ServiceNow has it set this way?

Thank you.

[kirankawle]

Security and Data Integrity: Allowing unrestricted modifications to sensitive objects like sys_glide_object could lead to unintended changes that compromise data integrity or system stability.

Standardization: By disabling certain features in the baseline, ServiceNow ensures a consistent and predictable behavior across all instances, reducing the risk of misconfigurations.

Encouraging Best Practices: ServiceNow often restricts direct modifications to encourage users to follow best practices, such as creating custom objects or fields instead of altering baseline configurations.

Minimizing Risks: Email fields, in particular, may have restrictions to prevent misuse or exposure of sensitive information, especially in environments with strict compliance requirements.

kindly refer this explaination might help your question .

Thanks