1. Understanding the Role Types
Before setup, it is important to distinguish between the two role categories:
Customer Roles: A free feature available to all GUIDEcx users. These define the roles of external stakeholders (e.g., "Champion," "Executive Sponsor").
Project Roles: A premium feature included with the Resource Management package. While basic tiers provide "Project Manager" and "Team Member," premium tiers allow for unlimited custom internal roles (e.g., "Engineering," "Onboarding Specialist").
2. Configuring Roles in Resource Management
To manage the global list of roles available in your workspace, navigate to Resource Management: Click on Resource Management in the left-hand sidebar.
Manage Customer Roles:
Click the Customer Roles tab.
To set permissions, click the Project View Permission dropdown next to a role.
Choose Full Plan View (Full Access) or Portal View (abbreviated experience focused on their specific tasks).
Manage Project Roles:
Click the Project Roles tab.
To create a new role, click + Add Project Role.
Type the name (e.g., "Marketing") and click the Avatar icon under "Assigned Members" to search for and select internal team members to fulfill that role.
Only Admins and Managers can create, edit, and delete Customer and Project Roles.
3. Assigning Roles to Tasks in Templates
For roles to automate assignments in active projects, they must be linked to tasks within your Templates.
Click Templates in the left-hand sidebar and select a project template.
Select a Task from the plan view.
In the task details drawer, locate the Role field.
Set Responsibility:
If the task is internal, ensure Responsibility is set to Internal and select the appropriate Project Role (e.g., Project Manager).
If the task is for a client, set Responsibility to Customer and select the appropriate Customer Role (e.g., Champion).
Tasks assigned this way will automatically be funneled to whichever user is assigned that role when a project is launched from the template.
4. Roles in Active Projects
Once a project is created, you must assign specific users to the roles defined in the template.
Open the Team Tab: Navigate to your active project and click the Team tab.
Assign Customer Roles:
Locate the customer role (e.g., "Champion").
Click + Add User.
Choose New Customer to invite a new contact or Existing Customer to search your database.
Check the box Assign all unassigned roles to this user to immediately populate their task list.
Assign Project Roles (Internal):
Locate the internal role (e.g., "Customer Success Manager").
If using premium Resource Management, look for the "Best Match" pill. GUIDEcx will suggest the team member with the highest availability and best skill match.
Click + Add User to assign the team member to the role.
5. Reviewing the Automated Plan
Navigate to the Plan tab of your project.
Review your tasks. You will see that the Assignee column is now populated with the specific users you added to the Team tab, based on the roles you designated in the original template.
Best practices for creating customer and project roles
Roles work best when they represent repeatable responsibilities in your onboarding process. A useful role should help answer a simple question:
Who should own this type of work when this project is created?
Instead of recreating every job title used by your organization or your customers, focus on the people who consistently own tasks, decisions, approvals, or deliverables.
Create roles around responsibilities, not specific people
Use role names that can be reused from project to project.
For example, instead of creating a project role called Sarah – Technical Services, create Technical Consultant. Sarah may fill that role on one project while another consultant fills it on the next.
The same principle applies to customers. A customer's exact title might be "Director of Business Systems," but if that person is responsible for technical setup during every implementation, IT Lead or Technical Lead may be a more reusable Customer Role.
This makes your templates easier to maintain as team members and customers change.
Start with the work in your project template
A practical way to build your role list is to review your standard implementation template and look at who typically owns each group of tasks.
For an onboarding process that includes kickoff, configuration, data migration, integrations, training, and launch, your roles might look like this:
Role | Example responsibilities |
Implementation Manager | Runs kickoff, manages milestones, follows up on risks, and coordinates launch readiness |
Implementation Consultant | Leads configuration and solution-design activities |
Technical Consultant | Handles integrations, SSO, API work, or other technical requirements |
Data Migration Specialist | Supports data mapping, imports, migration testing, and validation |
Training Specialist | Prepares and delivers administrator or end-user training |
Customer Success Manager | Participates in the transition from implementation to ongoing success |
You do not need every role in every implementation. Create the roles that correspond to work your team assigns repeatedly.
Use Customer Roles to define who you need from the customer
Customer Roles are especially useful when your implementation depends on participation from several people within the customer's organization.
For example:
Customer Role | When you might use it |
Customer Project Lead | Coordinates the implementation internally and keeps customer-owned work moving |
Executive Sponsor | Provides executive alignment, resolves major blockers, or approves key decisions |
IT Lead | Owns SSO, security, integrations, networking, or technical prerequisites |
Data Owner | Provides source data, reviews mappings, and validates migrated data |
System Administrator | Participates in configuration and prepares to administer the solution after launch |
Training Lead | Coordinates training, internal communications, or end-user enablement |
Choose names your project team and customers can understand without needing to know your internal terminology.
For example, Customer Project Lead is usually more useful than a role such as Operations Level 2, unless "Operations Level 2" has a consistent meaning across your customer base.
Don't create a role unless it changes ownership
Avoid creating roles simply to describe everyone involved in a project.
Suppose your customer's implementation includes a Finance Director, VP of Operations, and COO. If none of those people owns a distinct group of tasks, you probably do not need three separate Customer Roles.
On the other hand, if the Finance Director must approve billing configuration and the COO must provide final launch approval, separate roles may make sense because each represents different project ownership.
A useful test is:
Would I assign a task in my template to this role?
If the answer is consistently no, you may not need the role.
Keep roles broad enough to reuse, but specific enough to assign work
Roles that are too broad make it difficult to tell who should do the work.
For example:
Too broad: Consultant
More useful: Implementation Consultant, Technical Consultant
Roles that are too specific create the opposite problem.
For example:
Too specific: West Coast Enterprise API Implementation Engineer Unless region, customer segment, and technical specialty all change how work is assigned in your standard process, Technical Consultant may be sufficient.
Start with the broadest role that still makes task ownership clear. Add more specialized roles only when your delivery process actually requires them.
Consider where responsibilities split during the customer journey
A new role is often useful when ownership changes at a meaningful point in your implementation.
For example, an implementation organization might use:
Implementation Manager → Technical Consultant → Training Specialist → Customer Success Manager
The Implementation Manager owns the overall project, while specialists own particular portions of the work.
That structure can make capacity planning more meaningful because the project reflects which types of resources are needed at different stages of delivery.
Example: SaaS implementation with data migration and SSO
Illustrative scenario.
A software company regularly runs implementations that require configuration, historical data migration, SSO setup, administrator training, and launch.
They create these internal Project Roles:
Implementation Manager
Implementation Consultant
Data Migration Specialist
Technical Consultant
Training Specialist
They create these Customer Roles:
Customer Project Lead
Data Owner
IT Lead
System Administrator
Executive Sponsor
Their template can then reflect the actual delivery model.
The Data Migration Specialist and Data Owner handle migration activities. The Technical Consultant and IT Lead work together on SSO. The Training Specialist works with the System Administrator on administrator readiness.
When a new project begins, the people may change, but the responsibilities remain familiar.
Review your role library periodically
Your role list should reflect how your team actually delivers projects today.
Periodically review your roles and ask:
Are there roles that no longer own any template tasks?
Are multiple roles essentially doing the same thing?
Are project managers frequently reassigning tasks because a role is too broad?
Has a new specialist become a repeatable part of your delivery process?
Do customers regularly ask what a Customer Role means?
If the answer is yes, simplify, rename, or expand your role structure.
A smaller, intentional role library is usually easier to maintain than creating a role for every possible participant.




