Docs
Admin

Capabilities

Define the skills and roles your team members can contribute to projects.

Capabilities

Capabilities are the skills, disciplines, or roles that team members bring to projects. When you assign someone to a project, you specify which capability they're contributing—helping you understand what skills are allocated where.

Why Capabilities Matter

  • Project planning: See what skills are assigned to each project
  • Resource matching: Find team members with specific capabilities
  • Workload analysis: Understand how different skills are utilized
  • Profile enrichment: Team members showcase their expertise

Managing Capabilities

Viewing Capabilities

Navigate to SettingsCapabilities to see all defined capabilities in your organization.

Creating a Capability

  1. Go to SettingsCapabilities
  2. Click Add Capability
  3. Enter the capability name (e.g., "UI Design", "Backend Development", "Project Management")
  4. Click Save

Editing or Removing

  • Click on a capability to edit its name
  • Use the delete button to remove unused capabilities

Note: You cannot delete a capability that's currently assigned to members or projects.

Assigning Capabilities to Members

Team members can have multiple capabilities reflecting their skills:

Via Profile Settings

  1. Navigate to your Profile
  2. Find the Capabilities section
  3. Click to add capabilities from the list
  4. Or type to create a new capability

Via Admin Settings

Admins can assign capabilities when managing members:

  1. Go to SettingsMembers
  2. Click on a member
  3. Add capabilities in their profile section

Using Capabilities in Projects

When adding team members to a project:

  1. Open the project detail page
  2. Click Add Row in the workload table
  3. Select a team member
  4. Choose their capability for this project
  5. Enter their hours

The same person can be assigned to a project multiple times with different capabilities (e.g., both "Design" and "Project Management").

Common Capability Structures

By Discipline

  • UI/UX Design
  • Frontend Development
  • Backend Development
  • DevOps
  • Quality Assurance
  • Project Management
  • Strategy

By Seniority

  • Junior Developer
  • Senior Developer
  • Lead Developer
  • Principal Developer

By Function

  • Design
  • Development
  • Management
  • Research
  • Support

Choose a structure that matches how you think about roles in your organization. Most agencies use discipline-based capabilities.

Best Practices

Start simple. Begin with 5-10 core capabilities that cover your main disciplines. Add more as needed.

Be consistent. Use the same capability names across the organization. "UI Design" and "UX Design" as separate capabilities causes confusion.

Avoid over-granularity. "React Development" and "Vue Development" are usually better combined as "Frontend Development" unless the distinction matters for billing or staffing.

Review periodically. As your services evolve, update capabilities to reflect what you actually do.