Account Lists are created and edited at the Sitemate Start Account Layer using the same list editor you already use in workspaces. This article walks through both flows and the small differences when working at the account level.
Create an Account List
Open the Account Layer from the Workspace Switcher.
Click Account Lists
Click + Add List.
The “Add new List” modal opens.
Add columns (list properties), add rows (list items), and configure styles, colours and column types as you would in a workspace list.
The list saves automatically as you make changes — no separate "Save" action is required.
The list is now stored at the Account Layer and is immediately available to be pulled into any workspace — see How to pull an Account List into your workspace.
Edit an Account List
Open the Account Layer Account Lists.
Click the Account List you want to edit. The Account List detail page opens.
Make your changes — add or remove rows, edit values, add or rename columns, apply styles or colours, attach files to cells, reorder rows, run bulk operations.
Changes are saved automatically. Updates propagate to every workspace that has pulled the list.
Editor capabilities
The editor at the Account Layer supports the full feature set you already know from workspace lists:
Add list items (rows) — single or in bulk.
Add, edit, delete list properties (columns).
Edit cell values, styles and colours.
Reorder rows.
Bulk operations — bulk delete, bulk style.
Cell file attachments.
Differences when working at the account level
A few small things behave differently in the account-level list editor compared with a workspace list:
Element | Behaviour at the Account Layer |
Date-expiry notification bell | Hidden — notifications are configured per workspace after the list has been pulled. See Notifications on pulled Account Lists below. |
Edit permission | Account Admin |
List Settings | Settings at the Account Layer only include the List Name. For list sorting and deployment options - this can be configured in the workspace copy of the Account list. |
Notifications on pulled Account Lists
If your Account List has a date-expiry column, you'll notice the notification bell is hidden in the account-level editor.
This is by design.
The account-level list does not have a notification picker.
Each workspace that pulls the list does have its own notification picker on the workspace copy.
Workspace admins configure who is notified for date-expiry events in their own workspace.
The list starts with no subscribers in each workspace until someone is configured.
This gives each workspace control over its own notifications rather than inheriting a central list of subscribers from the account level.
How updates propagate
When you change an Account List at the Account Layer, the update flows down to every workspace that has pulled the list:
New rows added at the Account Layer appear in every workspace.
Edits to existing rows are reflected in every workspace.
Rows you delete at the Account Layer are removed from every workspace.
Column changes flow to every workspace.
Workspace users cannot add, edit, or remove items in a pulled list at any level. All structural and content changes happen here at the Account Layer.
At project folder level, workspace users have a restricted picker that lets them choose which items from your list appear in a specific project — but they cannot create new items.
For more on how workspace users interact with pulled lists, see How to pull an Account List into your workspace.
Notes / Tips
Archive a retired Account List rather than deleting it. Deletion removes it from every workspace that has pulled it; archiving keeps it available to be pulled again later.
Notifications live in the workspace. If you want users to receive date-expiry notifications, the workspace admin must subscribe to them after the list has been pulled.
Troubleshooting
Problem | What to check |
I expected a notification bell on the date-expiry column but it's not there | This is intentional. Notifications are configured per workspace, not at the account level. Ask a workspace admin to configure recipients in each workspace after the list has been pulled. |
I'm an Org Controller but the editor is read-only | Edit permission at the account level is restricted to Account Admins |
Auto-save didn't apply my change | Check the network connection and reload the page. The editor uses the standard Dashpivot auto-save behaviour. |
A workspace admin is asking how they can add their own item to the list | They can't — Account Lists are read-only in workspaces by design. Either add the item here at the Account Layer (and it will flow to all workspaces that have pulled it), or recommend they use a separate workspace-level list for items they want to manage themselves. |