Named Support Contacts (NSCs) are employees of your organization who have been identified by the Named Support Contact Admin (NSCA) to support specific product lines. 

• NSCs are identified during the deployment or production phase.
• There's a limited number based on the number of employees and your subscription with Workday.

Responsibilities:

• Create cases and collaborate with Workday Support depending on your product assignment.

Named Support Contact Read-Only (NSCRO) is a role that the NSCA can designate to have read-only access to cases within specific product lines.

• NSCROs are identified during the deployment or production phase.
• There's no limit on the number of NSCROs.
• NSCROs have access to view and follow case comments.
• NSCROs can be added to Case team.

The Training Coordinator (TC)  is the point of contact within your organization who manages training. 

• TCs are identified during the deployment phase.
• Each organization is limited to 2 training coordinators.

Responsibilities:

• Workday Learning Center accounts.
• Training plans and budgets.
• Training enrollments (approve, assign, decline).
• Training subscriptions.
• Training cases.

A Security Lead (SL) is a primary point of contact for security communications between Workday and your organization.

• Identified during the deployment or production phase
• A minimum of one Security Lead should be assigned.

Responsibilities:

• Work closely with an NSC if case updates are required in Workday Community.
• Represent the customer's organizational security plans and policies.
• Act as the point of contact for any high profile security events.
• Coordinate internal resources to organize any necessary countermeasures in your IT infrastructure or within your Workday tenant.

Community Organization Administrators manage access to Workday Community for your organization.

• Community Organization Administrators are identified during the deployment phase.
• There's no limit on the number of Community Organization Administrators.

Responsibilities:

• Approve or deny Workday Community memberships.
• Manage user access to Workday Community.

The Developer Support Contact (DSC) role is to log support cases within the Workday Extend developer site.

• DSCs are identified during the deployment of Workday Extend.
• Each organization is limited to 3 DSCs.

Responsibilities:

• Assign collaborators as DSCs, but not as administrators.
• Submit and manage Workday Extend cases using the Support section of the Developer Site.
• View and update existing cases within the Workday Extend Developer site.

Account Team members are consultants who can create cases on behalf of your organization. Consultants assigned to the Account Team for a customer use the Workday Partner Center (partner consultants) or Enterprise Center (Workday consultants) to create, view, and maintain all cases.

• Account team members are identified during the deployment phase.
• The number of team members varies based on the size of your deployment.
• Individuals must be certified on Workday.
• The team consists of:
  •  Either an Engagement Manager (Workday primed) or Partner Project Manager
  • Functional consultants
  • Integration lead
  • Integration consultants
  • Integration analysts
  • Data conversion consultant
  • The delivery assurance team

Responsibilities:

• Work with customers to ensure a successful Workday deployment.
• Create, update, and view cases.

Authorized to approve tenant purchase agreements, and manage accounts payable activity and billing contract management.

• Billing contacts are identified during the Self-Service Tenant Purchase.
• There's no limit on the number of contacts.
• Billing contacts are added to case teams and receive email notifications about case comments.