Available in Element Core. See our packages overview for details.
Overview
As your list of internal users grows, tailored access to Element451 becomes essential. Whether it's athletic coaches monitoring recruits, international agents tracking applicants, or faculty reviewing applications for specific programs, ensuring individuals see only the Contact Records/Profiles relevant to their roles is crucial. Visibility Groups is your tool for fine-tuning that access with ease, including controlling access to conversations associated with those Contact Records.
Accessing Visibility Groups
Navigate to Settings > Manage Users > Visibility Groups
How Visibility Groups Work
Visibility Groups allow you to manage access to contact records (including a contact's conversations) at a granular level. You can create up to two levels of subgroups to define what records are accessible to different team members.
Understanding Subgroups
Subgroups inherit the primary group's conditions and add their specific filters for even more precise control. Being a subgroup changes how users and visibility filters behave.
Filter inheritance (AND logic): A subgroup automatically includes the parent group's visibility filters, shown as read-only. Any filters you add to the subgroup apply as an AND condition on top—narrowing the record set further, never expanding it.
Example: Parent group is filtered to "Intended Campus = Element HQ." A subgroup adds "Major = Business." Result: users in the subgroup only see Business majors from Element HQ—without having to rebuild the campus filter on every subgroup.
User inheritance: Users assigned to a parent group are automatically inherited by all of its subgroups. Inherited users appear as read-only within the subgroup and must be managed from the parent. A user added to the parent is in every subgroup beneath it—you cannot assign someone to only some subgroups.
Nesting limit: You can nest up to two levels deep (parent → subgroup → sub-subgroup). Groups at the maximum depth will not have the option to create additional subgroups beneath them.
Planning Your Group Structure
Using the parent group for power users: You don't have to assign anyone to the parent group—or you can use it strategically. A common pattern is to assign directors or admins at the parent level so they automatically inherit access to all subgroups, while individual staff are assigned only to the subgroup relevant to their role.
Example: A Director of Admissions is assigned to the parent "Undergraduate" group and automatically sees all records across every program subgroup. A Business admissions counselor is assigned only to the "Business" subgroup. A Biology admissions counselor is assigned only to the "Biology" subgroup.
Subgroups vs. standalone groups: The same outcome as a subgroup structure can be achieved with independent single-level Visibility Groups—just create multiple groups each containing the same base filter.
Use subgroups when:
Multiple groups share a common base filter and you don't want to rebuild it on every group
You have power users (directors, admins) who need access across all related groups
Use standalone groups instead when users need to belong to some—but not all—related groups. Because a user added to a parent group automatically inherits access to every subgroup beneath it, there is no way to limit them to only certain subgroups.
Common Use Cases for Using Subgroups
Athletics: Parent group for the coaching staff, with individual subgroups per sport. A head athletic director at the parent level sees all recruits; individual sport coaches are assigned only to their sport's subgroup.
Admissions by program: Parent group filtered by campus or enrollment type (undergraduate/graduate), with subgroups per academic program. The director sits at the top and sees everything; program counselors are assigned only to their program's subgroup.
Territory-based recruiting: Parent group filtered by region, with subgroups per territory. Regional directors at the top; individual recruiters assigned to their territory subgroup only.
Creating + Managing Existing Visibility Groups
Creating Visibility Groups
Creating Visibility Groups
Navigate to Settings > Manage Users > Visibility Groups
Click the + New Visibility Group button
Name your visibility group by replacing 'Untitled Group' at the top of the form
Settings: Provide a brief description of your visibility group that clearly identifies its purpose
Visibility: This is where you will establish the main filters for the group. You can also opt to load an existing segment from the segment dropdown for quicker setup. As you apply filters, the number of people who match the criteria of selected filters will be displayed for your review.
Subgroups (Optional): Further narrow down access by creating up to two levels of subgroups within your primary group. Apply additional filters to each subgroup to achieve the desired level of visibility. Subgroups inherit all filters from their parent group (shown as read-only), as well as all users assigned to the parent group. Users added directly to the parent will automatically appear in any subgroups beneath it.
Add Users: Individually search and add internal users to the visibility group.
As a final step, you will need to enable the 'Restrict the people visible to this user' setting for each user you added in Step 7. To do this:
Navigate to the user's profile (Settings > Manage Users).
On the user's profile, click on the Visibility Groups tab.
Enable the 'Restrict the people visible to this user' setting by toggling it on.
The visibility group should already be selected for this user if you added them during the creation process (Step 7). You can also add additional visibility groups to the user by checking the relevant boxes.
Adding + Removing Users
Adding + Removing Users
Managing users in a Visibility Group can be done in two ways: directly from the group or via the user's profile. Your choice depends on your needs. For multiple changes in the same group, the first option is more efficient.
Option 1: Adjust user access within the Visibility Group:
Navigate to Settings > Manage Users > Visibility Groups.
Click on the Visibility Group of your choosing.
From the Users tab, add or remove users.
Option 2: Adjust user access within the user's profile:
Navigate to Settings > Manage Users.
Click on the user's name.
Click on the Visibility Groups tab at the top.
Check/uncheck the boxes of the visibility groups you wish to add/remove.
Editing a Visibility Group (Subgroups, Visibility)
Editing a Visibility Group (Subgroups, Visibility)
Navigate to Settings > Manage Users > Visibility Groups.
Click on the Visibility Group of your choosing.
Make your edits
To edit the visibility filters/segments, use the Visibility tab at the top. After making your adjustments, be sure to click the blue Apply button to save your changes.
To edit the subgroups, use the Subgroups tab at the top. You have the option to add additional subgroups, edit an existing subgroup (pencil icon), or delete a subgroup (trashcan icon).
Deleting a Visibility Group
Deleting a Visibility Group
Navigate to Settings > Manage Users > Visibility Groups.
Click the three vertical dots icon to the right of the Visibility Group you wish to delete.
Click delete. You'll be asked to confirm your action.
Note: Deleting a parent group automatically deletes all of its subgroups. If you want to preserve a subgroup, delete or reassign it before removing the parent group.
Visibility Groups & Related Entities
Visibility Groups control access to contact records by limiting which users can view specific contact profiles.
These restrictions also affect related data across the platform. See how Visibility Groups impact each feature below.
Conversations
Conversations
Users who do not have access to a contact cannot see conversations associated with that contact in the Conversations inbox.
Exception:
If a conversation is assigned to a user or their team, they will still have access to that specific conversation.
Tasks
Tasks
Users who do not have access to a contact cannot see tasks associated with that contact in the Tasks list.
Exceptions:
If a task is assigned to a user or their team, they will still have access to that task
Users subscribed to a task will also retain visibility, regardless of Visibility Group restrictions
Appointments
Appointments
Users who do not have access to a contact cannot see appointments associated with that contact in the Appointments list.
Exception:
If an appointment is assigned to a user or their team, they will still have access to that specific appointment.








