Spaces and Lists
Give the work that does not fit a standard module its own structure.
Bring lists and documents together in a Space, use the fields your team needs and inspect records through useful views and filters.
A spreadsheet often starts a process without defining it.
Some work belongs to a team, a customer or a recurring internal process but has no natural home in a standard module. Spaces and Lists provide that organization. The team still defines what each field means, who maintains the records and how a record progresses. A configurable list is not automatically a validated specialist application.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Custom Spaces
Bring relevant lists, documents and work entry points into a Space with a purpose your colleagues can understand.
Custom list fields
Create lists with supported text, date, amount and other fields so a custom register reflects the information your team actually maintains.
List and board views
Use lists, boards and filters to organize the overview around the work you need to inspect, without creating a separate copy of every record.
AI-assisted workspace planning
Discuss the lists and views your team needs with Tsumira AI, then review proposed structure and actions within your permitted access.
Use a Space as a meaningful place to work.
Group the entry points for a team, client or business area. Lists and documents can sit near one another so a brief and the work it describes are easier to find. Give the Space a clear purpose before adding material; collecting unrelated links under one name will not explain the process to a new colleague.
- Spaces for teams, clients and business areas
Capture the information the process needs.
Create lists with text, dates, amounts and other supported fields. Distinguish the record's identity from progress, responsibility and supporting detail. Existing business records and custom registers can be used in the working environment, but a custom amount field does not establish accounting behavior, tax rules or a replacement for a finance record.
- Custom fields with a clear team meaning
Choose a view for the question being asked.
Use lists, boards and filters to inspect the same working records from a useful perspective. A filtered view changes the overview, not the underlying responsibility to keep data correct. AI can help propose a structure or organize work, but the team reviews the suggestion and per-user authority remains in place before changes are executed.
- Focused views and reviewed AI assistance
A concrete workflow
Define the process
Explain what one record represents and which decision it supports.
Choose fields
Add the supported fields needed to maintain that record.
Create views
Test a list or board against real questions from the team.
Review use
Check a small sample before expanding the register or adding more users.
An illustrative working example
Illustrative scenario: a customer launch checklist
An agency creates a Space for a client's launch. A custom list records the material still needed, with dates and ownership, while the brief remains in Docs. The team uses a board to discuss progress and a filtered list to inspect open items. Before expanding the setup, another colleague tests whether each field is understandable and whether a completed record actually means the agreed work is done.
Questions about this topic
Is a custom list a specialist ERP module?
No. It organizes records and views. Specialist accounting, compliance and industry behavior must be verified independently rather than inferred from field names.
Can documents live alongside lists?
Spaces can bring work entry points together, including lists and documents. Access to the actual material still follows the relevant authority.
Do filters create different copies?
A view is a perspective on working records. Check the selected filter before assuming that an absent item was deleted or completed.
Can AI build without our review?
AI can assist with proposals. Review the suggested structure and actions before execution, within the user's permitted access.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Sheets
Application concept: Select a Google Sheet tracker and define its rows, field meanings and review responsibility before structuring a List.
Microsoft Excel
Application concept: Compare an Excel operational register with the supported List fields instead of promising formula or macro compatibility.
Notion
Application concept: Plan how a Notion working database should be organized into clear Tsumira Spaces and views.