Your profile

In one sentence

The Profile page is your personal control panel — your name and login defaults, the facility and department that loads when you sign in, the passkeys you've enrolled, the calendars you've connected, and the approver delegations you've set up for when you're out.

What you control vs what your admin controls

You control: your full name, default facility / department, your passkeys, your calendar integrations, your own approver delegations.
Your admin controls: your email address, base role, additional roles, seat type, and per-user permission grants. If any of those need to change, the conversation is with your admin via User management.
Nobody but you sees your passkeys or calendar tokens — even your admin can't enumerate the credentials you've enrolled or read your calendar through your account.

Identity

The top section shows three fields:

Full Name — editable. This is what other people see on approvals, audit trails, and activity logs. Identity is snapshotted into audit records at write time, so renaming yourself doesn't rewrite history — past actions keep showing the name you had then.
Email — read-only. Managed by your account; an admin has to change it via the database or support if you legitimately need a new email.
Role — read-only. Your base role (Admin / Standard User). Additional roles you hold aren't shown here; ask your admin if you want to see the full picture.

Defaults — facility and department

If your organization has more than one facility, pick the one you work at most. That facility becomes your active scope at sign-in, so the dashboard, search, and Ask the Library default to records for that site. You can always switch via the scope picker in the top bar without changing your default.

Optionally also pick a default department within that facility. Department scope is used by some pickers (Actions, Ask the Library) to narrow what you see by default. Leave it blank to default to all departments.

These are defaults, not restrictions. Your record-level access is decided by your role + facility scope + per-record access — see Facility & Department Scope and Access Control.

Approver delegations

If you're going to be unavailable, delegate your approvals to a colleague so the queue keeps moving while you're out. The Profile page has the Approver Delegations section for your own delegations — admins manage delegations on behalf of others from Approval Delegations instead.

Add a delegation with:

A delegate (who picks up your approvals).
A start date and end date.
An optional Applies to scope — limit the delegation to specific module types (Documents only, MOC only, etc.). Leave blank to cover every approval routed to you.

Delegations save immediately when you add them — there's no separate save step. The full mechanics live in Approval delegations.

Passkeys

The Security · Passkeys section is where you enroll, name, and remove passkeys. Each passkey is tied to a device — your laptop, your phone, a YubiKey, an iCloud-synced credential.

Enrolling, signing in, and managing passkeys are covered in detail in Passkeys. Two things worth knowing:

Enroll more than one. A single device is a single point of failure. Enroll your phone and your laptop so losing one isn't a recovery event.
If your org turned on the step-up policy, your passkey is the only way to approve. Enroll one before the policy goes live. Auth policy covers the policy and the warning admins see when they enable it.

Removing a passkey is immediate — anyone holding the device can no longer use it to sign in or confirm sensitive actions on your behalf. The credential is invalidated, not just unlinked.

Integrations

The Integrations section connects external calendars so you can import meetings into QFormance.

Google Calendar — connect via Google OAuth. Calendar-only scope; this is separate from the SSO sign-in scopes if your org uses Google SSO. See SSO for the distinction.
Microsoft Calendar (Outlook / Microsoft 365) — same deal: calendar-only scope, distinct from Microsoft SSO sign-in.

Once connected, the Import from calendar button on Meetings shows your recent events. Pick one and the meeting record is pre-filled — title, attendees, transcript (if available).

Disconnecting an integration revokes QFormance's access immediately. Your past imported meetings stay — the integration just stops pulling new events going forward.

What this page doesn't do

Email address changes. Email is your account identifier; changing it has to go through your admin (and, in some cases, support).
Role or seat-type changes. These are admin-controlled at User management. Ask your admin.
Org switching. A single user account belongs to a single organization in the customer-facing product today. There's no cross-org switcher.
Notification preferences. Notifications are currently driven by the system event types (approvals due, mentions, etc.) rather than per-user opt-outs. If you want finer control, raise it as a feature request.

Passkeys — the full passkey enrollment and recovery flow
Approval delegations — the broader delegation model
Single sign-on (SSO)
Meetings — the calendar-import flow your integrations feed into
Facility & department scope
User management — what your admin controls about your account