> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/faqs/the-concept-of-tenant-in-digit.md). # The concept of Tenant in DIGIT #### What is a tenant? In the context of software architecture, a "tenant" typically refers to an individual or organization that uses a shared software application or service. Each tenant operates within its isolated portion of the application's resources, such as data, configuration, and user interface. #### What is a multitenant system? Multitenancy refers to a software architecture where a single instance of the software serves multiple tenants or clients. Each tenant typically has its own isolated and customizable environment, but they all share the same underlying infrastructure and codebase. In a multitenant system, tenants are often distinguished by factors such as data, configuration, user interface, and access rights. This architecture is commonly used in cloud-based applications, where it allows software providers to efficiently serve multiple customers while minimizing infrastructure costs and maintenance efforts. For example, in a multitenant web application, each tenant might have its own database or database schema or data partition, ensuring data isolation and security. However, all tenants share the same application codebase and runtime environment, reducing overhead and simplifying updates and maintenance. #### Goals and Objectives * Implement multi-tenancy to support multiple tenants within a single instance of the platform and product. * Enable creation, updating, and searching of tenants/accounts * Ensure data isolation and security by enforcing tenant-level authorization. * Provide configuration options for administrators to customize system behaviour. #### Key Stakeholders * Development Team * Project Stakeholders * End Users --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digit.org/faqs/the-concept-of-tenant-in-digit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.