Spheres within Spheres

Open

What is a Sphere in OrgBrain?

A Sphere is the fundamental data container and organizational unit in OrgBrain. Every instance of OrgBrain ties to a Sphere, which serves as the primary boundary for data storage, access control, and governance. Think of a Sphere as your organization's secure data vault where all information, models, and AI interactions are contained and managed.

What are sub-spheres and how do they work?

Sub-spheres are nested data containers within your primary Sphere that allow you to create isolated environments for specific purposes. They inherit the security and governance framework of the parent Sphere while providing additional segmentation and control. Sub-spheres enable you to organize data and AI operations based on your specific business needs while maintaining centralized oversight.

Why would I create sub-spheres?

Sub-spheres provide flexible data organization and isolation for various business scenarios:

• Regional compliance: Store data in specific geographic regions to meet local regulatory requirements

• Subsidiary management: Create separate environments for different business units or subsidiaries

• Client segmentation: Isolate client data for professional services or managed service scenarios

• Project isolation: Separate sensitive projects or initiatives from general organizational data

• Security levels: Create different security zones for varying data sensitivity levels

• Departmental boundaries: Provide isolated environments for different departments or teams

How do sub-spheres handle data sovereignty?

Sub-spheres can be configured to store data in specific regions or infrastructure environments based on your requirements. This means you can create sub-spheres that comply with GDPR by storing European data in EU regions, maintain data residency for specific countries, or isolate data for clients who have particular sovereignty requirements—all while maintaining the ability to manage everything from a central control plane.

Can sub-spheres have different security policies?

Yes, while sub-spheres inherit the foundational security framework from the parent Sphere, they can implement additional security controls and policies specific to their purpose. This includes:

• Custom access controls and permissions

• Enhanced data protection measures

• Specific compliance requirements

• Tailored governance policies

• Unique audit and monitoring configurations

How do users access different sub-spheres?

Access to sub-spheres is controlled through OrgBrain's identity-first security architecture. Users can be granted permissions to specific sub-spheres based on their roles and responsibilities. The system ensures that users can only access the sub-spheres they're authorized to use, maintaining strict data boundaries between different organizational units or purposes.

Can data move between sub-spheres?

Data movement between sub-spheres is governed by your organization's data governance policies and compliance requirements. While the platform can support controlled data sharing between sub-spheres when appropriate, such transfers must be explicitly authorized and logged. This ensures that data movement respects regulatory requirements, client confidentiality, and organizational boundaries.

How do I manage multiple sub-spheres?

OrgBrain provides centralized management capabilities that allow administrators to oversee multiple sub-spheres from a single control plane. This includes:

• Unified user management and access controls

• Centralized monitoring and audit capabilities

• Consistent policy enforcement across sub-spheres

• Consolidated reporting and compliance tracking

• Coordinated backup and disaster recovery

Do sub-spheres affect AI model performance?

Sub-spheres are designed to maintain AI performance while providing data isolation. Each sub-sphere can utilize the same foundation models and AI capabilities as the parent Sphere, but the AI processing respects the data boundaries of each sub-sphere. This means AI agents and knowledge bots operate within their designated sub-sphere without compromising performance or functionality.

Can I create sub-spheres for external clients?

Yes, sub-spheres are ideal for professional services organizations, consultancies, or managed service providers who need to maintain strict client data separation. You can create dedicated sub-spheres for each client, ensuring their data remains completely isolated while still benefiting from your organization's AI capabilities and expertise.

How do sub-spheres handle compliance requirements?

Each sub-sphere can be configured to meet specific compliance requirements relevant to its purpose. For example:

• A healthcare sub-sphere can enforce HIPAA compliance

• A financial services sub-sphere can meet regulatory banking requirements

• A government sub-sphere can implement security clearance levels

What happens to sub-spheres when the parent Sphere is modified?

Sub-spheres maintain their independence while benefiting from parent Sphere updates. Security enhancements, new AI capabilities, and platform improvements in the parent Sphere are typically inherited by sub-spheres, but specific configurations and data within sub-spheres remain isolated and protected.

Can I create nested sub-spheres?

Yes, OrgBrain supports nested sub-spheres, allowing you to create hierarchical data organization structures. For example, you might have a regional sub-sphere for Europe, with nested sub-spheres for individual countries, and further nested sub-spheres for specific subsidiaries within each country.

How do I migrate data between sub-spheres?

Data migration between sub-spheres is handled through controlled processes that respect governance policies and compliance requirements. The platform provides tools for authorized data movement while maintaining complete audit trails and ensuring that all transfers comply with your organization's data handling policies.

What are the cost implications of multiple sub-spheres?

Sub-spheres are designed to be cost-effective organizational tools. While each sub-sphere maintains its own data storage and processing capabilities, the overall infrastructure is shared efficiently. Costs are determined by the specific use-cases.

How do sub-spheres support disaster recovery?

Each sub-sphere can have its own backup and disaster recovery configuration based on the criticality and requirements of the data it contains. This allows for tailored recovery strategies—critical client data might have more frequent backups and faster recovery times, while less sensitive data might use more cost-effective backup strategies.