Teams in District Engage help you organise projects and control access to content. This article explains how to create and manage teams effectively.
Before you begin
Only users with administrator permissions can create and manage teams. Teams must be enabled in your site settings.
Types of Teams
District Engage offers two types of teams to match different organisational needs:
Regular Teams
- Team members get access to all team projects
- Maintains existing system-level permissions for non-administrators
- Perfect for standard project collaboration
Restricted Teams
- Provides enhanced security for sensitive projects
- Only team members and administrators can access content
- Ideal for internal or confidential projects
How to Create a Team
- From the Dashboard, click People in the left-hand menu
- Click the Teams tab
- Click the + icon in the top right corner
- Fill in the following details:
- Title: Enter a name for your team
- Description: Add details about the team's purpose
- Team Type: Choose Regular or Restricted
- Click Save to create the team
How to Add Team Members
- Navigate to the team you want to edit
- Click the Members tab
- Click + Add member
- Search for the user you want to add
- Select a role for the team member
- Click Add to confirm
When adding members to a Restricted team, remember that only these members and site administrators will be able to access the team's projects and content.
Team Roles and Permissions
The table below outlines what each role can do within a team:
Team Lead |
|
Project Manager (assigned to a team) |
|
Other Team Roles Including:
|
These roles retain their standard system permissions (see Understanding User Roles) but their access and capabilities are limited to projects within their assigned team(s). For example, a Publisher assigned to Team A can only publish content for Team A's projects. |
Multiple Roles
Users can have multiple roles within a team, or different roles across different teams. For example, someone could be a Team Lead in one team and a Project Manager in another.
Best Practice
Assign team roles based on job responsibilities and maintain the principle of least privilege - only give users the access they need to perform their tasks.