User & Group Self-Service
Remove Members
Take people out of the groups they no longer belong in, with a request per group on the record.
Completes when the people are removed from the group in the directory, once approved or applied.
https://mcp.avatier.com/mcp
Ask in Plain Language
Run Remove Members from the AI Assistant You Already Use
The group's own Remove Group Member workflow decides who approves, with identity verification first in Avabot and MCP. One completed member removal = one Secure Outcome; failed attempts are never billed.
You: Remove Jordan Lee from the Project Atlas group. Justification: project closed. Avatier: verify: passed · group: Project Atlas · people: 1 selected · request: submitted, may need approval
Why it matters
People Leave Projects. Their Group Memberships Should Too.
A membership nobody removes keeps its access, so taking people out deserves the same record as adding them.
What a removal needs
The groups, the current members to take out, an optional justification, and the approval your Remove Group Member workflow sets.
What goes wrong by hand
Removing people by email or ticket leaves no request per group, no approval record and no activity-log entry to show it happened.
What Remove Members does
You pick from each group's current members, and each group gets its own request. Group Self-Service policy never blocks a removal.
What per-seat pricing charges
Per-seat IAM charges for every licensed seat, whether anyone leaves a group this month or not. Pay Per Identity Action™ charges only for completed member removals.
The Action
How Remove Members Runs
On the web, Remove Members walks through these screens, for one or many groups at once. In Avabot and MCP you verify, name one group, pick from its current members, give an optional justification and confirm.
Verify in Avabot or MCP
Avabot and MCP only. Remove Members starts with identity verification in the conversation, with the methods your policy already allows, such as Security Questions, Google Authenticator, PingID or other push methods, or Identity Challenge Card. On the web there is no extra check beyond your sign-in.
Identity Verification (Avabot and MCP)
Pick the Groups
Open the Remove Members tile and pick one or more groups. The same flow is also under Modify Group > group > Users > Remove.
Pick the Members
Choose Next to see the current members of the selected groups, and tick the people to remove. Select All takes out every current member of each selected group, whatever the search box shows, except people you untick.
Give a Justification
Save opens the confirmation, where you enter a Justification. It is optional.
Confirm
Confirm, and a success message appears. Each group gets its own request, recorded in Request History with a Request ID, and goes through the Remove Group Member 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, each request removes people from one group. Group Self-Service admins and that group's owners can choose to apply it now.
Secure Outcome
What Counts as Done
A Secure Outcome is a completed, verified, policy-compliant identity action. A member removal completes when the people are removed from the group in the directory, once the request is approved, or at once when a Group Self-Service admin applies it. Each group gets its own request, recorded in Request History with a Request ID. One completed member removal = one Secure Outcome.
Evidence
- A Request ID for each group in Request History (filter Remove Group Member, exportable)
- A Group Self-Service 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 Member Removal
Pay per completed member removal. Failed attempts are never billed.
| Compared | Manual or Per-Seat IAM | Remove Members, Pay Per Identity Action™ |
|---|---|---|
| What you pay for | Every licensed seat, whether it acts or not | Completed member removals only |
| Failed attempts | No line between an attempt and a result | Attempts, failures and retries are never billed |
| The work | Manual intervention or tickets | Once approved or applied, the people are removed from each group in the directory, one request per group |
| Evidence | Silent failures and missing audit trails | A Request ID for each group in Request History and a Group Self-Service activity-log entry |
Pay Per Identity Action™ is in invitation-only preview. Pricing is shared with qualified organizations.
Works with the Groups Remove Members Touches
Remove Members writes the change through the group's own Group Self-Service connector: Active Directory (through VDS in tenants that use LDAP authentication), Microsoft Entra ID, AWS or Okta.
- AWS
- Okta
- Microsoft
- Active Directory and Microsoft Entra ID groups, through their Group Self-Service connectors.
- Other Systems
- AWS and Okta groups, through their Group Self-Service connectors.
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
Can I remove a user who is excluded by our Group Self-Service policy?
Yes. The policy only stops additions and never blocks a removal.
Can I empty a group in one go?
Yes, on the web. Select All on the remove step takes out every current member of each selected group, except people you untick.
Does removing a member need approval?
It follows your tenant's Remove Group Member workflow. Group Self-Service admins can choose to skip it.
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 Members
You've Automated the System. Now Secure the Groups.
Pick the groups and the members to take out, and each group's request is recorded in Request History with a Request ID.