Use Case: Limiting Project Access to a Single Department
- A Department Property Object exists.
- The Project object references the Department property.
- Project Task references the Project object.
- A Permission Group exists for Engineering users.
- RBAC permissions are already configured for Project and Project Task.
Business Context:
Departments should work only with their own projects. Users must not see projects or tasks belonging to other departments. You want a simple, direct rule that enforces this separation without adding multiple roles.
Overview:
This use case shows how you can limit access using a single business property.
- Projects are tagged with a Department value.
- Only users in the Engineering department can access Engineering projects.
- The same restriction automatically applies to tasks related to those projects.
This ensures users see only the projects and tasks that belong to their department.
Scenario:
Projects are tagged with a Department property such as Engineering, Sales, or Finance.
Each Project includes related Project Tasks.
You want to ensure:
- Engineering users can access only Engineering projects.
- Engineering users can also access tasks under those projects.
- Projects from other departments are completely hidden.
- Engineering users can access only Engineering projects.
- Engineering users can access tasks only when they belong to Engineering projects.
- Projects and tasks from other departments are hidden.
- Access control remains simple, consistent, and scalable.