Capabilities

Capabilities are the skills or roles used for project staffing. They should be specific enough to support planning but broad enough that they stay maintainable.

When your role includes financial visibility, capabilities can also hold default cost and bill rates. Those rates help Supervisible estimate cost, revenue, and margin before a specific person is staffed.

Where Capabilities Are Used

• Member profiles.
• Project requirements.
• Unassigned project reservations.
• Command Center.
• Workload assignment flows.
• Project and member filters.
• Public API and MCP context.

Managing Capabilities

Admins can create, edit, archive, restore, and delete capabilities from Settings -> Capabilities.

Each capability has:

• Name.
• Optional description.
• Default cost rate, when financial fields are visible.
• Default bill rate, when financial fields are visible.
• Active member count.

The list has active and archived views. Active capabilities are available in staffing pickers and project setup. Archived capabilities stay attached to historical data, but they are removed from active assignment and API resolution flows until restored.

The inspector and inline list let admins update details and rates. Capabilities that are already used can be archived instead of deleted; delete is reserved for safe cleanup.

Default Rates

Changing a capability default fills unrated matching assignments so current project totals can update, but it does not overwrite explicit row or member rates.

Good Capability Sets

Examples:

• Strategy, Project Management, Design, Web Development, Data, Content.
• Senior Designer, Designer, Design Director if seniority affects staffing.
• Shopify, Webflow, Paid Media, Analytics if tools or service lines drive assignments.

Avoid duplicating synonyms like "Dev", "Developer", and "Engineering" unless the distinction changes staffing decisions.

Related

• Members
• Creating a Project
• Command Center