Initial workspace setup
Configure the workspace name and timezone before your team begins regular CRM work.
Organization Admins can edit two workspace fields: Name and Timezone. The internal workspace slug is not an editable customer setting.
Choose the workspace name
Use the business or team name colleagues will recognize. This name appears in the CRM shell and helps users confirm they are entering data in the correct workspace.
Set the timezone
Choose the relevant IANA timezone, for example Asia/Kolkata. WebPro CRM stores system timestamps consistently and presents time-based information using the workspace timezone. Changing the timezone does not rewrite historical database timestamps.
Recommended setup order
- Confirm the workspace name and timezone.
- Enable currencies and choose a default.
- Review Lead Sources and Lost Reasons.
- Configure the Sales Pipeline.
- Invite the team and assign appropriate roles.
Only Organization Admins can manage these workspace-level settings.
Before the team starts entering data
Review each setting with the people who will use the CRM. The timezone affects how due times and timestamps are presented. Currency configuration controls valid Deal currencies. Lead Sources affect acquisition context, while Lost Reasons support consistent outcome review. Pipeline stages should describe genuine steps in your sales process rather than every internal task.
Changing the workspace name is presentational and does not move records. Changing the timezone changes how time-based information is displayed; it does not rewrite the underlying historical timestamps. Make timezone changes deliberately so colleagues understand why previously familiar times may appear differently.
Example setup
A service business operating primarily in India might use Asia/Kolkata, enable INR as its default currency, retain USD as an additional currency, and configure sources such as Website, Referral, LinkedIn, Outbound, and Existing Client. Its Deal stages might include Growth Diagnostic, Discovery Call, Proposal, and Negotiation before Won and Lost outcomes. These labels are an example—the workspace owns its configuration.
Common mistakes
- Inviting the full team before checking roles and reference values.
- Creating several Lead Sources that mean the same thing.
- Treating currency changes as foreign-exchange conversion.
- Renaming stages without considering current Deals and historical context.
- Giving broad administrative access merely to solve an ownership issue.
After setup, create one synthetic Lead and Deal to confirm that selections and stages appear as expected before regular customer information is entered.