Understanding the dual-purpose design of this plugin is essential before using it. There are two completely separate systems running within the same plugin.

Side 1: Admin Staff Team (Internal) #

Where: DMSI DDLS > Team > Team Members / Roles / Workload / Activity Log

Purpose: Manage your own company’s staff who work in DDLS.

Data stored: Staff roster in the dmsilm_tm_admin_team_members table.

Roles available: Admin, Manager, Support, View-Only (built-in), plus up to 50 custom roles.

How staff log in: As regular WordPress users. When a user is added to the staff team and assigned a role, they gain access to the DDLS admin areas that their role permits.

Key limitation: A staff member must already have a WordPress user account on your site. Team Management maps existing WordPress users to DDLS staff roles.

Side 2: Customer Team Licenses (External) #

Where: Customer portal pages on your public-facing website.

Purpose: Let customers who purchased a Team License manage which of their colleagues share that license.

Data stored: Customer team members in the dmsilm_tm_customer_team_members table, linked to specific license IDs.

Roles available: Team Admin (can manage the team) and Team Member (access only).

How customers access their team: Through the DDLS customer portal (typically at /my-account/ or a dedicated portal page). Team pages appear in the portal navigation when a customer holds a team license.

Key point: Customer team members are your customers’ employees or colleagues. They are NOT your internal staff.

Why They Are Separate #

These two systems solve different problems: