---
title: "Build for multiple customer organizations | OwlMeans"
description: "Use organization entities when your app serves several customer organizations."
url: "https://owlmeans.com/docs/platform/how-to/build-for-multiple-customer-organizations/"
lang: "en"
---

# Build for multiple customer organizations

![](https://owlmeans.com/_astro/platform-how-to-build-for-multiple-customer-organizations.CwnVQZ6r_Z1lrHUA.webp)

Use organization entities when your app serves several customer organizations. Each organization entity has members and an access boundary. A data-model entity, such as a task, is a different concept.

1.  State the customer boundary in your specification: which records belong to each organization entity and which roles manage its membership.

2.  Open the project’s organization and group controls in the intended scope.

    ![Organization entities: customer organizations and their application membership.](https://owlmeans.com/_astro/app-organizations.DjxRnpwx_1S8NgY.webp)

    Organization entities: customer organizations and their application membership.

3.  Add or manage members and group membership using the available controls.

4.  Review organization-scoped permissions and grants.

5.  Test with two synthetic customer organizations. Confirm each user sees only the records their permissions allow.

6.  Test a user with membership in more than one organization entity and check the intended context.

For Task Grove, two customers can use the same application while managing separate projects. A manager in one customer organization should not gain access to the other’s tasks.

> Multi-tenancy means one application serves several customers while keeping their access separate. Define and test that separation alongside the business features.

The [MCP organization tools](https://owlmeans.com/docs/mcp/reference/application-users-permissions-and-organizations) expose organization names, members, groups and grants. Use `entitySlug` when a tool requests the customer organization’s name. Preserve access checks when asking an agent to add new record types.

## Application example

**Category:** Project and task management. **Example:** Task Grove, a task board for a small team.
