Field Visibility questions usually focus on feature differences, effect timing, and permission checks; this FAQ covers 3 common questions and practical answers.
FAQ
What is the difference between Field Visibility and member card display settings?
- Member card display settings control whether a field is shown on the directory card at all, which works as an overall display switch.
- Field Visibility controls which roles can view specific fields, so it supports more detailed access control.
- If you need both display control and viewer-based access control, you can use the two settings together.
How long does it take for a Field Visibility policy to take effect?
- After you save the policy, the setting takes effect immediately.
- Ask members to refresh the member card or reopen the client.
- When they check the related field again, the new visibility rule will apply.
Why can a whitelisted member still not view a hidden field?
- Confirm that the target member has been added to the whitelist correctly.
- Check whether the policy is enabled and whether the sensitive member scope is set correctly.
- Use Verify Permissions to check the actual effect of the current policy.
Glossary
| Term | Definition |
|---|---|
| Field Visibility | A policy capability that controls how specific fields on a member card are shown to internal members. |
| Sensitive Member Scope | The members affected by the policy, which can be all members or selected members. |
| Whitelist | The members who are allowed to view hidden fields for management or collaboration needs. |