Admin User Guide

    Use this guide if you help configure GEVADE CRM. Admin users usually manage settings, users, permissions, contacts, pipelines, workflows, calendars, forms, communication channels, AI-assisted tools, and troubleshooting preparation.

    Who this guide is for

    • Admin users
    • Operations managers
    • Setup specialists
    • Team members responsible for CRM configuration
    • Businesses preparing to maintain GEVADE CRM internally

    Key Responsibilities

    1. Review account settings

    Admins should confirm time zone, business information, notifications, account settings, and workspace details.

    2. Manage users and permissions

    Admins may invite users, review access, remove inactive users, and adjust permissions depending on account configuration.

    3. Maintain contacts and companies

    Admins should help keep contact data clean, review imports, check duplicates, and organise tags and fields.

    4. Manage pipelines and lead structure

    Admins should review pipeline stages, lead ownership, opportunity movement, and source tracking.

    5. Configure workflows carefully

    Admins should test triggers, actions, wait steps, stop conditions, and connected tools before enabling workflows.

    6. Configure calendars and bookings

    Admins should review staff availability, time zones, buffers, appointment confirmations, and booking links.

    7. Review forms, pages, and funnel setup

    Admins should test form submissions, redirects, notifications, contact creation, source tracking, and mobile layout.

    8. Support troubleshooting

    Admins should collect examples, affected records, screenshots, timestamps, and expected vs actual behaviour before submitting support requests.

    When to Request Support

    Submit a support request if:

    • Settings are unavailable.
    • User access does not behave as expected.
    • Imports are not working correctly.
    • A workflow is not triggering.
    • Forms are not creating contacts correctly.
    • Calendar availability is not behaving as expected.
    • You need account-specific configuration review.