
Security Settings#
Navigate to Settings → Security (shown to Owners and Admins). It holds four cards:
- Two-factor authentication — Choose who must protect their sign-in with an authenticator app under Required for: Administrators (owners, admins and managers must enroll before they can use the app; this is the default), Everyone (every staff member must enroll; client portal users are not affected) or Optional (nobody is required, but anyone who has enrolled is still asked for a code at sign-in). The card shows how many administrators and members have enrolled. Click Save policy; people who now have to enroll see the setup screen the next time they open the app. New accounts have seven days to enroll.
- Support access — What AutomateNexus CRM support staff can open when they visit your workspace to help you. Let support open synced email is off until an Owner or Admin switches it on: while it is off, support staff and the platform's administrators see none of the email synced from your team's mailboxes. Every support visit is recorded in the audit log as a Support visit.
- Single sign-on — Sign-in through your company's SAML identity provider, such as Okta, Microsoft Entra ID or Google Workspace: verify your domain, connect the provider, decide who can join, test it and require it.
- Provisioning (SCIM) — Let your directory add, update and remove people, and map its groups to roles.
Single sign-on and provisioning are explained step by step in Single Sign-On (SAML) & SCIM Provisioning.
Sign-In Codes#
Every sign-in with a password is confirmed with a code: the Check your email screen says a six-digit code was emailed to your address. The code works once, for ten minutes, and Send a new code sends another. If you have set up an authenticator app, you enter its code instead. Signing in through your company's single sign-on, or with a link emailed to you, needs no code, and neither does Google, Microsoft or LinkedIn on an account that has no password.
Your Own Sign-In#
Each person manages their own sign-in under Settings → Authentication:
- Session — Your email, sign-in method and last sign-in time.
- Password (at least 8 characters) and Email address — Change your password or your email address.
- Two-factor authentication — Turn on a code from an authenticator app for your own account (scan the key, then enter the six-digit verification code), or turn it off with a current code.
- Sessions — This device's session is listed; Sign out other devices and Sign out all devices end your sessions elsewhere.
- Connected accounts — Connect or Unlink Google, Microsoft and LinkedIn as ways to sign in.
- Bring data from another CRM — Migrate your CRM opens the migration tool described below.
- Export your data — Downloads your profile, and the contacts, deals and activity history your role can export, as a JSON file.
- Delete account — Permanently deletes your login and profile after a 30-day review. Records in a workspace belong to that workspace and stay with it.
- Sign out — Ends your session on this device.
Approval Workflows#
Set up approval workflows from Settings → Approvals (shown to organization admins) so that certain records wait for an admin before they are finalized:
- Pending lists the requests waiting for review, with the count shown next to Approvals in the Settings menu; History shows approved and rejected requests.
- Approvals are switched on per record type. Where the Configure tab is available, it lists Which records wait for approval: Invoice, Payroll Period, Deal, Order, Journal Entry, Project and Employee, each with an On/Off switch, a Require a note when rejecting switch and an Auto-approve after field: the number of hours with no review after which a request is approved (checked every 15 minutes, and the requester is told). If the tab is not available to you, approval workflows are switched on per organization by the AutomateNexus CRM team; contact support to have invoices, deals, orders, projects or other records wait for an admin.
- Quote approvals — Under Settings → Invoicing, the Quotes card has Approval above (% discount) and Approval below (% margin) thresholds. A quote that discounts more than the limit, or whose margin falls under it, needs an admin's approval before it is sent. Setting a threshold to 0 turns that rule off.
Data Migration#
Migrate your CRM brings people, companies, deals, notes and activity over from HubSpot, GoHighLevel, Pipedrive, Salesforce or a spreadsheet. Open it with Migrate your CRM on the Bring data from another CRM card under Settings → Authentication, from the Import your data step of the setup wizard, or directly at /data/migration. Running a migration takes the import permission and a role that can see and edit every person, company and deal; otherwise the page asks you to ask an admin.
A migration goes through five steps: Source, Connect, Plan, Preview and Run.
- Source — Pick where the data comes from:
- HubSpot — Connect with a private app token or a Service Key. Brings contacts, companies, deals and pipelines, notes, tasks, calls, meetings and logged emails, owners and custom properties.
- GoHighLevel — Connect a sub-account with a Private Integration token and its Location ID. Brings contacts, businesses, opportunities and pipelines, notes, tasks, users and custom fields.
- Pipedrive — Connect with an admin's personal API token. Brings people, organizations, deals (archived ones too) and pipelines, activities, notes, users and custom fields.
- Salesforce — Upload the .zip from Salesforce's Data Export. Brings accounts, contacts, leads, opportunities and stages, tasks, events, notes and users.
- Spreadsheet — CSV or Excel files of people, companies or deals, one row per record with column names in the first row. A people file can name each person's company; a deals file can name a company and a contact email to link them.
- Connect — Paste the token, or upload the files. The screen lists where to find the token in the other system and which read access it needs.
- Plan — Decide What to bring; map each field under Fields (Goes to one of your fields or custom fields, or Don't bring); match the other system's users under Owners (matched by email, with a default owner for records with no owner); choose where each deal stage Lands in under Stages; and choose what happens to records you already have under Already here: Fill in their empty fields (recommended), Overwrite with what the source has or Leave them as they are. People are matched by email and companies by website, else name.
- Preview — Check sample records, then Test with a few of each, or Bring everything.
- Run — Follow the progress per record type: added, filled in, already here, skipped and failed. You can leave the page while it runs, Pause or Stop it, and Carry on later. Records that could not come over are listed with Download as CSV.
A migration can be undone: Undo the test or Undo this migration removes what came over, and after a test Undo the test and bring everything runs the full migration. Past migrations are listed on the page with their status, how many records were added and how many were filled in or matched.
Data Warehouse#
Connect your own data warehouse for advanced analytics and reporting under Administration → Data Warehouse. Admins and Managers can open the page, and Admins add connections. The page shows your connections, sync configs, recent syncs and success rate, with tabs for:
- Connections — Snowflake, Amazon Redshift, Google BigQuery, Azure Synapse, Databricks, DOMO, Apache Spark, ClickHouse, PostgreSQL or MySQL, each with a connection test.
- Sync configs and Scheduler — Which data is synced to the warehouse and how often.
- Logs, Monitoring, Analytics and Notifications — Sync history, health and alerts.
- API keys — Keys used by warehouse jobs to read from the CRM API.
- Webhooks — Notified when a sync finishes or fails.
Audit Logging#
AutomateNexus CRM keeps an audit log of changes in your organization. Open Settings → Audit log (shown to Owners and Admins) to see who changed what and when:
- Each event shows the action (Create, Update, Delete, Export, Import or Support visit), the table it touched (the filter offers API keys, Companies, Contacts, Customers, Deals, Invoices, Organizations, People (exports), Profiles and Projects), who made the change, a risk level, the details and the date.
- The details column shows the fields that changed; for an export or import, how many rows it carried; and for a support visit, whether support could only view or could make changes, until when, and the reason given.
- Filter by user, action, risk level (High, Medium, Low), table and date range.
- Export CSV downloads every event matching the filters, up to the newest 5,000; narrow the date range to export older events.