#Profile Settings

#Overview

Profile settings let you review the identity and security posture attached to your current portal session. Partner Admin and Partner User sessions use Settings Profile at /settings?section=profile to edit their own supported account profile fields by reusing the Account Profile form and /api/account/profile contract. Client Manager and Client Staff users use the same Settings Profile section for a managed read-only profile summary. Client Admin users use the Account shell at /account; legacy /settings?section=profile links redirect to /account?section=profile for that role.

Client Manager and Client Staff display name and email address remain managed identity fields in the Settings Profile panel. The portal does not store local-only Settings profile values and does not offer unaudited identity changes. If either value is wrong in Settings Profile, open Support in the signed-in portal and create an account ticket for a profile update request.

Client Admin and partner users can edit the implemented Account Profile fields that the backend exposes for self-service: first name, last name, mobile number, timezone, and portal language. Email address remains read-only in Account Profile. Verified email-change requests use the dedicated email-change flow when available. Security and MFA management for Client Admin users is in Account > Security. Partner MFA appears in Settings as a required, operations-managed, non-editable summary.

#Prerequisites

• You are signed in to the AiDial portal. See Signing In for instructions.
• Your current session belongs to an active tenant.
• Client Admin users need the /account shell for self-service profile edits. Partner Admin and Partner User sessions edit their own profile from /settings?section=profile. Client Manager and Client Staff users use /settings?section=profile for the managed profile summary.
• If MFA remediation is required, other protected portal areas remain blocked until the identity-provider setup or verification is completed and the portal security status is refreshed.

#Reviewing Your Profile

For Partner Admin and Partner User:

1. Select Settings from the sidebar.
2. Open the Profile section at /settings?section=profile.
3. Review and edit the supported Account Profile fields: first name, last name, mobile number, timezone, and portal language.
4. Review the read-only email address and email verification badge when one is available.
5. Review the required operations-managed MFA summary. MFA is required for integration-secret changes, key rotation, signing-secret rotation, SCIM token rotation, and SSO/SCIM setup. Step-up on publish, rollback, and compliance remains pending the audit mirror.

For Client Manager and Client Staff:

1. Select Settings from the sidebar.
2. Open the Profile section at /settings?section=profile.
3. Review the profile and security summary:

• Display name - the name from your authenticated session, or Unavailable when the session does not provide one
• Email address - the email from your authenticated session, or Unavailable when the session does not provide one
• Portal role - your current server-resolved portal role
• Allowed factors - MFA factors currently permitted by role, policy, and tenant state
• Enrolled factors - MFA factors currently reported for your account
• Security status - whether MFA is required, satisfied, pending, failed, optional, or unavailable

1. Use Refresh security status after completing MFA setup or verification with the identity provider.

For Client Admin:

1. Open Profile from the account menu, or go to /account?section=profile.
2. Review and edit the supported Account Profile fields: first name, last name, mobile number, timezone, and portal language.
3. Review the read-only email address and email verification badge when one is available.
4. Use Account > Security at /account?section=security for password, two-factor, recovery-code, and recent-activity security surfaces.

#Ownership Matrix

#MFA Actions

Settings Profile and Account Security show MFA actions only when the current session and account security state make them available. Partner Settings Profile shows the required operations-managed MFA summary instead of edit controls.

Other protected portal areas remain blocked while mandatory MFA is not compliant. Complete setup or verification with the provider, then return to the profile or security surface and refresh the security status.

If you lose access to your authenticator, use a provider-issued recovery code during sign-in. If you no longer have recovery codes, contact your organisation administrator or help@aidial.com.au. The Profile section can show reminders and trusted provider links, but it cannot bypass MFA, reveal one-time codes, or reset your authenticator directly.

#Field Reference

#Access, Scope, and Runtime Behaviour

The browser uses your signed-in portal session. You do not need to enter or send an API key, and the browser must not send X-API-Key.

Profile details and MFA actions are scoped to the current signed-in user and active tenant. Browser calls go to portal route handlers such as /api/settings/profile, /api/settings/profile/mfa-lifecycle, /api/auth/mfa-sms-enrol, and /api/account/profile; those server-side routes inject the bearer token and call aidial_api. API routes enforce their own auth, CSRF, tenant checks, and route security headers because middleware does not protect /api/**.

Settings Profile reads MFA lifecycle state from aidial_api through /v1/portal-mfa-lifecycle. Account Profile reads and saves Client Admin, Partner Admin, and Partner User profile details through /v1/account/profile. The Account Profile save path requires an If-Match ETag, rejects unsupported fields before calling the API, and refreshes the trusted session context after a successful save.

MFA actions may be rate-limited and require a current trusted identity-provider state. If your tenant, session, or MFA state cannot be verified, the portal blocks the action and asks you to refresh or sign in again.

#Common Issues

#Related Pages

• Settings Overview
• Signing In
• Active Sessions