| Warning |
|---|
Organisations is currently in BETA mode and has not been formally released at this time - meaning that all functionality and literature around it are subject to change prior to its official launch. The documentation below is only designed to be used as an aid to support discussions with customers around the principles of Organisations, prior to its official release - at which time, fuller documentations and training options will be available. |
What Is Organisations?
Organisational tenancy in a self-service context involves explaining how multiple organizations can independently manage their resources and users within a shared system or platform, while maintaining privacy and security. In a self-service context, this typically means providing organizations with the tools and permissions to autonomously manage their own segment of the platform, such as user accounts, data, and customization settings, without the need for direct intervention from the system's administrators. Here's a detailed way to describe it:
Definition and Purpose: Start by defining what organizational tenancy is—essentially, it's a way to partition a single instance of a software application to support multiple tenants (organizations or departments), allowing each to operate as if they have their own dedicated instance. The purpose is to ensure data isolation, security, and a tailored experience for each tenant, while benefiting from economies of scale.
Self-Service Capabilities: Highlight the self-service capabilities that enable organizations to manage their tenancy autonomously. This includes creating and managing user accounts, setting permissions and roles, customizing the interface and functionality to suit their needs, and handling their own data securely.
Privacy and Security: Explain how the system ensures privacy and security for each tenant. Despite sharing the same underlying resources, data and operations are isolated so that one tenant cannot access another's data. This is often achieved through rigorous access controls, data encryption, and other security measures.
Scalability and Efficiency: Discuss how organizational tenancy in a self-service context allows for scalability. As organizations grow and their needs evolve, they can adjust their usage of the platform, add more users, increase data storage, and utilize more features, all without requiring direct support from the service provider.
Examples and Use Cases: Provide examples or use cases to illustrate how different organizations might utilize their tenancy. For instance, a university might manage different departments as separate tenants, each with its own set of users, courses, and resources, while a multinational corporation might manage each country operation as a separate tenant.
Administrative Tools and Documentation: Mention the importance of providing tenants with robust administrative tools and comprehensive documentation. This ensures that they can effectively manage their tenancy, troubleshoot issues, and customize the platform to meet their specific needs.
Support and Community: Finally, note the role of support and community in a self-service context. Even though organizations manage their tenancy autonomously, access to a supportive community and responsive customer support from the platform provider is crucial for addressing complex issues and facilitating peer-to-peer help.
Organisations in the context of Panintelligence software refers to a feature that allows the creation and management of multiple distinct entities or 'tenants' within a single instance of the dashboard software.
...