Define who belongs in a group
Groups (Org settings → Groups) organize the internal Athean users in your workspace. (To group prospect companies and people, use Lists.)
- Rule-based membership: Group membership is evaluated over your active users based on a rule. A rule can use a user's name, email address, title, organization-maintained attributes (such as team or region, if your organization keeps them), and whether they have an active LinkedIn connection. For a fixed set of people, the rule can list their work email addresses.
- Read-only roster: You can't add or remove individual members by hand. To change membership, change the group's rule or have the user information it reads corrected (see Correct the information a group rule uses).
- No access by itself: Creating a group doesn't invite users, grant permissions, share content, or start agents. Provision users first, then attach the group to the roles, content, agents, or layouts it should receive.
Create a group
Organization administrators create and manage groups in Org settings → Groups:
- Select New group.
- Pick a starter template (Team by title, Region or segment, or LinkedIn connected) or describe your membership rule in the chat (for example, "Create a group called East SDRs for active users whose title contains SDR and whose region is East" or provide a fixed list of work email addresses). Use attributes and values your organization actually keeps.
- Review Athean's membership plan and diagram, check who is included and excluded, then approve the plan and approve the save.
- Open the saved group's Members tab to verify the matched users.
A new group is live as soon as it's saved.
Inspect group members and refresh status
In Org settings → Groups, click a group's member count, select View members, or open the group's Members tab to search and verify resolved users.
Membership updates automatically as active users start or stop matching the rule. If the latest membership update fails, the Members tab shows a warning with the last successfully resolved members, and that membership stays in use until an update succeeds. If the member list can't load, select Try again. An error doesn't mean the group has no members.
Correct the information a group rule uses
- Open a group's Specs tab to see which user information its active rule evaluates (such as title, email list, team, or region).
- If the rule uses an explicit list of email addresses, edit and activate a new rule version to add or remove emails.
- If organization-maintained information such as a user's title, team, region, or manager is wrong, email support@athean.com with the user's work email, the group name, the detail that is wrong, and its current and intended values. If another system supplies that information, include the system and who manages it. Neither Org settings nor Athean in Admin chat can edit these attributes.
- After the information is corrected, recheck Members, then the roles, shared content, and layouts that depend on the group.
Edit a group rule and activate a version
- Open the group in Org settings → Groups (or select Edit from its row menu).
- Describe the rule change in the chat, approve the updated plan, and approve saving the new version.
- Open the Versions tab. Saving an edit creates a new version without replacing the live rule.
- On the new version, select Compare to inspect the differences, then select Make active version. The Current badge marks the active version.
- Recheck Members and the access or assignments that depend on the group.
To return to an earlier rule, select Make active version on that version.
Where groups can be assigned across Athean
| Feature | How group assignment works |
|---|---|
| Permissions & roles | In Org settings → Permissions, attach a group under a role's Automatic membership so every group member inherits that role. Group-derived roles cannot be removed on a per-user basis without changing the group or role binding. |
| Sequences & Snippets | In the share dialog, give a group access under People and groups, or use Add to libraries to place the item in its members' libraries. Access and library placement are separate choices (see Marketplace and Snippets). |
| Agents | Set an agent's Runs for audience or sharing access to a group (see Agents). The agent runs for the group's members only after you select the group under Runs for. |
| Dashboards | Filter standard Dashboards by group in the People picker, or share Custom dashboards with a group. |
| Layout configuration | Assign Home layouts, Account page layouts, field sets, and default saved views to groups in Org settings → Layout configuration. When a user matches more than one assignment for the same configuration, the first matching assignment in priority order wins. |
| AI usage | In Org settings → AI usage, select Add a group rule under Monthly budgets per group to set a monthly credit limit for the group's members. The first matching group rule wins (see AI usage and credit limits). |
| Projects | In a project's Manage project access, choose People and groups and add the group so its members can open the project and its chats (see Projects). |
| API secrets | Under a secret's Who can use this secret, choose People and groups and add the group so its members can use the secret without seeing its value (see API secrets). |
Check group usage and delete a group
The Used by column in Org settings → Groups links to the roles and layout configurations that reference each group. It doesn't list every sequence, dashboard, agent, project, or API secret shared with the group. Before deleting a group:
- Remove any assignments for that group in Org settings → Layout configuration (Athean blocks deleting a group while it is still assigned to a layout configuration).
- Check any sequences, custom dashboards, agents, projects, or API secrets shared with the group, and replace the group where the team should keep access.
- Open the group's row menu, select Delete, and confirm in the Delete group dialog.
Deleting a group can't be undone. Roles stop applying through it, and sequences and agents shared with it stop reaching its members through that group. The users stay in your organization, and access granted directly or through other groups still applies.