Groups

Groups contain the people who use Athean in your organization. Lists organize the accounts and contacts you work with. Use a group for your SDR team, regional managers, or another set of teammates.

A group defines membership. A role defines the actions those members can take. Creating a group does not invite users or grant permissions by itself. Provision users first, then attach the group to the roles, content, or configuration it should receive.

Membership follows a rule over your active users. Rules can use names, email addresses, titles, organization-maintained user attributes, and whether someone has an active LinkedIn connection. For a fixed set of people, give the rule their work email addresses. For a changing team, use the attributes that define it.

The member roster is read-only: change the rule or the underlying user information to change membership. Follow Maintain the information behind membership when a teammate changes teams or their details are wrong.

Organization administrators manage groups in Org settings → Groups.

1. Select New group.
2. Describe the group's name and exactly who should belong. Start with Team by title, Region or segment, or LinkedIn connected, or write your own request.
3. Specify the existing user attributes and values the rule should use. For example: “Create East SDRs for active users whose title contains SDR and whose region is East.” Confirm that your organization actually uses those values.
4. Review the assistant's membership plan and diagram. Check the inclusions and exclusions, then approve the plan and the save when ready.
5. Ask the assistant to test the rule and show who matches. Check the saved group's Members tab before using it for access or automation.

A newly created group becomes active when its creation is saved. Give it a name your team will recognize in sharing menus, role settings, and reporting filters.

In the Groups table, select the member count or View members. You can also open a group and select Members. Review the names and work email addresses, or use Search members... to find a person.

Membership updates automatically as active users start or stop matching the rule. Changes may take time to appear across the workspace; recheck the roster after updating a rule or user attributes.

If the latest membership update fails, Athean may show the last successfully resolved membership with a warning. That membership can remain in use until a successful update. Use Try again when offered; an error or unavailable roster does not establish that the group has no members.

If membership still looks wrong, check the rule and the information it uses. Contact support if the group cannot refresh.

1. Open the group's Specs to identify the information and values its active rule uses. For example, East SDRs might depend on a job title and a region value.
2. If the group uses a fixed set of work email addresses, edit and activate its rule to change that set.
3. For a correction to organization-maintained information such as job title, team, region, or manager, chat with us. Include the teammate's work email, group name, the detail that is wrong, and its current and intended values. If another system supplies it, include that system and the person who manages it. We will work directly with your team to confirm where the information is maintained and help correct it.
4. After the information is updated, recheck Members, then the roles, shared content, and layouts that depend on the group. If membership still shows a refresh warning or the previous people, resolve that before relying on the new assignments.

Changing a person's individual role assignment does not correct their group membership. Keep the membership rule and the information it reads aligned with the team you intend.

1. Open a group from Groups, or choose Edit from its row menu.
2. Describe the change in the conversation. Review and approve the revised plan, then approve saving it.
3. Open Versions. An edit saves a new version; it does not immediately replace the active rule.
4. Use Compare to review the change, then select Make active version on the version you want to use. The Current badge identifies the active version.
5. Recheck Members and the access or assignments that depend on the group.

Specs describes the active rule. You can return to an earlier saved rule by making that version active again.

For example, use East SDRs wherever that team needs the same access, content, or working setup. Configure each use explicitly:

• Permissions: open Org settings → Permissions and select the group under a role's Automatic membership. Members then receive that role's permissions.
• Sequences and libraries: share a sequence with People and groups to give the team access. Use Add to libraries for library placement. Access, library placement, and a Marketplace listing are separate choices.
• Agents: follow Set up an agent for a team to select the group under Runs for, save its participation, and check the schedule. Creating the group alone does not start an agent; sharing access is a separate choice.
• Dashboards: use groups in People filters to review the team's work. Share a custom dashboard through People and groups when the team should be able to open it.
• Workspace layouts: assign the group in Layout configuration to apply the Home layout, Account page layout, or field set available for that configuration. When someone matches multiple assignments for the same configuration, the first matching assignment in priority order wins.

As someone joins or leaves East SDRs, these group-based uses follow the updated membership. Their direct permissions and membership in other groups still matter.

Follow Layout configuration to build layouts, assign them by group, review the people affected, and understand how managed tabs work alongside personal tabs.

Group-derived roles have no per-user exceptions. Removing a person's direct role assignment does not remove the same role inherited through a group. To exclude someone from that inherited role, change the group's rule or remove the group from the role's Automatic membership.

A membership change can affect permissions, shared content, agent audiences, reporting, and layouts together. Check those uses before activating a broad rule change.

The Groups table's Used by column links to role bindings and layout configuration assignments. Also review any sequences, dashboards, or agents that use the group; Used by is not a complete inventory of every sharing destination.

To remove a group, open its row menu, choose Delete, and review the Delete group confirmation. A group used in Layout configuration cannot be deleted until you remove its assignments there.

Deleting a group cannot be undone. Roles stop applying through it, and sequences and agents shared to it stop reaching its members through that group. Replace the relevant bindings or audiences first if the team should retain them. The users themselves remain in your organization, and access granted directly or through other groups may still apply.