Vertex CRM is a web application deployed for your organisation. This page covers access, structure, and where to go for help—the questions that come up in the first week.
Signing in
Users sign in at your deployment’s login page with credentials an administrator provides. There is no public self-service signup: the product is deployed per organisation, so account creation runs through your admin. Administrators can be required to complete multi-factor authentication.
How the workspace is organised
Working across organizations
If you belong to more than one organization, a switcher in the header changes context. Permissions are evaluated per organization, so your role in one does not carry into another—you might administer one unit and have read-only access in the next. One login, several contexts.
Your first week, in order
Common first-week questions
| Question | Short answer |
|---|---|
| Where do I change my password or MFA? | Your profile and security settings after sign-in. |
| Why can I not see a colleague’s account? | Role scope, or a different organization context. Ask your administrator. |
| Lead or account—which do I create? | Lead for unqualified interest; convert it once your criteria are met. |
| Can I import a spreadsheet? | Yes, via CSV import. Agree dedupe rules with your admin first. |
| Where is WhatsApp? | Inbox (WhatsApp lane). Admins connect AiSensy or Meta Cloud API under Integrations → WhatsApp. |
| Is there an API? | Authenticated API routes exist for integrated deployments; see your documentation. |
Where to get help
Product questions belong in Documentation and Support. Access and permission questions belong with your organisation’s administrator. Hosting, uptime, and backup questions belong with whoever operates your deployment. For commercial questions, contact us.
Planning a rollout rather than joining one? Start with the implementation checklist and best practices.
Frequently asked questions
- Where do I sign in?
- Use the login page for your deployment.
- How do organizations work?
- Permissions are per-organization; use the header switcher when you belong to multiple orgs.
- Is there a public API?
- Authenticated API routes exist for integrated deployments—see documentation.