ORGANISASIONOS / PRODUCT QUESTIONS
Your organization, in practice.
Practical answers about divisions, teams and everyday workflows.
Several divisions and lines of business: how can they be distinguished?
Yes. OrganisasionOS supports named divisions under a legal entity and the assignment of teams to those divisions. You can represent activities such as “Manufacturing” and “Services”. An industry or line of business describes the work; a division structures the organization; a legal entity represents the company. These are distinct concepts.
Example. A fictional company can have Manufacturing and Maintenance divisions, with separate teams and a shared payroll function if that function is granted access to the relevant employees.
A division name or industry label grants no permissions. Modules, actions and data visibility are configured separately, subject to each module’s capabilities. Automatic industry classification and universal division-based isolation are not claimed. A separately isolated customer organization is not just a division; production multi-organization hosting remains to be accepted.
Are any teams or functions, such as payroll, purchasing or management, shared across your divisions?
Explore the workflow ↗Separate access while sharing selected functions
Modules and profiles can be assigned to people, teams or groups where those functions are administrable. Seeing a module, performing an action and viewing its data are separate permissions. Modules have their own scopes, such as personal records, authorized teams, legal entities or authorized documents.
Example. A sales team sees its CRM records; a shared function can view several teams if granted the corresponding permissions. ERP retains source-module permissions when presenting cross-module information.
Division membership alone is not enough. Data separation must be checked module by module; a global profile or visible screen does not guarantee access to everything. Cross-customer federation has not been accepted as an operational business capability.
Which information should remain within each team, and which should be shared?
Explore the workflow ↗Several sites within one organization
OrganisasionOS includes hierarchical locations. Inventory workflows can locate assets or stock within their storage locations, depending on the module.
Example. VilleFictive distinguishes a workshop and a warehouse, then their storage locations, so people can find equipment where it belongs.
A physical site is not a legal entity, an industry or a separately isolated customer organization. Location classification does not by itself grant or remove every permission.
Do you mainly need to locate equipment, or also separate teams and access?
Explore the workflow ↗Different working conditions for different employees
Configured working conditions and automatic public-holiday handling are used in everyday work. Schedules and time banks use the organization’s rules and data.
Example. In the demonstration, Camille has a 35-hour week and a seven-hour holiday; Alex has a 40-hour week and an eight-hour holiday.
Your rules need configuration and validation. The product does not promise automatic compliance with every collective agreement or regulation.
Do your differences concern schedules, holidays or time banks?
Explore the workflow ↗From entry to payroll, everyone knows the next step
The employee enters and submits a timesheet. The supervisor reviews, approves or requests a correction with a reason. The employee corrects and resubmits it. Payroll checks approved hours and can finalize or return the sheet according to authorized actions. Statuses, decisions and histories make the workflow clear.
Example. Camille mistakenly records three hours as overtime. Nora requests a correction; Camille changes them to regular hours and resubmits. The corrected week has 28 worked hours and seven holiday hours.
Preparing and validating payroll data does not establish automatic transmission to an external payroll system. That connection needs separate confirmation.
Who reviews timesheets in your organization before payroll processes them?
Explore the workflow ↗Property 360: context for a municipal record
Property 360 brings together available property information, assessments and documents while preserving their sources. Geospatial data depends on authorized connections and layers.
Example. VilleFictive uses the same fictional DEMO-042 property record to prepare a planning meeting and find a related document.
An imported history is not real-time synchronization. Combining sources grants no additional permissions, and mapping integrations need separate validation.
Which sources would you like to bring together: planning, assessments, documents or mapping?
Explore the workflow ↗Document management: documents in context
Document management supports finding folders, viewing authorized documents, following versions and applying configured retention rules. Effective access remains governed by the document and its sources.
Example. A team finds a property plan and its versions without gaining access to every organizational folder.
Storage connectors, imports and synchronization each have their own scope. Microsoft Entra sign-in does not establish access to Microsoft 365 files.
Are your documents currently on a file server, in Microsoft 365 or elsewhere?
Explore the workflow ↗CRM: follow relationships and sales opportunities
CRM includes prospects, contacts, opportunities, pipeline stages, activities and histories. Records are followed by owner or team according to permissions. Links to other modules retain their source permissions.
Example. A team tracks an opportunity, its value and its next action. The demonstration has four open opportunities totaling CAD 12,850.
The new graphical composition and sales target are a planned evolution, separate from the existing CRM view. A cross-module view does not grant access to every division by default.
Should customers be shared across teams, or should some records remain within one team?
Explore the workflow ↗Inventory: quantities, locations and movements
Inventory workflows help locate items or assets and follow supported movements. Receipts, issues and reservations feed the quantities in the demonstration dataset.
Example. VilleFictive receives parts, issues some for an intervention and checks the remaining stock; totals agree with the movements.
Stock and asset registers are separate workflows. Visible scopes and purchasing or maintenance connections depend on enabled modules and permissions.
Do you mainly manage consumables by quantity, assigned assets, or both?
Explore the workflow ↗Hosting and isolated customer organizations
An isolated customer organization has its own data and access scope; it is not an internal division or a Microsoft authentication tenant. Internal division and team workflows exist independently of the multi-organization hosting work.
Example. A company can structure its divisions within its organization. Two independent customers need distinct hosting and authorization isolation, even on shared infrastructure.
Backups, restores and moves have been validated in isolated test environments. Production multi-organization delivery and full portability remain to be accepted. Dedicated or on-premises hosting requires qualification of prerequisites, operations and recovery. No unprepared migration or consolidated cross-customer view is promised.
Are you organizing divisions of one company, or hosting several independent customer organizations?
Explore the workflow ↗Keep your technologies and prepare for change
OrganisasionOS builds on existing tools and connects the workspace to services through Core and connectors. Microsoft Entra authentication works on configured installations; it is not complete Microsoft 365 integration.
Example. An organization keeps its current sign-in and then assesses document integration or a storage change without replacing its entire environment at once.
Email, calendars, files, migration and Google are validated separately. Interface continuity does not guarantee continuity of data, permissions and functions when changing providers.
Which existing services are your priority to keep?
Explore the workflow ↗The Companion’s role
The Companion is a shared desktop access point for applications and services authorized by the organization. Its workflows and chat have their own acceptance scopes; it does not replace Core’s rules.
Example. A person finds authorized tools in the same catalogue; the website shows distinct assistant, documents, telephony and application views.
Conceptual visuals are labeled. Remote administration of enrolled workstations and AI assistance inside every Craft application remain planned developments, not capabilities already delivered everywhere.
Is your priority application access, documents or the assistant?
Explore the workflow ↗APIs and specialist integrations
The business APIs used by the Portal exist. Internal contracts support planning specialist modules. Documentation for your scope is available on request using “API / specialist integration”.
Example. A time clock could send attendance into time and approval workflows after the hardware and protocol have been assessed.
Time-clock, machine and sensor connections need assessment. Collecting information is different from remotely controlling equipment. No universal connector or public API documentation portal is advertised.
Which equipment or software would you like to connect, and what information should it exchange?
Explore the workflow ↗