User & Group Self-Service

Remove Nested Groups

Take nested groups out of their parent groups, shown on screen as Remove Group Memberships, with a request per parent group.

Completes when the nested groups are removed from the parent group in the directory, once approved or applied.

Server URL: https://mcp.avatier.com/mcp

Ask in Plain Language

Run Remove Nested Groups from the AI Assistant You Already Use

The tenant's Remove Group Membership workflow decides who approves, with identity verification first in Avabot and MCP. One completed nested-group removal = one Secure Outcome; failed attempts are never billed.

You: Take the Contractors group out of All Staff. Justification: contractors no longer need staff access. Avatier: verify: passed · parent: All Staff · groups: 1 selected · request: submitted, may need approval

Why it matters

A Nested Group Keeps the Parent's Access Until Someone Removes It.

Every member of a nested group inherits what the parent grants, so taking it out deserves a record too.

  • What a removal needs

    The parent groups, the nested groups to take out, an optional justification, and the approval your Remove Group Membership workflow sets.

  • What goes wrong by hand

    Removing nested groups by email or ticket leaves no request per parent group, no approval record and no activity-log entry to show it happened.

  • What Remove Nested Groups does

    Only the nesting link is removed; both groups remain. Group Self-Service policy never blocks a removal.

  • What per-seat pricing charges

    Per-seat IAM charges for every licensed seat, whether any nesting is removed this month or not. Pay Per Identity Action™ charges only for completed nested-group removals.

The Action

How Remove Nested Groups Runs

On the web, the Remove Nested Groups tile opens the Remove Group Memberships screens below, for one or many parent groups at once. In Avabot and MCP you verify, name the parent group, pick from its nested groups, give an optional justification and confirm.

  1. Verify in Avabot or MCP

    Avabot and MCP only. Remove Nested Groups starts with identity verification in the conversation, with the methods your policy already allows. On the web there is no extra check beyond your sign-in.

    Identity Verification (Avabot and MCP)

  2. Pick the Parent Groups

    Open the Remove Nested Groups tile and pick one or more parent groups on the Remove Group Memberships screen. Okta groups are not listed. The same flow is also under Modify Group > group > Nested Groups.

  3. Pick the Nested Groups

    Choose Next to see the groups currently nested in them, and tick the ones to take out.

  4. Give a Justification

    Save opens the confirmation, where you enter a Justification. It is optional.

  5. Confirm

    Confirm. Each parent group gets its own request, recorded in Request History with a Request ID (as Remove Group Membership), and goes through the Remove Group Membership workflow. Group Self-Service admins are asked whether to use workflow and can apply the change at once.

    Approval point

Available on Web, Mobile, Teams, Avabot chat and MCP.

Avabot chat and MCP require the current (.NET 10) Avatier server.

In Avabot chat and MCP, Group Self-Service admins and the group's owners can apply the removal now.

Secure Outcome

What Counts as Done

A Secure Outcome is a completed, verified, policy-compliant identity action. A nested-group removal completes when the nested groups are removed from the parent group in the directory, once the request is approved, or at once when a Group Self-Service admin applies it. Each parent group gets its own request, recorded in Request History with a Request ID. One completed nested-group removal = one Secure Outcome.

Evidence

  • A Request ID for each parent group in Request History (filter Remove Group Membership, exportable)
  • An activity-log entry

Guardrails

Your Assistant Asks. Avatier Decides.

  • Verified First

    Avatier verifies the person before sensitive changes, with the methods your policy already allows.

  • Acts as the Signed-In User

    OAuth sign-in to your own tenant. No shared service account, no API key to manage.

  • Never Makes Up Values

    The connector only sends what the person actually said, and asks when something is missing.

  • Every Request Recorded

    Requests land in Request History, ready to review and export.

Pay Per Identity Action™

Pay per Completed Nested-Group Removal

Pay per completed nested-group removal. Failed attempts are never billed.

Manual or Per-Seat IAM vs Remove Nested Groups on Pay Per Identity Action™
ComparedManual or Per-Seat IAMRemove Nested Groups, Pay Per Identity Action™
What you pay forEvery licensed seat, whether it acts or notCompleted nested-group removals only
Failed attemptsNo line between an attempt and a resultAttempts, failures and retries are never billed
The workManual intervention or ticketsOnce approved or applied, the nested groups are taken out of each parent group in the directory, and both groups remain
EvidenceSilent failures and missing audit trailsA Request ID for each parent group in Request History and an activity-log entry

Pay Per Identity Action™ is in invitation-only preview. Pricing is shared with qualified organizations.

Works with the Groups Remove Nested Groups Touches

Remove Nested Groups works on Active Directory groups, including Active Directory through VDS in tenants that use LDAP authentication. Microsoft Entra ID, AWS and Okta groups do not support nested groups.

  • Active Directory
Microsoft
Active Directory groups only.

Avatier MCP

New to Avatier MCP?

The Model Context Protocol is an open standard, stewarded by the Linux Foundation, that lets AI assistants call real systems through connectors instead of custom integrations.

Up and Running in Under a Minute

One URL works in every MCP client. Pick yours, copy, paste, sign in.

  • Microsoft Copilot Studio
  • Claude Code
  • OpenAI Codex
  • Cursor

Frequently Asked Questions

Does removing a nested group delete that group?

No. It only takes the group out of the parent; both groups remain.

Can policy block a nested-group removal?

No. Group Self-Service policy stops additions only.

Can I remove nested groups from several parent groups at once?

Yes, on the web. Select several parent groups, then the nested groups to remove.

Is Avatier secure enough for large enterprises or regulated industries?

Absolutely. Avatier applies zero-trust controls, maintains fully auditable identity records, and holds SOC 2 Type II and ISO 27001 certifications. It also helps organizations support requirements and evidence needs associated with NIST, SOX, HIPAA, and GDPR. Every provisioning action is policy-enforced and auditable.

What is AI-driven configuration?

Avatier's AI-driven config turns plain-language intent into working policy. Rather than hand-coding rules, connectors, and roles, administrators describe what they need and Avatier recommends and sets up provisioning rules, role mappings, and workflows, then validates them before they go live. It shortens deployment from months to days and keeps configuration consistent, auditable, and free of custom scripting.

What is Pay Per Identity Action™?

Pay Per Identity Action™ is Avatier's pricing mechanic. Customers pay only for completed, verified, policy-compliant identity actions, called Secure Outcomes.

Is it the same as pay-per-action advertising?

No. Pay per action (PPA) is performance-marketing vocabulary for paying when an ad converts. Pay Per Identity Action™ charges for completed identity work.

How do I get started?

Getting started is free, deployment services are included, and a 45-day money-back guarantee applies. Contact Avatier for pricing for your organization.

What is MCP?

The Model Context Protocol is an open standard, stewarded by the Linux Foundation, that lets AI assistants call real systems through connectors instead of custom integrations.

How is it billed?

Pay Per Identity Action™ is in invitation-only preview: each completed, verified action is one Secure Outcome, and attempts, failures and retries are never billed.

Remove Nested Groups

You've Automated the System. Now Secure the Groups.

Pick the parent groups and the nested groups to take out, and each parent group's request is recorded in Request History with a Request ID.