User & Group Self-Service
Update Profile
People update their own profile details, and managers update their reports', through a request with a justification.
Completes when the directory attributes change, once the request is approved and executed or at the scheduled time.
https://mcp.avatier.com/mcp
Ask in Plain Language
Run Update Profile from the AI Assistant You Already Use
Submitted as a Lifecycle Management request through your tenant's approval workflow, with identity verification first in Avabot and MCP. One completed profile update = one Secure Outcome; failed attempts are never billed.
You: Update my mobile phone number to 555-0142. Justification: new phone. Avatier: verify: passed · field: mobile phone · read back: confirmed · request: submitted, may need approval
Why it matters
Profile Changes Should Reach the Directory Through a Request.
Names, titles, phones and departments live in the directory, and changes to them belong on the record.
What a profile update needs
The user, new values for the fields your admin made editable, a justification, and the approval your workflow sets.
What goes wrong by hand
Emailing IT for a title or phone change leaves no request, no approval record and no way to follow the change.
What Update Profile does
Only the attributes your admin made visible or editable appear, required fields are enforced, and the change is submitted as a request with a Request ID.
What per-seat pricing charges
Per-seat IAM charges for every licensed seat, whether anyone's profile changes this month or not. Pay Per Identity Action™ charges only for completed profile updates.
The Action
How Update Profile Runs
On the web, Update Profile walks through these screens. In Avabot and MCP you verify, Avabot reads the profile and offers the editable fields, then reads your change back and submits only on yes.
Verify in Avabot or MCP
Avabot and MCP only. Update Profile 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. In external MCP, an operator can let a recent connector sign-in stand in for it; that option is off by default.
Identity Verification (Avabot and MCP)
Select the User
Open the Update Profile tile and search for the user: yourself, or someone you can request for, such as a direct report or someone delegated or proxied to you. Okta-sourced users cannot be selected.
Choose When and Why
Choose Update Now or a scheduled time, and type a Justification. Workflow admins are first asked whether to use workflow.
Edit the Profile
Edit the profile form. Only the attributes your admin made visible or editable appear, and required fields are enforced. Fields can include name, contact details, phones, address and country, job title, department and company, manager and assistant, photo, and fields specific to your directory.
Submit
Submit and see the confirmation. The change is recorded in Request History with a Request ID and follows your tenant's approval workflow. A workflow admin who skips workflow applies it without approval.
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, Update Profile cannot change the manager, assistant or photo, and it refuses the whole update on tenants where the assistant field is editable.
Secure Outcome
What Counts as Done
A Secure Outcome is a completed, verified, policy-compliant identity action. A profile update completes when the directory attributes change: once the request is approved and executed, or at the scheduled time. Changes are not immediate unless a workflow admin skips workflow. One completed profile update = one Secure Outcome.
Evidence
- A Request ID in Request History (exportable)
- The request in Pending Requests, for approvers
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 Profile Update
Pay per completed profile update. Failed attempts are never billed.
| Compared | Manual or Per-Seat IAM | Update Profile, Pay Per Identity Action™ |
|---|---|---|
| What you pay for | Every licensed seat, whether it acts or not | Completed profile updates 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 and executed, or at the scheduled time, the profile attributes change in the directory |
| Evidence | Silent failures and missing audit trails | A Request ID in Request History, also shown to approvers in Pending Requests |
Pay Per Identity Action™ is in invitation-only preview. Pricing is shared with qualified organizations.
Works with the Directories an Update Profile Touches
Update Profile changes directory attributes in Active Directory, Microsoft Entra ID and LDAP. Users from an Okta directory cannot be selected.
- LDAP
- Microsoft
- Active Directory and Microsoft Entra ID attributes.
- Other Directories
- LDAP attributes. Okta-sourced users cannot be targeted.
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
I changed my phone number, but the directory still shows the old one. Why?
Update Profile submits a request. The directory changes only after it is approved and executed, and you can follow it in Request History.
Can I change my manager?
In the web form, yes, through the manager picker if your admin made it editable. Avabot does not change managers.
Which fields can I edit?
Your admin decides, attribute by attribute, what is shown, editable and required.
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.
Update Profile
You've Automated the System. Now Secure Self-Service.
Change the fields your admin allows, give a reason, and the update is recorded in Request History with a Request ID.