RoleDefinitions - IEEE-Team-3/map GitHub Wiki
Roles define what a user can do within a team. Each role comes with a predefined set of permissions that govern access to various features and actions.
- Creator and ultimate controller of the team.
- Has access to all features, settings, and can manage roles.
- Only one owner per team.
- Helps the owner manage the team.
- Can change settings, manage members, create sub-teams, and more.
- Cannot delete or transfer ownership of the team.
- Manages people-centric tasks like member onboarding, role assignments, and internal communication (e.g., chat and announcements).
- Cannot manage settings or create nested teams.
- Standard user role with access to tasks, chat, announcements, and visibility into their own performance on leaderboards.
- Has limited, read-only access to view announcements and tasks, depending on the privacy settings.
Each role can be scoped globally (entire team) or locally (specific nested team or task board).
- Role tagging (e.g., Developer, Designer, etc.)
- Contextual roles for projects or temporary assignments.