Getting Started

Workstation is organized around customer records, team activity, operations, marketing, performance, knowledge, and configurable workflows. You do not need to configure every module before using the app, but a few core concepts make the rest of the documentation easier to follow.

Organizations

Each organization has its own isolated data. Contacts, accounts, deals, activities, tickets, projects, invoices, content, settings, and users belong to one organization and are not shared with other organizations.

This matters because permissions, departments, data visibility, properties, pipelines, default record layouts, and automations are configured per organization.

The sales flow

The most common workflow starts with a contact and ends with a deal outcome:

Contact -> Deal -> Won or Lost
              |
          Price Offer -> Invoice

A Contact represents a person you may sell to, support, or work with. Contacts carry lifecycle fields such as status, score, source, pipeline, and stage, so early prospects do not need a separate prospect module. When the opportunity is real, open a Deal. Create or associate a Price Offer when a formal quote is needed.

Properties and record layouts

Properties defines the native, custom, and computed data available to a record. Objects controls where that data and the module’s cards appear on supported record pages. Pipelines controls stages and movement rules. These settings are independent but designed to work together.

Records and relationships

Workstation connects records so teams can see the full customer history:

• Accounts contain contacts.
• Deals link to accounts and contacts.
• Activities can be linked to contacts, accounts, deals, and other supported records.
• Tickets can be linked to accounts and contacts.
• Projects can be linked to deals.
• Campaigns and segments help track where contacts came from and how audiences are grouped.
• Invoices can connect commercial work back to customer records.

Use these relationships to avoid duplicating information. For example, log a call as an Activity on the deal or contact instead of writing the same note in several places.

Views and saved table layouts

Many modules support list views with filters, sorting, columns, and saved configurations. Use Table Views when teams need repeatable views such as “My Open Deals” or “High Priority Tickets”.

Permissions and visibility

Access is controlled by team roles, permissions, departments, and visibility settings.

• Use Team to manage users and roles.
• Use Departments to model organization structure and record visibility.
• Use Settings for security, integrations, imports, exports, and global configuration.

Recommended setup order

For a new workspace, configure the basics in this order:

1. Invite users and confirm roles in Team.
2. Configure Departments if visibility depends on team structure.
3. Review native fields and create custom fields in Properties.
4. Configure Pipelines for contact lifecycle and deal stages.
5. Add required, conditional, and stage-based rules using Data Validation.
6. Arrange supported record pages in Objects.
7. Configure imports, integrations, and security in Settings.
8. Create saved Table Views for common workflows.
9. Configure optional modules such as Forms, Inbox, Content Hub, and KPI Definitions when the team is ready to use them.

Next steps

If you are learning the CRM flow, start with CRM Setup and Contacts. If you are configuring the workspace for a team, start with Settings, Team, and Departments. If you are expanding beyond CRM, review Inbox, Forms, Invoices, and Content Hub.