Account Lists are added to a workspace from inside the workspace, not from the Account Layer. An Org Controller at the workspace home level browses available Account Lists and pulls the ones they want into their workspace. This article walks through the pull flow, what happens afterwards, and how workspace users interact with pulled lists.
Step-by-Step Instructions
Log in to Dashpivot Web as an Org Controller.
Open the workspace you want to add the list into.
From the workspace home level, open the workspace List Library.
Click + Add List → Pull from account library.
The Account List Library modal opens. It shows every Account List available in this Sitemate Start account, with:
List name
Item count
The list of items
An indicator showing whether the list is already pulled into this workspace
Select one or more lists you want to pull into the workspace.
Click Add Lists.
The selected Account Lists are added to your workspace and appear in the workspace list view with a Sitemate Start badge.
What the Sitemate Start badge means
A list with a Sitemate Start badge is a workspace copy of an Account List. It tracks the source at the Account Layer:
Edits made at the Account Layer flow down automatically — no action is needed in the workspace.
The list is read-only at the workspace home level. Workspace users cannot add, edit or remove items; they cannot add, remove or rename columns; the Add Item and Upload CSV buttons are all disabled.
The Deployed List Editing setting is not available for pulled Account Lists and cannot be enabled. Because account lists are always read-only at the workspace level, this setting does not apply.
The list can be deployed to project folders as normal. At project folder level, users have a restricted Add Item picker to choose which items from the parent list to surface in that project — but cannot create new items.
All editing of the list itself must happen at the Account Layer by an Account Admin.
How workspace users interact with a pulled Account List
The behaviour differs slightly between the workspace home level and the project folder level. Both are read-only with respect to the source list — there is no way for a workspace user to create, modify or delete items in the list.
At the workspace home level
The list detail page opens in read-only mode:
Control | Behaviour |
Add Item | Disabled. Tooltip: "Account level lists can only be edited in the Sitemate Start Account layer" |
Upload CSV | Disabled |
Download CSV | Available |
Item checkboxes (selecting rows) | Available — used for the Deploy and Archive actions |
Cell click / cell editing | Cells do not respond to clicks (matches existing project-level behaviour for org-level lists) |
Colour icons on cells | Disabled |
Add property column | Hidden |
Settings → List name field | Disabled. Tooltip: "List Name can be edited in the Sitemate Start Account layer" |
Settings → List Deployment Type | Available for editing |
Settings → List Item Sorting | Available for editing |
Selected items toolbar | Shows Deploy and Archive only — no Download or Apply colour |
At the project folder level
Once a pulled list has been deployed to a project folder, users at that level get a restricted picker:
Control | Behaviour |
Add Item | Enabled — opens an input field that dropdowns items from the parent Account List only matching what is typed |
Add Item dropdown | Only shows items that already exist in the parent Account List. There is no "create new" option. |
No items found state | If the typed text doesn't match any item in the parent list, an empty-state row appears (no creation option) |
Settings | Disabled |
Upload CSV | Disabled |
Download CSV | Available for use |
Cell click / cell editing | Cells do not respond to clicks |
Selected items toolbar | Shows Undeploy only or Download List |
This means at every workspace level, new items can only be created at the Account Layer. Workspace users can choose which of those items appears in a project view, but cannot add to the master list.
Configure notifications
If your pulled list has a date-expiry column and you want users to receive notifications, the workspace admin must subscribe recipients in the workspace.
The date-expiry notification bell is not available at the Account Layer (notifications are workspace-only by design).
After pulling, open the list in the workspace and configure recipients using the standard date-expiry notification picker on the workspace copy at the home layer.
The list starts with no subscribers until the workspace admin configures them — no one receives notifications by default.
Archiving and re-pulling
You can archive a pulled Account List in your workspace from the workspace home level if you no longer need it there. Archiving a workspace copy doesn't affect the Account Layer source or other workspaces.
If you later re-pull the same Account List into your workspace:
The archived workspace copy is reused rather than recreated.
Its state (active or archived) is set to mirror the current source state at the Account Layer:
If the source is active → the workspace copy becomes active.
If the source is archived → the workspace copy stays archived.
Archiving is a home-level action only. Archive / restore / delete are not available from project folder view, matching how existing org-level lists already behave.
Pulling multiple lists at once
You can pull several Account Lists in one go:
Open the Pull from account library modal as above.
Select all the Account Lists you want to pull.
Click Add Lists.
Each selected list is added to the workspace with its own Synced badge.
What workspace users can and cannot do
Action | Home level | Project folder level |
View the list | Yes | Yes |
Add a new item to the list | No — Add Item disabled | No — picker restricted to existing items in parent list |
Edit an item that came from the Account Layer | No | No |
Remove an item that came from the Account Layer | No | No |
Edit or remove a column | No | No |
Edit the list name | No | No |
Upload CSV | No | No |
Download CSV | Yes | Yes |
Apply cell colours | No | No |
Pick which items from the parent list surface in this view | N/A | Yes — via the Add Item picker |
Deploy the list to a project folder | Yes (Org Controller) | N/A |
Undeploy from a project folder | N/A | Yes |
Archive the list at workspace level | Yes | No — home level only |
Configure date-expiry notifications | Yes (workspace admin) | N/A |
Notes / Tips
Pulled Account Lists are read-only in workspaces. All editing must be done by an Account Admin at the Account Layer. This is by design — it's what keeps the master list consistent across workspaces.
The project folder "Add Item" picker is a way to control which items appear in a specific project's view, not a way to add new items. The pattern is similar to how existing org-level lists already work at project level.
Cross-account boundary is enforced. You can only pull Account Lists that belong to the same Sitemate Start account as your workspace. Lists from other accounts will not appear in the modal.
The "already pulled" indicator in the modal saves you from accidentally pulling the same list twice.
Account Lists can be used with Workspace Templates. There are no restrictions with using Account Lists with Workspace level Templates - but Account Templates can only use Account Lists.
Auto-deploy of an Account List if it’s linked to an Account Template. If an Account template has an account list linked to it, when the template is pulled into the workspace, the respective list will also be pulled into the workspace.
Troubleshooting
Problem | What to check |
I don't see "Pull from account layer" under Add List | Confirm you are an Org Controller in this workspace, that you are at the workspace home level (not inside a project or team folder), and that the workspace is part of a Sitemate Start account with Account Layer enabled. |
The Account List Library modal is empty | No Account Lists have been created yet — ask an Account Admin to create one at the Account Layer. |
An Account List I expected isn't in the modal | Confirm the Account List belongs to this Sitemate Start account. Lists from other accounts will not appear. Also check whether the list has been archived at the Account Layer. |
I pulled a list but it didn't appear in the workspace list view | Refresh the page. The list should appear with the Sitemate Start badge. |
Add Item is disabled in my pulled list | This is expected at the workspace home level. Account-level lists can only be edited at the Account Layer. At project folder level the picker is enabled but only allows selecting existing items from the parent list. |
I need to add a new item to a pulled list | The item must be added by an Account Admin at the Account Layer. Once added, it will appear in every workspace that has pulled the list. |
No one is receiving date-expiry notifications on a pulled list | Notifications are workspace-only and start with no subscribers. A workspace admin must subscribe recipients on the workspace copy. |
I archived a pulled list, then re-pulled it and the rows look different | The workspace copy mirrors the current source state on re-pull. If the source has changed since the workspace copy was archived, the re-pulled copy will reflect those changes. |