Source catalog
Available collections and their capabilities come from the company's configured catalog. Working and archive sources may differ, and some data is read-only. A model relation does not automatically expose every account table.
Company working data · deliberate changes
Maintain your data.
See the difference first.
Find records in available sources, edit supported fields and review a before-and-after plan before applying it. SABSUS Manager is a company data-maintenance workspace, not an autonomous manager or unrestricted database access.
Working data requires an account, permissions and relevant connections.
- 01FindSource and intended selection
- 02PrepareSupported field and value
- 03CompareBefore → after
- 04ApplyInspect per-record outcomes
Available sources
Sources and capabilities are company-specific
Before → after
Review differences before committing
Per-record outcomes
Check successes, errors and conflicts
01 / A clear workflow
A clear sequence instead of blind edits
Suppose several records contain wording that needs correction. First find the intended set, then prepare the replacement and inspect exactly which records and fields will change.
- 01
Choose the source
Open an available collection. Use pagination and a server-side field filter; table text search searches already loaded records.
- 02
Prepare the edit
Edit a supported field or select records for a bulk change. Unavailable and system fields do not become editable.
- 03
Review the plan
Compare old and new values by record. Check the selection, translation language and fields affected by the operation.
- 04
Apply and inspect
Explicitly apply the prepared plan and inspect its results. A conflict or error does not mean every selected record was changed.
02 / Working tools
An editor for careful work with available data
Structured forms instead of raw JSON
Supported text, translations, numbers, dates, flags, nested objects, lists and references are edited in forms. Related records display readable names when available. An unavailable reference is not replaced with an invented value.
Selected-field changes
Set a supported value or replace a text fragment in selected records. Translation changes are language-aware. The preview shows the result; this is not a background rule for all future records.
Capability-based creation and copying
If the source permits creation, obtain a new-record template, fill its fields and prepare a plan. Copying and other actions also depend on source capabilities. Having Manager does not create otherwise unavailable permissions.
Images in a draft
Upload a supported JPG, PNG or WebP and attach it to an editable field. Its URL enters the draft first; the record change goes through preview and save. This is not bulk import of arbitrary files from an external database.
History and working exports
Inspect Manager operation outcomes, including individual successes and failures. CSV includes selected rows, or already loaded rows if none are selected. It supports reconciliation but is not a complete database backup.
The time-limited preview shows changes before application. Original record versions help reveal conflicts if the data has changed. After applying, inspect per-item outcomes instead of assuming the entire batch succeeded.
- Only selected records and supported fields
- No promise of atomic batches or automatic rollback
- Deletion is not the ordinary way to correct a field
03 / Illustrative scenarios
Three data-maintenance tasks
Correct a record
Find an accessible record, correct its description or translation and compare the difference. Apply it after checking the intended field and language.
Replace recurring text
Select the intended records, field and replacement. Review each record's changes rather than including unrelated records by default.
Reconcile outcomes
Filter records by a field, export the selected rows and inspect operations performed through Manager. Keep loading and export limits in mind.
These are workflow examples, not customer case studies or promised outcomes.
Requirements and boundaries
Data access is not access to everything
Manager works with permitted company sources and capabilities. It does not connect arbitrary external databases, provide SQL or secret access, or make employment decisions. Its history covers its own operations, not all SABSUS activity. Deletion requires a separate deliberate action; restoration within Manager is not promised.
FAQ
The important
questions.
Is Manager a people-management workspace?
Here the name identifies a working-data editor. It handles available collections, records and reviewable changes, not autonomous hiring, payroll or scheduling.
Can I edit every company record?
No. Sources and actions depend on the catalog and granted permissions. Some fields and sources are read-only; system and sensitive settings do not become generally accessible.
Is a bulk edit applied immediately?
A plan with differences is prepared first, then applied through a separate action. Afterwards, check per-record results and possible conflicts.
Is CSV a complete backup?
No. It exports selected or already loaded rows. A full backup and recovery strategy requires a separate solution.
Can every edit or deletion be undone?
Universal rollback is not claimed. The interface specifically warns that Manager cannot undo deletion. Check the plan, selection and necessity before applying an operation.
Start with your task.
Not another interface.
Explore the right workflow, required connections and access boundaries for your scenario.