The Reality of Multiple Roles

Real life does not fit into single categories. People wear multiple hats, work across different contexts, and operate in overlapping roles:

• A veterinarian who also manages their own small livestock farm
• A farmer who runs a commercial cattle operation and rehabilitates injured wildlife
• A zoo curator who also serves as a consultant to wildlife conservation programmes
• A wildlife manager in a national park who also works part-time for a conservation NGO
• A conservation biologist who conducts field research, teaches university courses, and advises government wildlife departments
• A paraprofessional farm manager who keeps bees as a personal hobby

Kora's design recognises this complexity. You are not forced to choose one identity. The system adapts to support your multiple roles and contexts.

How Multi-Context Work Happens in Kora

Single User Type, Multiple Contexts

Many users have a single user type but work across different animal management contexts:

Example 1: Farmer with Diverse Operations

UserType: Farmer Contexts: Livestock (cattle), Beekeeping (apiary), Wildlife (rehabilitation)

Sarah runs a commercial beef cattle operation. She maintains beehives for pollination and honey production. She rehabilitates injured native birds as a licensed wildlife carer.

How Kora supports this:

• Same interface, context-adaptive terminology - When working with cattle, she sees paddocks and livestock features. When working with bees, she sees hive management tools. When working with wildlife, she sees rehabilitation workflows.
• Unified task management - Morning tasks might include checking cattle water, inspecting hive health, and feeding recovering birds. All in one task list.
• Single animal registry - All animals (cattle, bees, native birds) managed within one system
• Context-appropriate features - Livestock breeding records for cattle, apiary management for bees, release planning for wildlife

Sarah does not switch between different systems or user accounts. Kora recognises the context based on what animals she is working with. It adapts the interface accordingly.

Example 2: Wildlife Manager with Multiple Responsibilities

UserType: Wildlife Management Contexts: National park wildlife populations, endangered species research, anti-poaching operations

James manages wildlife in a 50,000-hectare national park. He tracks elephant populations (mob-level monitoring). He monitors GPS-collared rhinos (individual tracking). He coordinates anti-poaching patrols. He contributes data to a national endangered species database.

How Kora supports this:

• Mixed individual and mob tracking - Track 200 elephants as populations, 12 rhinos individually with GPS integration
• Multiple location hierarchies - Park subdivided into territories, patrol zones, conservation areas
• Cross-organisational data sharing - Contribute rhino data to national studbook while maintaining park-specific records
• Security and conservation features - Poaching incident reporting, ranger patrol coordination

James operates in multiple contexts (population monitoring, individual conservation, security operations, research collaboration). All within his Wildlife Management user type.

Multiple User Types, Multiple Contexts

Some users legitimately need multiple user types because their roles span fundamentally different access patterns:

Example 3: Veterinarian Who Also Farms

Primary UserType: Veterinarian Secondary context: Farmer (own livestock)

Dr. Maria is a licensed veterinarian operating a mobile practice serving 30 client farms. She also manages her own small cattle herd at home.

How this works:

• Veterinarian access for professional work - Cross-property access to all client animals, veterinary observation capabilities, health certificate generation, clinical diagnosis features
• Farmer access for personal animals - Complete management of her own cattle herd
• Clear separation - When she accesses her own animals, she operates as owner (Farmer context). When she accesses client animals, she operates as veterinarian with professional responsibilities and logged access.

Permission structure:

• Advanced permissions for veterinary professional work (cross-property medical records)
• Standard permissions for her own farm operations
• System tracks which context she operates in based on which animals she accesses

This dual role is common. Kora supports it naturally. The system knows the difference between "Dr. Maria treating a client's cow" (Veterinarian role, logged access, professional liability) and "Maria managing her own cattle" (Farmer role, personal property).

Example 4: Conservation NGO Staff Member Who Also Teaches

Primary UserType: Conservation & NGO Secondary context: Education

Michael works full-time for a primate conservation NGO. He coordinates breeding programmes across seven zoos internationally. He also teaches a conservation biology course at the local university using the NGO's field data.

How this works:

• Conservation & NGO access - Manage studbook, coordinate breeding transfers, access records across participating institutions, CITES compliance
• Education context - Grant students ReadOnly access to de-identified field research data, demonstrate conservation workflows, teach practical animal management skills

Permission structure:

• Advanced permissions for NGO work (cross-institutional breeding programme management)
• Limited delegation - Grant students temporary ReadOnly access to specific datasets
• Clear boundaries between professional conservation work and educational demonstration

Example 5: Regulatory Inspector with Personal Hobby Farm

Primary UserType: Regulatory Authority Secondary context: Farmer (personal animals)

John is a government livestock inspector responsible for biosecurity compliance across 200 commercial farms in his region. He keeps backyard chickens and two goats at home for personal enjoyment.

How this works:

• Regulatory access - ReadOnly or limited access to farms he inspects, disease surveillance data, cross-property compliance monitoring
• Personal farmer access - Complete management of his own small backyard flock and goats

Permission structure:

• ReadOnly to Basic for regulatory work (view compliance data, record inspection findings)
• Standard permissions for personal animals
• Strict separation to prevent conflict of interest (cannot inspect his own property records with regulatory access)

This separation is critical for professional ethics and data integrity.

Navigating Multiple Contexts

