English
Frontline Admin · My Profile · Interactive walkthrough

My Profile

Configure the operator identity shown across Frontline: avatar, first name, last name, email, and Save.

Interactive walkthrough4 min
My Profile settings with avatar, name fields, account email, and Save
Screen guideMy Profile

Check which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.

What My Profile is for

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 this page to identify what the control changes, which source context it uses, who owns the result, and where to verify it.

Use the page to identify the trigger, source data, owner, visible result, and review point before changing production behavior.

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.

Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.

Troubleshooting

If the result is wrong, debug in this order: source data, permissions, connected tools, required fields, workflow logs, then any generated output used later.

When debugging, open the related CRM record, Max activity, workflow run, or integration log first. Fix the source data or rule before adding more automation.

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.