What you’ll learn

Explain the configuration and custom fields control purpose behind custom fields security

Configure custom field definitions, validation parameters, and module rollouts

Handle configuration settings overrides, options cleanups, and security controls

Provide audit-ready change logs and configuration histories

Lesson 1 of 3 Reading 12 min

Set field permissions

Custom Fields Security focuses on custom fields security settings, user access roles, encrypting sensitive fields, and auditing edit actions. In AWRA, custom fields and configuration parameters allow tenants to adapt database tables to unique business operations without breaking data structure.

The primary objective is database stability and change control. Configuration admins should test definitions and validation rules before wide deployment.

In practice, a security admin restricts a custom field to the finance role, enables data locks, and audits edit logs.

Security configuration path

Classify

Check if custom field contains sensitive business details.

Configure

Set user role visibility permissions.

Restrict

Lock values against unauthorized runtime updates.

Audit

Log all edits to definitions and value fields.

Configuration model

Custom field definitions modify active database schemas.
Input validation rules protect data value format and type.
Settings overrides require security controls and approvals.
Always verify template layouts before run-time value imports.

Lesson 2 of 3 Workshop 14 min

Encrypt sensitive columns

The operating routine is to configure field access permissions, audit sensitive visibility flags, monitor edit logs, and check overrides. That sequence prevents data formatting errors and keeps parameters aligned with policies.

Before publishing configuration updates, check security profiles, access groups settings, user logs, override reasons, and security logs. These safety gates protect data values, user inputs, and reporting stability.

An administrator can verify active parameters, clear settings caches, or run cleanups directly from the builder.

Field security guide

Signal	Check	Action
Private client note	Contains sensitive data	Restrict field visibility to account manager
Unauthorized field edit	Check user role rules	Block update and alert system admin
Audit check scheduled	Review settings configurations	Verify access rules match guidelines
Security key rotation	Check encryption settings	Rotate keys and verify data integrity

Admin decisions

Restrict layout changes to certified system administrators.
Lock global defaults using security approval overrides.
Resolve values validation errors during template imports.
Ensure data cleanups occur on a regular cadence.

Lesson 3 of 3 Practice 14 min

Audit configuration edits

Configuration updates and field overrides should leave proof. Useful evidence includes security settings profiles, access registries, configuration audit logs, and security alarms, which is required for audit logs reviews and system restores.

Management should review configuration drift: stale custom fields, broken dropdown options, or unapproved overrides point to settings reviews needs.

In practice, closure means sensitive columns are restricted, editing rules match guidelines, and config edits are logged.

Fields security checklist

Security rules are active

Sensitive fields are locked

Audit logs are generated

Overrides require approvals

Log files are secured

Oversight validation

Confirm that change logs record configuration updates.
Verify that database constraint tests are successful.
Validate that custom options match active guidelines.
Ensure configuration rollbacks are tested and ready.

| AWRA OpsHub

Custom Fields Security

What you’ll learn

Course content

Set field permissions

Encrypt sensitive columns

Audit configuration edits

Finished the material?

More in this path

Workflow Builder Basics

Approval Workflows

Security & Data Protection

Need a quick answer while you read?

AwraIQ