Manage profile and account security
Profile and security settings protect the individual AtomicPay account that accesses one or more business workspaces. This is separate from team roles, permissions, and product access, which control what a collaborator can do inside a business.
Use this guide for owner and collaborator account hygiene, especially before launch, during team growth, or after offboarding.
What profile and security control
| Area | Purpose |
|---|---|
| Personal account identity | Display name, email, and profile details for the login. |
| Password and recovery | Protects access to all businesses the user can open. |
| Personal preferences | Affects the individual account experience where available. |
| Account separation | Keeps one login from being shared across multiple people. |
| Security hygiene | Reduces wrong-account access and invite problems. |
Profile vs business team settings
| Topic | Manage in Profile | Manage in team settings |
|---|---|---|
| Password reset | Yes | No |
| Collaborator invite | No | Yes. See team roles. |
| Finance permissions | No | Yes. See finance permissions. |
| Product access | No | Yes |
| Wrong-account invite issue | Indirectly | Yes. See invite troubleshooting. |
Secure your account
- Open Profile from the account menu.
[Screenshot: Account menu open — Profile or Account settings option highlighted.]
- Confirm the email on the account is correct and actively monitored.
[Screenshot: Profile settings page — email, display name, and password change option in the account menu.]
- Update profile photo or display details when needed.
[Screenshot: Profile photo or display name field — updated and saved.]
- Change your password if credentials may be shared, weak, or stale.
[Screenshot: Change password form — current and new password fields.]
- Use password recovery only from the official login page if you are locked out.
[Screenshot: Login page — Forgot password link on official AtomicPay login.]
- Avoid sharing one login across multiple collaborators.
[Screenshot: Team invite flow — separate invite sent instead of shared credentials.]
- Invite teammates through the business team area instead of sharing passwords.
[Screenshot: Team invite modal — collaborator invited with role and email.]
- Review which business workspaces the account can access.
[Screenshot: Workspace switcher — all businesses this login can open listed.]
What to verify for launch teams
| Check | Why it matters |
|---|---|
| Owner account uses a monitored email | Recovery and finance notices reach the right person. |
| Collaborators have their own logins | Enables remove collaborators without disrupting everyone. |
| No shared password in chat or docs | Reduces account takeover and wrong-account access. |
| Finance users use appropriate finance permissions | Personal account security does not replace permission design. |
| Offboarded users are removed from the business | Old access should be revoked promptly. |
Best practices
- Use a business-monitored email for the primary owner account.
- Give each collaborator their own invite and role.
- Remove old access when someone leaves. See remove collaborators safely.
- Do not store passwords in shared documents or support tickets.
- Review accepted invites so the right person joined the right business workspace.
Common mistakes
- Sharing one owner login with the whole launch team.
- Ignoring a compromised password because “it’s just the seller account.”
- Confusing profile settings with finance permissions.
- Letting a collaborator keep access after offboarding because the login still exists.
- Accepting a team invite on a personal email that nobody monitors.
FAQ
Is profile security the same as team permissions?
No. Profile controls your personal account. Team roles and product access control business permissions.
What if I forgot my password?
Use the password recovery flow from the login page. If recovery fails, contact support with the account email and business context.
What if someone joined with the wrong account?
Should finance users share one login?
No. Give each finance user their own account and only the finance permissions they need.