@Chandrababu

Set up project-scoped access in Agile Studio instead of letting everyone use broad roles. Create separate Programs/Workspaces for each application and mark each Product as Private, then add only the correct Teams to its access list. In Settings > Security, enable team-based and org-unit scoping so objects are visible only to members of the owning team/program. Remove global roles (like ASAdmin/ASLead) from users who don’t need cross-project visibility and give them project-specific roles (ASDeveloper, ASTester, ASProductOwner) via the right team. If you need stronger enforcement, add ABAC policies on Product/Feature classes that allow read/update only when the user’s team/program matches the item’s owner fields. For hard isolation, create two access groups pointing to separate Agile Studio applications and assign users accordingly. After changes, reindex search and ask users to relogin. Finally, run an access audit report to confirm no one outside a team can open the other project’s product.