When you work across multiple roles or contexts, Kora provides several mechanisms to keep things organised:

Context Recognition

The system recognises context based on:

• Which animals you are working with - Cattle vs. bees vs. wildlife vs. zoo animals
• Which property you are accessing - Your own farm vs. client properties (for veterinarians)
• Which features you are using - Livestock management vs. conservation genetics vs. regulatory compliance

You do not manually switch modes. The interface adapts naturally based on what you are doing.

Permission Boundaries

Even with multiple contexts:

• Access boundaries remain clear - Veterinarian cannot access client animals' ownership transfer records beyond medical necessity
• Professional separation maintained - Regulatory inspector accessing farm data for compliance sees different scope than when managing personal animals
• Audit trails track context - System logs which "hat" you were wearing for each action

Organisational Separation

When working across organisations:

• Property-based boundaries - Your own farm's data is separate from client farms
• Cross-organisational coordination - Conservation programmes share data through explicit authorisation
• Role-appropriate access - See only what your current role and relationship justify

Common Multi-Context Scenarios

Scenario 1: Farmer Diversifying into Agritourism

Starting point: UserType: Farmer Context: Commercial sheep farming Permissions: Standard

Evolution: Starts offering farm tours, petting zoo, and educational programmes. Now manages:

• Commercial sheep flock (livestock production)
• Petting zoo animals (goats, rabbits, chickens)
• Educational demonstrations (showing visitors lambing, shearing, herding)

Kora adaptation:

• Same Farmer user type, expanded contexts
• Add petting zoo animals with individual tracking for welfare monitoring
• Task workflows expand to include visitor management and educational scheduling
• Biosecurity features activated to manage visitor risk

No user type change needed. Permissions and features adjusted to reflect expanded scope.

Scenario 2: Veterinarian Expanding Practice

Starting point: UserType: Veterinarian Context: Small animal practice (dogs, cats) Permissions: Advanced

Evolution: Expands to also serve:

• Livestock farms (cattle, sheep)
• Equine clients (horses)
• Exotic animal consultations (zoo, wildlife rehabilitation)
• Teaching veterinary students

Kora adaptation:

• Same Veterinarian user type
• Cross-property access extends to new client types
• Education context added for student teaching
• Specialised features enabled (livestock treatment protocols, exotic animal medical records)
• Student accounts created with ReadOnly access to de-identified teaching cases

Veterinarian role naturally accommodates expanding scope.

Scenario 3: Wildlife Manager Becoming Conservation Coordinator

Starting point: UserType: Wildlife Management Context: National park field operations Permissions: Standard

Evolution: Promoted to regional coordinator role managing:

• Multiple protected areas (cross-property wildlife monitoring)
• Conservation partnerships with NGOs
• Regional studbook coordination for endangered species
• Government reporting and compliance

Kora adaptation:

• User type might shift to Conservation & NGO or stay Wildlife Management
• Permissions elevated to Advanced
• Cross-property access granted for coordinated conservation areas
• Studbook management features enabled
• Regional reporting and analytics access

Role expansion triggers permission adjustment and feature activation.

Scenario 4: Paraprofessional with Side Projects

Starting point: UserType: Paraprofessional Context: Zoo animal care specialist Permissions: Standard

Personal context: Also keeps personal aquarium (saltwater reef tank) and volunteers at wildlife rescue centre

Kora adaptation:

• Primary zoo work continues as Paraprofessional with Standard permissions
• Personal aquarium managed as Public user type with Basic permissions (separate property)
• Volunteer wildlife rescue work: ReadOnly to Basic access to rescue centre's animals (limited ability to modify data owned by rescue organisation)

Multiple contexts coexist: professional zoo work, personal hobby, volunteer service. Each with appropriate access boundaries.

Requesting Multi-Context Support

If your work spans multiple contexts and you find the current configuration limiting:

Identify the specific challenge:

• "I am a veterinarian but also manage my own farm. I need to clearly separate my client work from my personal animals."
• "I work for a conservation NGO managing breeding programmes, but I also teach university students using our field data. Students need view-only access to specific datasets."
• "I am a farm manager during the day and volunteer at a wildlife rescue centre on weekends. I need access to both but cannot mix the data."

Describe what you are trying to accomplish:

• Professional/personal separation
• Cross-organisational access with appropriate boundaries
• Multi-role coordination with different permission levels
• Teaching or training access alongside operational work

Work with your administrator: System administrators can:

• Configure multiple properties for different contexts under your account
• Adjust permissions by property or animal type
• Enable context-specific features
• Grant temporary elevated access for specific projects
• Create clear organisational separation

The Unopinionated Advantage for Multi-Context Users

Traditional opinionated systems force you to choose: "Are you a farmer or a veterinarian?" "Is this livestock or wildlife?" "Is this commercial or conservation?"

Kora's unopinionated design says: "You can be all of those things. Tell us what animals you are working with, and we will adapt."

This flexibility is especially valuable for:

• Professionals with diverse portfolios - Veterinarians, consultants, specialists
• Organisations with multiple missions - Farms with agritourism, zoos with conservation programmes, NGOs with education components
• Rural contexts - Where people wear many hats by necessity
• Career transitions - Moving from one role to another without losing historical continuity
• Collaborative projects - Temporary cross-organisational work without permanent role changes