Choose between one workspace and separate workspaces
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Two business units can share customers without being entitled to see each other’s notes, conversations or commercial records. Putting them in one CRM workspace because it simplifies handoffs can quietly turn a collaboration choice into an access decision.
Choose one workspace when the units’ permitted access is compatible and the available controls can enforce any necessary differences. Choose separate workspaces when required separation cannot be demonstrated within a shared arrangement. Neither choice is sufficient on its own: separate workspaces still need scrutiny of administrators, exports, connected tools and cross-boundary handoffs.
The useful question is not simply “one CRM workspace versus separate workspaces?” It is: what may cross the boundary, who may move it, and can the proposed arrangement enforce that rule without making ordinary work unmanageable?
1. Define the boundary before comparing convenience
Begin with the information each unit creates and the actions people need to perform. “Both teams work with the same customer” is too broad to determine access. A customer’s contact details, an account owner’s task list and a private pricing discussion can have different audiences.
Write a boundary statement that names the permitted collaboration and the prohibited exposure. For example, in a hypothetical business:
Equipment Sales and Maintenance Services may exchange customer contact details and a handoff summary for an agreed referral. Each unit’s internal commercial notes and full conversation history remain restricted to that unit. A designated oversight role may access both for a documented operational purpose.
This statement makes the choice testable. A shared workspace is acceptable only if it can support those distinctions. Separate workspaces are acceptable only if the handoff process does not routinely copy restricted histories across them.
Distinguish viewing, editing, exporting, assigning and administering. Someone who may read a handoff summary does not necessarily need permission to export the source records or change another unit’s ownership rules.
The principle is consistent with OWASP’s authorization guidance: grant only necessary access, default to denial and check authorization on each request. That guidance is a design standard to assess against, not evidence that a particular workspace implements it.
2. Separate collaboration needs from access habits
List the recurring tasks that genuinely cross the boundary. Then identify the smallest information package each task requires.
- Referral: customer identity, relevant contact details, requested service and handoff owner—not automatically every prior message.
- Joint account planning: an agreed account summary and next actions—not unrestricted access to all opportunities.
- Management reporting: defined totals or selected records—not necessarily general browsing rights.
- Customer issue resolution: relevant context for the issue, with a named recipient and a clear end to temporary access where supported.
Watch for access habits disguised as requirements. “The director sometimes wants to look around” needs a defined oversight role. “The other unit might need it later” is not a reason to expose all records now.
Also establish which record is authoritative. If separate workspaces contain the same customer, each unit needs to know who maintains shared contact details and how corrections are communicated. Otherwise, separation can produce conflicting records that users resolve by copying more information than necessary.
3. Use a filled workspace-boundary decision table
Fictional worked example: the following decision table concerns Equipment Sales and Maintenance Services. All names, quantities and arrangements are hypothetical. It is a recommended decision method, not a description of available product controls.
Assume Sales has 14 users and Services has 9. They make about 12 cross-unit referrals each month. Most work stays within its originating unit. Both unit leads require internal commercial notes and full conversation histories to remain separated. The workspace’s actual permission behavior has not yet been verified.
Each row compares a shared arrangement with separate workspaces and records what would change the assessment.
Row A — Routine collaboration
- One workspace: potentially fewer handoff steps if permitted users can access the appropriate shared information without seeing restricted material.
- Separate workspaces: a named sender passes a minimal referral summary to a named recipient, who records acceptance in the destination unit.
- Example decision: separate workspaces are operationally plausible because referrals are occasional rather than the main working pattern.
- Condition that changes the decision: joint handling becomes routine and measured handoff delays materially disrupt work, provided shared-workspace access tests also pass.
Row B — Commercial notes and conversation history
- One workspace: acceptable only if ordinary users cannot access the other unit’s restricted records through any relevant access path.
- Separate workspaces: aligns more directly with the intended boundary, but administrators, shared connections and copied content still require verification.
- Example decision: favor separate workspaces until the necessary isolation is demonstrated.
- Condition that changes the decision: a shared arrangement passes the required read, edit, search and export checks for every relevant role.
Row C — Administration and oversight
- One workspace: may reduce duplicated configuration, but a broadly privileged administrator could affect both units.
- Separate workspaces: requires coordinated membership reviews and configuration decisions; shared administrators may still span the boundary.
- Example decision: each unit lead owns membership requests, while one designated operations owner coordinates reviews across both.
- Condition that changes the decision: the organization cannot sustain separate administration, and a shared arrangement can demonstrably preserve the required boundaries.
Row D — Reporting and common customer details
- One workspace: could simplify shared reporting if suitable permissions and reporting functions are available.
- Separate workspaces: needs a controlled process for combining approved totals and reconciling shared contact changes.
- Example decision: use a monthly approved summary rather than grant broad record access merely to produce a management report.
- Condition that changes the decision: reporting needs require frequent record-level collaboration that the summary process cannot support.
Row E — Cross-boundary exceptions
- One workspace: exceptions may be easier to arrange, but informal access expansion could become permanent.
- Separate workspaces: a minimal handoff or explicitly authorized access arrangement is needed; users must not substitute shared credentials.
- Example decision: the originating unit lead approves the information package, and the receiving owner confirms receipt.
- Condition that changes the decision: exception volume or repeated workaround attempts show that the stated boundary no longer matches actual work.
Row F — Overall decision
- Selected arrangement: plan for separate workspaces, subject to verifying their actual isolation and administrator scope.
- Reason: the information-separation requirement is firm, while collaboration can currently use a small, defined referral package.
- Unresolved evidence: access paths, export behavior, connected-tool scope and privileged access remain to be checked.
- Review trigger: reassess after the hypothetical first month of operation, or sooner following unexpected cross-unit visibility or repeated handoff failures.
This table is deliberately conditional. It does not treat an unknown capability as a passing control, and it does not assume that separate workspace names prove isolation.
4. Verify access paths, not just the default screen
A filtered list can make a workspace look separated while leaving the underlying records accessible elsewhere. A view is an organizational convenience unless its access behavior has been established.
Use clearly marked test records containing no real customer information. With appropriately authorized test accounts, check what each ordinary user, manager and administrator can actually do:
- Find another unit’s test record through search or a report.
- Open a known test-record link.
- Read related notes, messages, attachments or activity history where those surfaces exist.
- Edit, reassign or export information outside the intended scope.
- Receive information through notifications, connected tools or other enabled access paths.
Record the expected result, observed result, role used and date for each check. Treat untested paths as unresolved rather than silently assuming they are safe. Conduct checks only within authorized scope; this is not an invitation to probe unrelated systems.
OWASP’s object-level authorization guidance explains why knowing a record identifier must not by itself confer access. That is directly relevant when testing whether a hidden record remains accessible through its link.
For an Alactic workspace, verify the required behavior and its availability in the current workspace and plan. Do not infer that a control exists because it appears in this recommended assessment.
5. Count the administration work on both sides
A shared workspace can reduce duplicated setup, yet require more careful role design. Separate workspaces can make responsibilities clearer, yet multiply membership changes and reconciliation tasks. Compare those actual tasks rather than declaring either structure “simpler.”
For each arrangement, assign an owner to onboarding, role changes, departures, privileged access review, shared contact corrections and reporting. Record how each task will be completed and what evidence shows completion.
In the hypothetical example, the operations owner could track time spent processing referrals, correcting conflicting contact details and reviewing access during the first month. The purpose is not to prove the original decision right. It is to discover whether the arrangement is creating hidden work or encouraging shortcuts.
Keep firm boundaries separate from convenience scores. Lower administration effort cannot compensate for a failed requirement that users must not see another unit’s internal notes. First eliminate arrangements that cannot meet the boundary; then compare the operating effort of those that remain.
6. Design exceptions before people invent workarounds
An exception process should be short enough to use and specific enough to preserve the boundary. For each cross-unit request, capture:
- The customer or task involved and the business purpose.
- The minimum information or action needed.
- The sender, recipient and approving owner.
- Whether the solution is a handoff summary or an authorized access change.
- The closure condition and, where applicable, who removes access.
In the fictional Sales-to-Services referral, the package contains contact details, the requested service, a relevant equipment description and the referral owner. It excludes internal discount discussions and unrelated conversation history. The receiving unit confirms whether it accepts the task; sending the package alone does not establish ownership.
If the available system cannot provide narrowly scoped temporary access, do not describe that mechanism as available. Use an approved minimal handoff where suitable, or escalate the unresolved need to the boundary owner.
Repeated exceptions deserve investigation. They may reveal a boundary that is too restrictive, poorly defined responsibilities or a missing collaboration process. They are not automatic justification for granting everyone broad access.
7. Set failure responses before declaring success
The two arrangements fail differently. A shared workspace may expose information across units. Separate workspaces may create missed handoffs, conflicting customer details or uncontrolled copying.
If unexpected visibility appears: pause the affected sharing process, notify the responsible administrator, preserve the relevant observations and identify the affected access paths. Restrict access through authorized controls where possible. Re-test before treating the boundary as restored; changing a visible filter is not sufficient evidence.
If handoffs are missed: check whether the package had a named recipient, an acceptance step and a clear task owner. Repair those responsibilities before copying entire customer histories or collapsing the boundary.
If duplicated records conflict: identify the authoritative owner for each shared field and establish a correction route. Do not assume a broad synchronization process is necessary or available.
If exception requests keep growing: revisit the decision table with actual examples. Change the structure only after confirming that the alternative meets both the information boundary and the collaboration need.
8. Make the next decision measurable
For your next review, choose one pair of business units rather than trying to redesign the whole organization. Complete the decision-table rows with their actual restrictions, recurring handoffs, administrators and unresolved tests.
Leave the review with four concrete outputs: an approved boundary statement, a provisional workspace decision, an owner for every unresolved verification and a review date. A provisional decision is useful; an undocumented assumption is not.
Track unexpected cross-unit visibility, handoffs awaiting acceptance, corrections caused by conflicting records, exception requests and administration time. Set thresholds locally rather than borrowing arbitrary benchmarks. Required separation tests should pass before real restricted information is placed in a proposed shared arrangement.
The decision is ready when the team can explain not only why it chose one workspace or separate workspaces, but also what evidence would make it choose differently.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications