Overview
Job roles are the bridge between people, rate cards, time entries, and billing. A role such as UX Designer or Project Manager can exist at the organization level, appear on a rate card, and then be assigned to a member for a specific client or project.
The key distinction is scope: an org-level role means a member is eligible to use that role. A client or project billing-role assignment means the member is actually configured to use that role in that work context.
The three layers
| Layer | Meaning | Example |
|---|---|---|
| Organization job role | The role exists in your workspace. | UX Designer. |
| Member role | The member is eligible to perform or bill as that role. | Alex has UX Designer. |
| Client or project billing role | The member is assigned to use that role for a client or project. | Alex is UX Designer on Website Redesign. |
Set up roles
- Open Profitability → Settings → Rates → Roles.
- Create the roles your team prices, reports, or plans by.
- Assign each member the org-level roles they can use.
- For client-level billing, add the member to the client's billing roster and choose one or more roles.
- For project-level billing, add the member to the project and choose one or more billing roles for that project.
Create client billing-role assignments
Use client billing-role assignments when the same member-role setup should apply to work under a client. This is the cleanest setup when a client has standard role pricing or a client-level rate card.
- Open Profitability → Settings → Rates → Rates.
- In View by, choose Clients (the label follows your workspace name for clients).
- Select the client that should use the member's billing role.
- Find the Billing Members card for that client.
- If the member is not listed, click Add member, choose the member, and continue.
- In the Billing roles for [member name] dialog, select the roles they can bill as for that client, such as UX Designer or Project Manager.
- Click Preview impact when available to see which inheriting projects will change.
- Click Apply change or Save to finish.
If projects under that client inherit client billing roles, the assignment can flow down to those projects. If a project uses its own project-level override, edit the project billing roles instead.
Create project billing-role assignments
Use project billing-role assignments when a specific project needs its own staffing, pricing, or role restrictions.
- Add the member to the project first if they are not already a project member. Project billing roles can only be configured for project members.
- Open Profitability → Settings → Rates → Rates.
- In View by, choose Projects.
- Select the project that should use the member's billing role.
- Find the Billing Members card for that project.
- Find the member's row. If the row says Access only — no billing roles configured, open the row action menu and choose Configure billing roles. If the member already has billing roles, choose Edit billing roles.
- In the Edit billing roles dialog, select the roles they can bill as on that project.
- If the member is currently inheriting billing roles from the client, confirm Disable inheritance & save when prompted. This saves the selected roles as a project-level override.
- Click Save.
After saving, the project can resolve role-based rates for that member from the project rate card, the client rate card, or a more specific member override, depending on your rate setup.
Client roles vs project roles
Client billing roles are useful when the same member-role setup should apply across many projects for that client. Project billing roles are useful when a specific project needs a different roster or different role selection.
- Use client roles when a member usually bills the same way for all work under that client.
- Use project roles when the project has its own staffing, special pricing, or role restrictions.
- Use inheritance when projects should pick up the client's billing roster automatically.
- Use project override when the project should ignore the inherited client billing roles.
Eligibility is not assignment
A member can be eligible for a rate card because they have a matching org-level role. They are not actually assigned to use that card until they are assigned to the matching billing role on a client or project that uses the card.