Set org-level privacy defaults and lock fields

This guide shows you how to set the default visibility for each member profile field and optionally lock fields so members can’t change them.

Who can do this: Admins with the directory:configure-privacy-defaults permission.

Before you start

• New members automatically inherit the defaults you set here when they join.
• Existing members are not affected unless you use the retroactive apply option in this same form.
• Locked fields appear as read-only in members’ privacy settings with the note “Set by your admin.”

Steps

Set the default visibility for each field

1. In the admin sidebar, select Directory, then select Privacy defaults.
2. For each field in the Field visibility defaults section, choose a default:
   • Public — new members’ profiles show this field to everyone, including visitors who aren’t signed in (on public directories).
   • Members only — new members’ profiles show this field to signed-in members only.
   • Hidden — new members’ profiles don’t show this field in the directory at all.
3. To prevent members from changing a field’s visibility, check Lock this field next to that field.
4. Select Save. The defaults are saved for new members.

Apply defaults to existing members (optional)

If you want to update existing members’ privacy settings to match your new defaults:

1. Check Apply these defaults to existing members now.
2. A Reason for retroactive apply field appears. Select one of the following reasons:
   • Compliance investigation
   • Member request via support
   • Bulk default apply
   • Org policy change
   • Other
3. Select Save. A confirmation dialog appears explaining that only fields members haven’t customized will be updated. Members who have already set their own preference for a field keep their setting.
4. Select Apply to confirm, or Cancel to go back.
5. A progress indicator appears. Wait for the message “Privacy defaults applied to N members” before navigating away.

This retroactive apply only updates fields each member hasn’t already customized. If a member set their own preference for a field, that preference is preserved.

Verify

For the non-retroactive path: you’ll see “Defaults saved” when your changes are saved. New members who join after this point inherit these defaults.

For the retroactive path: you’ll see “Privacy defaults applied to N members” along with a View audit log link to confirm the batch completed.

If something goes wrong

• The Save button stays greyed out — if you’ve checked Apply these defaults to existing members now, you must also select a reason before the button becomes active.
• “Some members could not be updated — download error report” — download the report to see which members were affected. A rollback option is available for 48 hours after the batch runs.
• “Could not save — try again” — the changes didn’t save. Select Save again or refresh the page and re-enter your changes.
• “Another admin updated privacy defaults” — reload the page to see the latest settings, then re-apply your changes.

Related

• Audit member directory privacy changes
• Per-field visibility options reference
• Privacy override reason codes reference
• How directory visibility and privacy work