Skip to main content
Maidpilot

← Help Center

Account Settings

Update your profile, password, and notification preferences.

Open Settings → Profile to update your name, email, and password for the signed-in user. Profile settings only affect your account; company-wide branding, hours, and AI knowledge live under Company and AI Secretary settings.

Update your profile

Keep your display name and email current so teammates and support can identify you. Use an email you check regularly if the platform sends security or account notices.

Secure your account

Use a strong password and keep your sign-in details private. If you suspect unauthorized access, change your password immediately and contact support from the dashboard. Avoid sharing passwords with coworkers; each person should have their own account and role.

Choose notification preferences

Adjust notification preferences so you get the alerts you care about, for example new leads or AI escalations, without unnecessary noise. Start with the alerts tied to your daily workflow and add more only when the team needs them.

Understand profile vs company settings

  • Your profile controls your user name, email, password, and personal preferences.
  • Company settings control hours, service area, branding, and team roles.
  • AI Secretary settings control knowledge, escalation, and call language.
  • Billing settings control plan, add-ons, and payment method.

Knowing which setting is which avoids the common mistake of updating a personal preference and expecting it to change company-wide behavior.

When your role or employment changes

If you leave the company or change roles, an owner can update team access from the Team page. Keep that step in mind when a teammate is promoted, moves to a different role, or finishes working with your company.

Change or reset your password

Use a unique password and change it immediately if you suspect your account was shared, reused, or exposed. After changing the password, check the profile email and any active notification preferences before continuing work. Do not ask a coworker to keep your password; role-based access is safer and keeps team activity attributable.

Keep security data accurate

Treat the profile email as a recovery address. If you switch roles, keep it accurate so account notices and support replies reach you. Remove old email addresses and update display names when a person changes their legal or business name.

Audit settings when a user changes

When an employee is promoted, moved, or leaves, review their profile, team role, notification preferences, and any connected access at the same time. Update the role first, then reset preferences if they no longer fit. This avoids a situation where a former teammate still receives customer alerts or can open areas they no longer need.

Set up account recovery before you need it

Keep the profile email current and accessible before an account problem happens. If the email is correct, support can verify the owner or user through the normal account process. When someone changes their work email, update the profile and remove the old address so time-sensitive alerts do not continue going to an abandoned inbox.

Map notifications to the workday

For each notification preference, name the person who needs it and the time of day they can act on it. An owner may want alerts for billing and handoffs but not for every routine lead. A manager may want booking requests and customer activity. A cleaner may want job changes but not payment details. The preference page is easier to tune with that map in front of you.

Write a password change routine

Change the password when an account may have been shared, a device was lost, or a person with access left. After the change, sign out of old sessions if that option exists, update the password manager, and confirm the profile email still belongs to the right person. Do not use the same password across other business systems.

Run a short security review

Once a quarter, sit with the account owner and review the profile email, active team members, roles, and notification preferences that carry customer information. Confirm that every active user still works in the role shown and that no former teammate has access to customer alerts. Record the review date and the one fix made, even if the fix is only a corrected email address.

Prepare an account settings handoff

Write down who manages the account email, who can change the payment method, and who should receive security notices. When the owner changes, update the profile email and team role in the same session. A handoff note prevents customer alerts and billing notifications from going to an old address after the responsible person has changed.

Make preferences reviewable by role

Instead of tuning each user's preferences from memory, write the intended preference set for owner, manager, and field staff on one page. Use that page when a new user is created or a role changes. The page keeps account settings consistent and gives the team a clear reason why each person receives the alerts they do.

Check recovery after every account change

After changing an email, role, or notification preference, confirm that account recovery still works for the person who needs it. Send a test security notice if the platform provides one and check that it reaches the correct inbox. Store the recovery email and the current owner in the handoff note so the next security review does not depend on memory.

Finish with a settings snapshot

After any account change, write a one-line snapshot of the profile email, role, and key notification preference. Keep the snapshots in a simple log so the team can see what changed, when it changed, and why. This makes future troubleshooting faster and avoids guessing whether an old alert address is still active.

Common account settings mistakes

  • Keeping an old work email that no longer receives security or billing notices.
  • Sharing a password because a teammate lacks the permission needed for a task.
  • Changing a personal notification preference when the real issue is a missing role or access.
  • Leaving a former user's profile active after they stop working with the company.
  • Forgetting to update recovery details when the account owner changes.

Run a quarterly account review

Every three months, review the profile email, password policy, active users, roles, and notification preferences that carry customer data. Confirm that each active user still belongs in the role shown and that every alert address is current. Write the date and the one correction made. A quarterly review keeps account security accurate without creating a lengthy audit process.

Prepare for a faster support conversation

When account support is needed, include the profile email, the page or feature where the issue appears, and the result expected. If the issue is about access, name the user, the role, and the module they cannot open. If it is about email delivery, confirm the address shown in settings and the spam folder before writing. This context reduces back-and-forth and keeps sensitive details out of plain messages.

Turn this guide into a working step

A help article becomes useful when you apply it to a real part of your operation. Open the matching dashboard page, make one small change, and verify the effect before moving to the next setting.

  1. Open the dashboard section named in the guide and compare what you see with the steps above.
  2. Use a realistic example from your business, such as one customer, one service, or one upcoming week.
  3. Ask a teammate to complete the same step and confirm they understand the result.
  4. Check notifications or the linked record afterward so the change is reflected where the team works.

If something looks different in your account

The exact label or placement can change when features are added or refined. Start by checking your plan, because some settings, channels, add-ons, and AI tools are only available after they are enabled for your company.

  • Confirm the feature is active on your plan or add-on.
  • Check whether the setting should be changed at company level, user level, or service level.
  • Refresh the page and reproduce the issue once with a recent browser.
  • Note the exact page, setting, and expected outcome before contacting support.

What to include when you need help

Write down the goal you wanted to accomplish, the steps you tried, the message or behavior you saw, and whether the problem affects one customer, one user, or the whole company. That context lets support connect the issue to the right setting instead of starting a generic investigation.

Continue exploring

Can't find what you're looking for?

Contact Support FAQ