Workspaces and teams
Keep different businesses, projects, or areas of work separate.
Organize separate work in separate workspaces
A workspace contains its own clients, deals, activities, settings, and calendar.
You can use different workspaces for different businesses, brands, projects, or areas of responsibility.
Keep unrelated information apart
For example, you might create separate workspaces for:
- Consulting clients
- Property management
- A second business
- A temporary project
- A specific market or location
Switching workspaces changes the CRM data you are viewing. This keeps each area focused and avoids one very large, mixed client list.
Create a shared team workspace
A team workspace gives several people access to the same CRM data.
Members can work with shared:
- Clients
- Deals
- Activities
- Attachments
- Pipeline settings
- Workspace preferences
When someone updates a record, the team works from the updated information.
Manage member access
Team roles keep access simple:
- Owner: Full control, including team deletion
- Admin: Can manage members and shared data
- Member: Can view and edit CRM data
Owners and admins can create or regenerate a join code for new members.
Move useful information between workspaces
You can copy selected data from one workspace into another.
Choose whether to copy:
- Clients
- Deals
- Activities
- Lead sources
- Statuses
- Priorities
- Tags
- Custom fields
- Currency settings
Existing records are not overwritten. Related records are copied only when the records they depend on are also included.
Why use workspaces instead of tags?
Tags are useful for grouping records inside one business. They are less useful when two sets of data should have separate settings, pipelines, calendars, and access.
Use tags when the work belongs together. Use separate workspaces when it does not.
Why use this instead of sharing spreadsheets?
Shared spreadsheets can work for small lists, but they become difficult when several people update clients, deals, notes, and activities.
A team workspace provides:
- Connected records
- A consistent structure
- Clear member roles
- One current pipeline
- Shared activities and files
- Less copying between documents
Why use this instead of a large enterprise CRM?
Enterprise systems may provide detailed permissions, territories, departments, and approval chains. They also require more setup and management.
Good Old CRM keeps team access understandable. It is a better fit for smaller teams that need to work together without maintaining a complex account structure.
Get started
Keep each area of work focused and share only what needs to be shared.
