My Profile
Configure the operator identity shown across Frontline: avatar, first name, last name, email, and Save.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Configure the operator identity shown across Frontline: avatar, first name, last name, email, and Save.
Concepts covered
Step breakdown
- Open My ProfileStart in the My Profile section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
My Profile controls the individual operator identity inside Frontline. The screen shows the avatar area, First Name, Last Name, account Email, and a Save button.
The email is the account identity and is shown as a fixed field. Name fields are the editable identity that teammates see when ownership, tasks, or workspace activity need to point back to a person.
What each control changes
The avatar area controls the visible personal marker. First Name and Last Name control how the operator appears in workspace context. Email identifies the account login. Save applies the profile update.
Use this screen before onboarding teammates into operational workflows so tasks, user rows, and ownership references are recognizable.
Operational outcome
Clean profile identity reduces ambiguity. When Max creates work, when users review Activity, or when admins inspect member access, the person responsible should be obvious.
Operational playbook
Use My Profile as part of the Frontline Admin My Profile operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does My Profile control?
Configure the operator identity shown across Frontline: avatar, first name, last name, email, and Save.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.