Profiles and Adaptability
Orgo is designed to serve organizations with very different operating rhythms without forking the core system for each one.
The main mechanism is the Organization Profile.
What a Profile changes
A Profile can tune defaults such as:
- expected reactivity;
- transparency and visibility defaults;
- escalation behavior;
- sensitivity to recurring patterns;
- retention behavior;
- automation and review cadence.
A fast-response environment can therefore behave differently from a volunteer association while both still use the same Task and Case model.
What a Profile does not change
A Profile does not create a new Orgo schema or a separate Task lifecycle.
same core model
+ different profile
= different operating behavior
This is one reason Orgo can be adapted across domains without becoming a collection of unrelated applications.
Profiles and domain modules
Profiles tune organizational behavior. Domain modules add specialized context.
They solve different problems:
Profile → how this Organization operates
Domain module → what this kind of work means