Groups

Groups let federal enterprise administrators view disaggregated analytics and create targeted policies such as model availability and ACU limits to selected members of a team. Groups are team-scoped: they do not create a separate team or change a member’s access to the rest of the team. Groups are available in the self-hosted, multi-tenant federal deployment. A site administrator can access them. Otherwise, your role needs Teams Update plus either Teams Read-Only or Analytics Read so the portal can display the team roster. Teams Update alone may not be enough, and your role must also be allowed to open Settings. Groups can also be managed programmatically with the Group Management API or the Python SDK.

---

​

Open group management

In the federal portal, go to Settings → Groups. The Groups tab is available to roles that meet the access requirements above in multi-tenant deployments. The groups table includes: Select a group row to open its details. The details view shows the group name, member count, configured ACU limit, model availability, and users.

​

Create a group

Select Create group to open the wizard. The wizard guides you through these steps:

1. Name the group — Enter a name such as Engineering.
2. Select models — Under Devin Models, choose which models members can use.
3. Set ACU limit — Set a per-member limit for each billing cycle, or leave it empty for no group limit. This step appears only for ACU-billed teams.
4. Add users — Optionally add team members now. You can add or remove members later.

An empty model selection means no opinion about a member’s model access. It does not override another group’s restriction. A group model policy applies only when at least one of the user’s groups specifies a model selection for a surface. Otherwise, the user receives the models available to the team. For the full model behavior, see Model Provisioning. For ACU-billed teams, group caps can only be configured after the team has an ACU billing configuration. The portal rejects negative or non-finite values and shows Enter a nonnegative ACU limit for an invalid entry. If a follow-up step fails after the group itself is created, the portal can show Group created with warnings. The group remains available, but one or more requested model, ACU, or membership changes might not have been applied. Select Go to group to review and complete the changes.

​

Set the default group for new users

In Settings → Groups, use Default group for new users to choose the group new users are added to when their account is created, such as on first login. Select None to stop adding new users to a group. Existing users and memberships are not changed. For ACU-billed teams, the default group’s ACU limit is the limit new users start with. See ACU Limits.

​

Name and edit a group

Group names are trimmed before they are saved. A name is required, and names must be unique within the team. The following names are reserved and cannot be used:

• All Users
• All Indexes

Names are checked without regard to capitalization, so all users and All Users are treated as the same reserved name. For a blank name, the portal shows Group name is required. For a case-insensitive duplicate, it shows A group with this name already exists. Open the group actions menu and select Edit group to change the group name or ACU limit. Select Edit models in the Models section to change which Devin models are available.

​

Manage members

From the group details view, select Add user to open the Add users dialog. Select the team members who should belong to the group, then select Save. You can also select Remove next to a member and confirm the removal. Only members of the group’s team can be added. Removing someone from a group does not remove them from the team. They keep their team access; only the controls assigned through that group stop applying. Group administration is team-scoped, so a permission granted only for a group does not confer access to manage that group or other groups. When a user is removed from the team, their group memberships are deleted as well. If they later rejoin, the old group’s model and ACU policies do not silently reapply. Membership is additive. A user can belong to multiple groups at the same time. This matters when controls are resolved. Adding another group can widen a user’s effective model access and raise their ACU limit:

• Non-empty model selections from multiple groups are unioned. Empty selections have no opinion. See Model Provisioning.
• A user’s ACU limit is the highest group ACU limit among their groups, unless an admin has set a manual user override for them. Groups without an ACU limit don’t affect it. See ACU Limits.

​

Delete a group

Open the group actions menu and select Delete group. The confirmation message explains that members keep their team access, but the group’s model availability and ACU limit no longer apply. Deleting a group is not reversible. Its membership and group-level controls are removed, while the members’ team accounts remain intact.