7. Administration

Admin workspace controls how the whole CRM behaves for your organization.

Users

• Create Staff, Company, Client, and Admin accounts.
• Set status (active / inactive).
• Filter and search users from User management.
• Deactivate leavers immediately to revoke access.

Roles & permissions

• Roles map to menus and API route permissions.
• Prefer cloning a standard Staff role and tightening permissions rather than overloading Admin.
• After changing permissions, ask users to refresh or re-login.

Menus

• Control which modules appear per role / branch context.
• Keep Client menus minimal (profile, documents, progress only).

Enquiry & conversion statuses

• Define statuses that match your pipeline (e.g. New → Contacted → Documents → Lodged → Granted).
• Avoid renaming statuses mid-month without communicating to Staff — reports will shift.

Lookups & reference data

Maintain:

• Lead sources
• Providers
• Countries, programs, visas, migration and business services
• Other tables your implementation uses for dropdowns

Clean lookups = clean filters and reports.

Branches & multi-tenant scope

• Create branches / brands / business units as needed for your plan limits.
• Separate menus where regions or franchises must not see each other’s data.

Global search

Use global search (where available) to find CRM records quickly across modules — especially useful for Admins and busy Staff.

Security reminders

• Least privilege by default
• No shared Admin passwords
• Review user list monthly
• Align API permissions with every new custom role (Enterprise)

→ Next: Pricing & plans