Account Settings

Overview

Account settings centralize identity, company defaults, password updates, team access, and notification controls so operational changes stay intentional and traceable.

How it works

• Profile and company fields establish contact, identity, and import defaults for dashboard workflows.
• Security, users, and notification settings define password changes, access boundaries, and operational email alerts.

Important fields

• Contact email: Receives billing receipts and critical workspace alerts.
• Default import country: Used to normalize phone numbers during CSV imports.

Use cases

• Owner profile maintenance
• Security hardening for active workspaces

Tips

• Good to know: stale contact emails are a common reason low-balance or incident alerts are missed.

My Profile

Personal profile data determines where operational communication is delivered.

Confirm your primary email can receive billing and support notifications.

• Name and email updates keep ownership and contact records accurate across billing and support workflows.
• Saved profile values become defaults used by account-level notifications and identity displays.
• Contact email: Receives billing receipts and alerts.
• Good to know: profile updates should be reviewed after role or ownership changes.
• Owner contact refresh
• Admin handoff preparation

Company Profile

Company profile values influence defaults used in imports and scheduled workflows.

Align timezone and locale defaults with your active launch geography.

• Workspace identity and locale settings are saved at the company layer for consistent multi-user behavior.
• Timezone and import defaults reduce avoidable formatting and scheduling mismatches across teams.
• Timezone: Used for scheduled launches.
• Good to know: default import country is especially helpful for teams handling mixed CSV sources.
• Multi-team scheduling consistency
• Import normalization

Security

Security settings let workspace owners change account passwords without leaving the dashboard.

Update passwords after team turnover or if you suspect credential exposure.

• The Security tab accepts your current password plus a new password and confirmation before saving.
• Password updates apply immediately to your login credentials for the client dashboard.
• Current password: Required to authorize a password change.
• New password: Must meet the platform password requirements shown in the form.
• Good to know: two-factor authentication and active session management are not available in the dashboard today.
• Routine credential rotation
• Post-incident password reset

Users

User management ties access to responsibility so workflows remain secure and auditable.

Review each member's permissions against current responsibilities before your next campaign cycle.

• Invites grant entry through role assignment, while feature toggles constrain what each member can access.
• Role and access updates apply centrally, preventing inconsistent permissions across feature groups.
• Role: Owner vs Member access levels.
• Good to know: least-privilege access lowers accidental launch risk without slowing specialist work.
• New teammate onboarding
• Permission right-sizing

Notifications

Notification policy decides who learns about operational events in time to act.

Enable critical alerts for owners and validate delivery with a controlled test event.

• Alert toggles map events like low balance and launch summaries to email recipients for proactive response.
• Saved preferences create a predictable communication loop across billing, calling, and campaign activity.
• Low balance alerts: Email when credits are low.
• Good to know: alert fatigue drops when only actionable notifications are enabled per role.
• Low-balance prevention
• Launch oversight

Next step

Verify profile, company defaults, and key alert settings before your next scheduled launch window.