Use the shared client workspace across CRM and Sales
Open one permission-aware view of a client’s existing tasks, sales work, documents, finance, projects and email without copying the source records.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Hub → CRM → Client workspace; native customer → Client workspace tab
PermissionHub visibility and native record access; each connected section retains its own source permissions
Before you begin
Verify the selected identity before reviewing client-wide information. A contact can lead to its verified company, while a lead remains a separate lead identity.
Follow these steps
- Open Client workspace from the CRM rail, a record action or the native customer’s Client workspace tab.
- Confirm the client, contact or lead in the header and open Native record when you need to inspect the source identity.
- Choose the relevant section and use its search, paging or available filters to find the source item.
- Open the original item to carry out actions owned by the native module. Return to the workspace for the combined context.
- Use Create task, Reminder or Letter only when the corresponding capability and dependent module are available.
Fields and options
- Sections
- Tasks, Reminders, Deals, Sales activities, Hub activities, Contracts, Letters, Compliance, Obligations, Workflows, Cadences, Invoices, Estimates, Proposals, Projects, Notes and Email.
- Identity
- A verified contact’s company relationship can provide client-wide context. Lead records are not automatically matched to a similarly named company.
- Source records
- The workspace reads authorised original records. A hidden or unavailable section is not an invitation to bypass its module permissions.
Rules and limits
- The workspace does not activate a missing module or create a second finance, contract or compliance system.
- Email additionally checks authorised record addresses and mailbox access; company context does not grant unrestricted contact mail.
- Compliance visibility does not certify the client’s legal compliance or enable an inactive monitor.
Check the result
- Compare a visible item with its original source record and permissions.
- Check a restricted staff role still cannot open a source record it could not access before.
If something does not look right
- For an unavailable section, check the dependency and native capability before treating it as missing data.
- If the identity looks wrong, return to the source record and correct the verified relationship there.
Common questions
Does this copy invoices or contracts into the Hub?
No. It presents authorised records from their original modules.
Why is a lead not showing company invoices?
A lead remains its own identity; company access is not inferred from a matching name or email domain.