Workspace Configurations are a layout engine in Squivr that deliver a focused experience built from reusable components. A Workspace can be bound to a specific Salesforce object (rendered as a record page) or set up as a global app-level Workspace.
Workspaces are ideal for use cases like:
- Account planning and customer success reviews
- Opportunity management and deal desk workflows
- Contact and stakeholder mapping
- Service or case triage
- Territory and pipeline reviews
- Global dashboards, home pages, and cross-record command centers
- Any workflow where the standard Salesforce UI is too cluttered or too generic
Whether the Workspace is object-scoped or global, users see a focused left-hand navigation and a working area that shows only what they need for the task at hand.
What is a Workspace Configuration?
A Workspace Configuration is a layout made up of a left navigation rail, a main working area, and an optional action bar, all built declaratively by a Salesforce administrator. Workspaces render in two modes:
- Object Workspaces are bound to a standard or custom object and render automatically when a user opens a matching record.
- Global (App-Level) Workspaces are not tied to a specific record. They appear as standalone tabs or home pages, and are useful for pipeline reviews, territory planning, and any workflow.
Each Workspace is configurable across three levels:
- The parent configuration (binding mode, visibility, global settings)
- Navigation items (the entries in the left rail)
- Components (what renders inside each navigation item)
Key Concepts
Workspace Configurations (Parent Records)
Workspace Configurations are the top-level records that define:
- Binding mode (object-scoped or global)
- If object-scoped, which object the Workspace is bound to
- Whether it is a system configuration or an admin-authored one
- The navigation bar color and state
Navigation Items
Navigation Items are the entries in the left rail. Each one represents a focused area of the Workspace, like Summary, Notes, Contacts, Pipeline, or Org Chart. Every Navigation Item includes:
- Label and icon
- Sort order
- Layout mode (Single Column, Two Column, Three Column)
- Optional visibility rule (hides the item when a condition is false)
Components
Components are the elements rendered inside a Navigation Item. A Component can be:
- A Squivr Lightning Web Component (Highlights, Related List, Notes, Action Bar, Quadrants, Whitespace, and more)
- An Aura component (Org Chart, Gantt Chart, Arc Groups, Action Plan)
- A Flow
- A Visualforce page
Each Component has layout options that determine which column it belongs to, how wide it is, and whether it is collapsible.
Action Bar
The Action Bar is a row of buttons that sits at the top of a Navigation Item. Buttons can:
- Launch a Flow
- Run a Squivr Rule
- Open a standard Quick Action
- Edit, delete, or clone the current record (object Workspaces only)
Action Bar buttons support visibility rules, confirmation modals, and per-button permission checks. On a global Workspace, record-specific action types (Edit, Delete) are hidden because there is no current record to act on.
System vs. Admin Configurations
Workspace Configurations have an Is_System__c flag that distinguishes:
- System configurations, shipped by the Squivr managed package and overwritten on upgrade
- Admin configurations, created or cloned by your team and preserved across upgrades
The recommended pattern is to clone a system configuration, mark the clone as admin-authored, and customize the clone. This keeps your changes safe from package upgrades while preserving the original as a reset-to-defaults fallback.
Snapshots and Versioning
Workspace Configurations do not maintain formal versions. Each save mutates the same record. For versioning, use the Clone pattern: clone before every significant change, keep the old clone Active and the new clone Draft until validated, then swap the Active flag.
The Squivr audit log captures every save with the running user, timestamp, and a diff of the changed fields.
Where Workspaces Appear
Workspaces can be rendered in two contexts:
Object Workspaces appear as a Lightning record page on:
- Account record pages
- Opportunity record pages
- Contact and Lead record pages
- Case record pages
- Any custom object record page (by adding the Workspace component to the page in Lightning App Builder)
Global Workspaces appear as standalone tabs in the Squivr app navigator, without a record context. Common uses include:
- Pipeline or forecast command centers
- Territory and whitespace planning dashboards
- Team home pages with quick links, queues, and KPIs
- Cross-object review surfaces (for example, a combined Accounts + Opportunities + Contacts workspace for account planning)
If you do not see a Workspace where you expect one, contact your Salesforce Admin.