Workbooks, calculations and clear decisions
Open a file or a selected SABSUS data snapshot, organize it, add formulas and explain the result to your team. Tables, reports, charts and workbook versions share one workspace.
Working data requires an account, permissions and relevant connections.
XLSX, ODS, CSV and other supported formats
Local and company workbooks are distinct modes
Importing a snapshot does not change the source service
01 / A clear workflow
Suppose a manager needs to compare planned and actual expenses. The goal is not to move the entire business into a spreadsheet, but to obtain a specific slice and build a calculation that can be checked.
Open a copy of a file, or select an available SABSUS source, apply filters and review the preview.
Give columns a clear structure. Use formulas, value validation, sorting and filters.
Group rows into a report, add a chart and a comment explaining what changed and what needs attention.
Use a company workbook within access permissions, or export the result in an appropriate format.
02 / Working tools
Use aggregation, conditions, lookup, text, dates and dynamic arrays. SUM, SUMIFS, IF, XLOOKUP, FILTER and other implemented functions help build calculations in understandable steps. Cross-sheet references, named ranges and drag fill are supported.
Structured tables combine column names, calculated columns and totals. Validation helps catch unsuitable values, while conditional formatting highlights important differences. These editing aids do not replace access controls.
Save filtered and sorted views. Build a report on another sheet with row and column groups, multiple measures and totals. Refreshing that report uses the workbook's source sheet; it does not automatically fetch an external system.
Use column, line, area, pie, scatter and combination charts. Adjust labels, legends and colors, then prepare a print area. Charts use calculated values rather than a pre-drawn illustration.
Sign in to the right company and work with colleagues in an accessible workbook. Participants, selected cells and saved versions provide context. Independent edits can merge; conflicting changes need attention. Collaboration is not a promise that conflicts never occur.
Open supported XLSX, ODS and text-based tables as copies. Export a workbook or an individual sheet; native JSON is available for a model backup. Office-format interoperability is partial, so complex workbooks should be checked after transfer.
In a company workbook, open the available-source catalog, select an operation and filters, preview the rows and explicitly create a workbook from the result. Available sources depend on current permissions. This is a snapshot for analysis, not a live spreadsheet that silently writes to CRM, inventory or accounting.
DEMO
A small XLSX sample for exploring calculations. It uses fictional data, not real company orders or results from your account.
03 / Illustrative scenarios
Import an agreed expense file, calculate category differences and build a chart. The result is an explainable calculation, not automatic authorization to pay.
Take an available SABSUS snapshot, filter irrelevant rows and group the measures you need. Add a comment documenting the selection criteria so a colleague understands the scope.
Copy a selected local workbook into the company, add comments and share its link with an authorized colleague. The original local workbook remains separate.
These are workflow examples, not customer case studies or promised outcomes.
Requirements and boundaries
Sheets does not promise full Excel or Google Sheets compatibility. VBA macros, Power Query and DAX are not claimed capabilities. A company-workbook link does not grant access to an outsider, and local cell protection does not replace server permissions. The examples on this page are illustrative, not customer results.
FAQ
It is a workspace for tables, formulas, reports and charts. You can use local or company workbooks, open supported files and import selected available SABSUS data.
XLSX import supports an implemented subset of formulas, formatting and objects. This is not full compatibility: complex files need checking and VBA macros do not run. The original file is not overwritten.
Importing from an available SABSUS source creates a snapshot after preview. This flow does not provide automatic two-way synchronization or write changes back to the source service.
A company-workbook link is for colleagues with the appropriate SABSUS access. The link itself does not open the book to an outside user. A local workbook stays separate and is not shared by sending the website address.
Do not assume every screen is automatically available through MCP. Workbook editing and selected SABSUS data access use their own interface and API. Check available AI operations in the connected client and its current tool set.
Explore the right workflow, required connections and access boundaries for your scenario.