Account Settings and Security
Protect account access, keep business-wide preferences current and make high-impact changes through a controlled, verifiable process.
Confirm your role before changing account-wide settings
Account settings control your profile, preferences, security and several workspace-wide behaviours. Access depends on your role. Before changing a shared setting, confirm authorization, record the current state, change one item, verify the intended result and review any connected workflow that may depend on it.
Match the change to the right level of authority
Seeing a setting does not always mean it should be changed. Confirm the active ConvoRev account, the reason for the change, the approved owner and the people or workflows that may be affected.
Your profile and preferences
Update your own display information, sign-in protection and permitted personal preferences.
Verify what teammates or customers may see.Shared operating controls
Account name, timezone, AI pause state and other shared behaviours can affect the wider team.
Use an authorized administrator and a change record.Security, data and integrations
Credentials, exports, access removal and deletion require additional verification and ownership.
Stop if the authority or impact is unclear.Check the active workspace and setting owner.
Record the current value and reason.
Avoid unrelated edits in the same pass.
Verify the setting and dependent paths.
Document the result and follow-up.
Keep identity and operating context current
Review the account name, contact information, timezone and other available operating preferences. Interface options can vary with your role and account configuration, so change only settings you can identify and verify.
Helps teammates distinguish the correct business or workspace.
Navigation, notifications and account switching show the intended identity.
Support, account notices or operational communication may depend on current information.
The approved business contact is correct and still monitored.
Schedules, appointments, reports and message timing can depend on it.
Calendar availability, active hours and quiet-hour boundaries remain correct.
Names or profile images may appear to teammates or customers in supported experiences.
Every visible identity is approved, recognizable and not a temporary test value.
Use the account-wide pause only for the right scope
The master pause is an emergency or maintenance control for AI replies across the account. Use it when a serious knowledge, connection, policy or security issue requires review. It does not disconnect channels, close conversations or assign a person to monitor incoming messages.
Broad AI reply stop
Use for a material issue that affects multiple conversations or the shared configuration. Establish human coverage before pausing.
One conversation
Use when a person needs to take over a specific contact without stopping AI replies elsewhere. See Pause the AI Agent for a Contact.
Outbound timing
Use for approved proactive or scheduled messaging windows. Quiet hours do not necessarily stop replies to new inbound messages.
- Assign human coverage.Name the person or queue responsible for new inbound conversations during the pause.
- Record the reason and start time.State the affected behaviour, channels and known customer impact.
- Correct the underlying issue.Update the authoritative knowledge, instruction, connection or policy—not only the visible symptom.
- Retest critical scenarios.Verify normal questions, exceptions, handoffs and enabled next actions before resuming.
- Resume deliberately.Confirm ownership, monitor the first live conversations and document the decision.
Protect every person with an individual identity
Use a unique password and enable two-factor authentication when available. Invite each teammate separately so access, activity and removal remain attributable to one person. Never share a sign-in between team members.
Use a password not reused on another service and store it with an approved password manager.
Use an approved second factor when available and store recovery methods securely.
Keep the approved business email and recovery ownership current without sharing codes.
Give each person their own invitation and the minimum permissions required for the role.
Stop and verify unfamiliar reset messages, recovery requests or new-device notices before acting.
Secure the account, preserve safe evidence, review sessions and notify ConvoRev promptly.
If your organization uses an identity provider, follow its configured sign-in, offboarding and recovery process. A password reset or email change may require additional identity verification.
Review more than the login
Review active sessions after a lost device, suspected access issue, password change or staff departure. End sessions you do not recognize. Then check the wider authorization footprint—a password change does not necessarily revoke every external connection.
Every active session belongs to a current authorized user.
A device, location or activity is unfamiliar.
Roles match present responsibilities and pending invitations are expected.
A person leaves, changes roles or no longer needs access.
Business ownership, administrators and connected accounts are current.
An owner, sender, calendar or business asset changes.
Each authorization has a current owner, approved purpose and minimum scope.
A workflow is retired, credentials rotate or unexplained activity appears.
Security and operational events reach the correct monitored destination.
A recipient or responsibility changes.
Stabilize first, then investigate
If you suspect unauthorized access or unexplained account changes, reduce risk without destroying useful evidence. Do not continue normal configuration work until the account owner confirms a safe recovery path.
Protect access and customer operations
Use the approved recovery path, end unknown sessions where available, pause affected AI activity if required and assign human coverage.
Check the complete authorization footprint
Review team access, channels, calendars, integrations, notification recipients and recent configuration changes before returning to normal operation.
- Record safe facts.Note the account, approximate time, affected area, observed behaviour and recognized versus unrecognized activity.
- Protect the sign-in.Use the approved password, two-factor and recovery process; do not share recovery material.
- Contain operational risk.Pause affected automation only when necessary and ensure a person monitors incoming conversations.
- Review connected access.Check sessions, users, channels, calendars, integrations and notification destinations.
- Verify before resuming.Retest critical customer paths and confirm the account owner approves normal operation.
Keep credentials, exports and deletion controlled
Integration credentials and similar technical controls should be handled only by authorized administrators through the approved implementation process. Never paste a secret into an AI instruction, knowledge source, conversation, note or support email.
Use secure authorization
Prefer the supported connection flow. Limit access, record ownership and rotate credentials through the originating system when required.
Never store secrets in customer-facing content.Use minimum necessary data
Confirm purpose, scope, authorized recipient, protection and retention before creating or sharing a file.
See Download Your Data.Treat removal as high impact
Confirm owner approval, required records, retention needs and external connections before requesting an irreversible account action.
Stop if any dependency is unclear.Diagnose the scope before repeating a change
Active account, user role, account configuration and whether the control belongs to a connected system.
Ask an authorized administrator to verify access; do not work around the permission boundary.
Whether the save completed, the correct account is open and a dependent system needs separate review.
Refresh once, confirm the current value and report the expected versus observed result.
Account, contact, calendar and connected-workflow timezones, plus daylight-saving changes.
Correct the authoritative timezone and retest boundary cases with synthetic data.
Whether the correct account-wide or contact-level control was used and whether the message came from a separate workflow.
Capture the channel, contact, timestamp and safe example; assign human coverage before further pausing.
Sessions, team members, pending invitations, integrations and recent authorized changes.
Follow the incident sequence and contact ConvoRev without sending credentials or codes.
Account settings and security FAQs
Why can another administrator see a setting that I cannot?
Available controls depend on the active account, your role and the account configuration. Confirm that you are in the correct workspace and ask an authorized administrator to review your responsibilities. Do not use another person's sign-in.
Does changing my password disconnect every integration?
Not necessarily. External channels, calendars and integrations can use separate authorizations. Review the complete access footprint after a suspected access issue, password change or staff departure.
Should I use the account-wide pause for one difficult conversation?
No. Use the contact-level AI pause when one conversation requires human takeover. Reserve the account-wide control for a material issue that affects the shared configuration or multiple conversations.
What should I send support about a security concern?
Include the ConvoRev account, approximate event time, affected area, expected behaviour, observed behaviour and safe steps already completed. Do not include passwords, recovery codes, temporary security codes or integration secrets.
When should I review account security?
Review it after a lost device, unfamiliar session, password or recovery change, staff departure, administrator change, new integration, channel ownership change or unexplained configuration activity.
Can I delete the account before exporting data?
Deletion can affect conversations, contacts, integrations and reporting. Confirm required records, contractual or legal retention needs, authorized exports, external connections and owner approval before requesting an irreversible action.
Send safe evidence, not security secrets
Include the ConvoRev account, affected setting or user, approximate time, expected result, observed result and checks completed. Remove passwords, recovery codes, integration credentials and unnecessary private customer information.