Managed Fields Form
A profile form where a policy banner explains directory sync, identity fields render locked with a synced marker, and other fields stay editable.
A profile form where a policy banner explains directory sync, identity fields render locked with a synced marker, and other fields stay editable.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Managed Fields Form is a profile editor where identity fields are locked by directory sync. A policy banner explains that Acme syncs profile data from Okta, then the locked rows, Full name and Work email, each show a Synced from Okta marker with a disabled input at the synced value. The remaining fields, Job title and Time zone, stay fully editable, and the footer notes how quickly synced fields refresh before a working Save changes.
The locked rows come from a small array, each rendering a Lock marker and a disabled input, so extending the managed set is a data change rather than new markup. The editable fields are ordinary controls with helper lines, making the boundary between what the directory owns and what the person owns obvious at a glance. It is the partial lock counterpart to a fully read only form.
Reach for this block in SSO managed workspaces where some profile fields come from a directory and the rest belong to the person. Drive the disabled flag and the Synced marker from your provisioning source so the lock always matches what the directory actually controls.
A natural flow around it on an Application Pro page:
Before
After
One strong use is an Okta synced profile. Other partial lock surfaces:
Tip: driving the locked set from your provisioning source keeps the Synced marker honest as the directory changes.