User & Group Self-Service
Add Owners
Give each group the owners who will manage it, with a request per group on the record.
Completes when the new owners are saved on the group in Avatier and in the directory, once approved or applied.
https://mcp.avatier.com/mcp
Ask in Plain Language
Run Add Owners from the AI Assistant You Already Use
The tenant's Add Group Owner workflow decides who approves, with identity verification first in Avabot and MCP. One completed owner addition = one Secure Outcome; failed attempts are never billed.
You: Make Dana Cruz an owner of the Finance Reports group. Justification: new team lead. Avatier: verify: passed · group: Finance Reports · owners: 1 selected · request: submitted, may need approval
Why it matters
Every Group Needs Owners Who Answer for It.
Owners manage a group's members, so who becomes an owner, and why, belongs on the record.
What an owner change needs
The groups, the people to make owners, an optional justification, and the approval your Add Group Owner workflow sets.
What goes wrong by hand
Naming owners by email or ticket leaves no request per group, no approval record and no activity-log entry to show it happened.
What Add Owners does
Each group you pick gets its own request. Becoming an owner grants Group Self-Service management of that group, so people your Group Self-Service policy excludes are refused.
What per-seat pricing charges
Per-seat IAM charges for every licensed seat, whether any group gets a new owner this month or not. Pay Per Identity Action™ charges only for completed owner additions.
The Action
How Add Owners Runs
On the web, Add Owners walks through these screens, for one or many groups at once. In Avabot and MCP you verify, name one group, pick people, give an optional justification and confirm.
Verify in Avabot or MCP
Avabot and MCP only. Add Owners starts with identity verification in the conversation, with the methods your policy already allows, such as Security Questions, Google Authenticator, PingID push 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 Add Owners tile and pick one or more groups. Per group, Modify Group > group > Owners > Add does the same, and Change Primary sets the primary owner.
Pick the Owners
Choose Next, search for people and tick them, or use Select All. A group with no owners must get at least two, and a group can have up to 100.
Give a Justification
Save opens the confirmation, where you enter a Justification. It is optional.
Confirm
Confirm. Each group gets its own request, recorded in Request History with a Request ID, and goes through the Add Group Owner 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 adds owners to one group, and Avabot cannot set the primary owner. Group Self-Service admins and that group's existing owners can apply it now.
Secure Outcome
What Counts as Done
A Secure Outcome is a completed, verified, policy-compliant identity action. An owner addition completes when the owners are saved in Avatier's Group Self-Service record and the owner list is written to the directory group, once the request is approved, or at once when a Group Self-Service admin applies it. In Active Directory, the primary owner becomes the group's "managed by" value. One completed owner addition = one Secure Outcome.
Evidence
- A Request ID for each group in Request History (filter Add Group Owner, 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 Owner Addition
Pay per completed owner addition. Failed attempts are never billed.
| Compared | Manual or Per-Seat IAM | Add Owners, Pay Per Identity Action™ |
|---|---|---|
| What you pay for | Every licensed seat, whether it acts or not | Completed owner additions 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 owners are saved in Avatier and written to each directory group, one request per group |
| Evidence | Silent failures and missing audit trails | A Request ID for each 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 Add Owners Touches
Add Owners writes the owner list back through the group's Group Self-Service connector: Active Directory, Microsoft Entra ID, AWS or Okta.
- AWS
- Okta
- Microsoft
- Active Directory groups, where the primary owner becomes "managed by", and Microsoft Entra ID groups.
- 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
How do I change who the primary owner is?
On the web, open Modify Group > the group > Owners and use Change Primary (or swipe an owner and choose Set As Primary); it saves immediately. Avabot cannot change the primary owner.
Is there a limit on owners?
The web pages allow up to 100 owners per group, and a group with no owners must get at least two.
Can I give the same owners to many groups?
Yes. Pick several groups in Add Owners on the web. For large sets of Active Directory groups, use Bulk Assign Owners, which runs in the web app only.
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.
Add Owners
You've Automated the System. Now Secure the Groups.
Pick the groups and their new owners, and each group's request is recorded in Request History with a Request ID.