Private Preview
Join Waitlist →

Manage profile and account details

Update account details carefully and understand which changes affect identity, notifications, and workspace display.

Updated 31 May 20264 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: May 2026

Outcome

You can review account details, make a safe change, and check where that change appears.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Use the account you intend to update.
Know whether the detail is personal, billing-related, or workspace-visible.
Avoid putting private document details in profile fields.

Visual frame

Review asset

Profile and account settings storyboard

Synthetic account frame only. It uses fake account details and keeps billing, identity verification, and support escalation separate.

FieldsVisible only
UpdateOne at a time
ReviewCheck display

Synthetic frame

Profile settings

Check editable fields first.

Display nameEditable
EmailAccount controlled
Team roleAdmin controlled
Knowing the field owner prevents support requests with the wrong scope.

Manage profile and account details workflow frame

Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.

FindReview visible fields
DecideChange one field at a time
VerifyCheck where it appears

Guided steps

Follow the task, then check the result.

Review visible fields

Check the fields that can be changed and read any note about where they appear.

Success check: You know which fields are profile-only and which may be visible elsewhere.

Change one field at a time

Make a single update, save it, and check for validation messages before editing another field.

Success check: The change saves without unexpected errors.

Check where it appears

Open the relevant account, team, or sharing surface to verify the displayed value is correct.

Success check: The updated detail appears only where expected.

Branch questions

Completion check

Fields were reviewed before editing.
Private document details were not added to profile fields.
Display state was checked after saving.

Support boundary

Support can use by default

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Intent ID
  • Article slug
  • App route

Requires your consent

  • User-written description
  • Email address
  • Explicit attachment
  • Redacted sample
  • Support bundle previewed to the user

Not collected by default

  • Raw original document text
  • Full local file paths
  • Pasted private content
  • Unmasked screenshots
  • Replay capture

Safe support summary

Copy a scrubbed handoff.

Redactorr KB support summary

Article: /knowledge-base/profile-account-settings
Selected issue: A profile field will not save.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route

Requires explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture

User note:
- Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.

Article details

Manage profile and account details

Update account details carefully and understand which changes affect identity, notifications, and workspace display.

Use this guide when the profile and account settings surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.

Outcome

You can review account details, make a safe change, and check where that change appears.

Before You Start

  • Use the account you intend to update.
  • Know whether the detail is personal, billing-related, or workspace-visible.
  • Avoid putting private document details in profile fields.

1. Review visible fields

Check the fields that can be changed and read any note about where they appear.

Check before you continue: You know which fields are profile-only and which may be visible elsewhere.

2. Change one field at a time

Make a single update, save it, and check for validation messages before editing another field.

Check before you continue: The change saves without unexpected errors.

3. Check where it appears

Open the relevant account, team, or sharing surface to verify the displayed value is correct.

Check before you continue: The updated detail appears only where expected.

Completion Check

  • Fields were reviewed before editing.
  • Private document details were not added to profile fields.
  • Display state was checked after saving.

Safe Examples

  • A synthetic display name such as Alex Example.
  • A masked email address where only the domain is visible.

If You Need Support

Contact support when:

  • A profile field will not save.
  • An account detail appears in an unexpected workspace surface.

Include only support-safe context:

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.

Still stuck?

Copy a safe article handoff.

Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: profile-account-settings
Route: /knowledge-base/profile-account-settings
Selected issue: A profile field will not save.

Safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
- Screen name or article section
- Action name

Only include with explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
- Hidden diagnostic uploads

User note:
- Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.

Support case builder

One case format, wherever you start.

This is the same support case shape used by diagnostics and article handoffs.

Safe to include
  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Article slug
  • Selected issue
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide