NestedTeamsLogic - IEEE-Team-3/map GitHub Wiki

Nested Teams Logic ๐Ÿ“‚

TeamApp allows teams to be organized in a hierarchical manner, where teams can create and manage sub-teams. These sub-teams inherit certain permissions from their parent teams, but also have the ability to be customized.


Features:

  • Parent-Child Relationship: Teams can have nested teams, and these teams can be further nested.
  • Inheritance of Permissions: Sub-teams inherit the core permissions and settings from their parent team, but they can be customized with different settings as needed.
  • Role Propagation: Roles and permissions set at the parent team level can be propagated to the sub-teams or overridden depending on the sub-teamโ€™s requirements.
  • Team Permissions: Permissions (like chat access, task assignments, etc.) can be controlled both at the parent and sub-team levels, making the app more flexible.

Use Case:

  • Main Team: A large team with multiple areas of focus can have sub-teams to handle specific tasks or projects.
  • Sub-teams: Each sub-team may have its own set of permissions, tasks, and chat groups but still remain part of the parent team for management purposes.

Benefits:

  • Organized Structure: Nested teams allow for better management of large teams with multiple areas of focus.
  • Flexibility: While sub-teams inherit key permissions from parent teams, they can also operate with unique settings and roles.

Key Considerations:

  • Access Control: Only team owners and those with high-level permissions (Admin, HR) can create nested teams.
  • Visibility: Ensure that visibility and access to resources are carefully controlled when dealing with nested teams.
โš ๏ธ **GitHub.com Fallback** โš ๏ธ