Each customer organization has a single user designated as the root administrator, representing the organization. However, an organization can have multiple users with non-root administrator role. As the business workload grows, the responsibilities of the root administrator also increase. To help manage this additional workload, the root administrator can create more non-root administrators.

• View/Update staffing organization details
• Add/Update/View/Deactivate/Reactivate organization non-root administrators
• Add/Update/View/Delete master data
• Add/Update/View/Deactivate/Reactivate/Delete regular employees and contractors
• Add/Update/View/Deactivate/Reactivate/Delete clients
• Add/Update/View/Deactivate/Reactivate/Delete client contracts
• Add/Update/View/Delete client projects
• Deploy resources in client projects, View deployment details
• Plan premature resource disengagement from the client projects
• Expire deployments in client projects
• View/Update client administrators
• Add/Update/View/Deactivate/Reactivate/Delete placement agents
• Add/Update/View/Deactivate/Reactivate/Delete placement agent contracts
• Deploy resources through placement agents, View deployment details
• Plan premature resource disengagement from placement agent deployments
• Expire placement agent deployments
• View/Update placement agent administrators
• Add/Update/View/Deactivate/Reactivate/Delete resource vendors
• Add/Update/View/Deactivate/Reactivate/Delete vendor contracts
• Add/Remove vendor resources in vendor contracts
• View/Update vendor administrators
• Add/Update/View/Delete internal projects
• Deploy resources in internal projects, View deployment details
• Plan premature resource disengagement from the internal projects
• Expire deployments in internal projects
• Task automation scheduling and control
• Timesheet generation
• Timesheet workflow (Timesheets pending submission, Timesheets rejected, Timesheets approved)
• Timesheet approval/rejection 
• Invoices generation
• Invoices payment workflow (Pending invoices, Paid invoices)
• Bills generation
• Bills payment workflow (Bills pending concurrence, Bills concurred, Bills paid)
• Unsubscribe
• Host Invoices

Organizations may have multiple clients. Each client has a single user designated as client administrator, representing the client organization.

• View client organization details
• View client projects details
• View client project resource deployments details
• View client contract details
• Timesheet approval/rejection for client project deployments
• Invoices workflow (Pending invoices, Paid invoices)
• Pay invoice

Organizations may have multiple placement agents. Each placement agent has a single user designated as placement agent administrator, representing the placement agent organization.

• View placement agent organization details
• View placement agent deployments details
• View placement agent contract details
• Timesheet approval/rejection for placement agent deployments
• Invoices workflow (Pending invoices, Paid invoices)
• Pay invoice

Organizations may have multiple vendors. Each vendor has a single user designated as vendor administrator, representing the vendor organization.

• View vendor organization details
• Add/View/Modify/Delete vendor resource
• Deactivate/Reactivate/Delete vendor resources
• View vendor contracts details
• Bills workflow (Bills pending concurrence, Bills concurred, bills paid)
• View Bills payment

Organizations may have multiple regular employees, i.e., employees on payroll. Regular employees are the resources exclusively owned by the organizations. Each regular employee has a user attached to the regular employee role.

“Employee Manager” is a variant of the “Regular Employee” role. Regular employees with “Employee Manager” role holds administrative significance compared to the users with “Regular Employee” role. While adding a regular employee to the resource pool, organization assign either the regular employee role or the employee manager role to the regular employee.

A regular employee with employee manager role can be assigned as a reporting authority for the other regular employees and other resources. This reporting hierarchy has significance in determining approvers dynamically for the internal project timesheets.

• View/Update regular employee details
• Timesheet workflow (Timesheets pending submission, Timesheets rejected, Timesheets approved)
• Timesheet approval (Timesheets pending approval, Timesheets approved)

Organization may engage multiple contractors. Each contractor has a user attached to the contractor role.

• View/Update contractor details
• View contractor contracts
• Timesheet workflow (Timesheets pending submission, Timesheets rejected, Timesheets approved)
• Timesheet approval (Timesheets pending approval, Timesheets approved)
• Bills workflow (Bills pending concurrence, Bills concurred, Bills paid))
• View Bills payment

Organizations may have multiple vendor resources from the vendors. Each vendor resource has a user attached to the vendor resource role.

• View/Update vendor resource details
• Timesheet workflow (Timesheets pending submission, Timesheets rejected, Timesheets approved)

There are certain actions which are role agnostic.

• Online registration. A staffing organization needs to provide organization information for getting registered as a customer/subscriber. After submitting organization information, organization awaits approval from the host. At this point no user for the organization created, no role is attached, and no login credential created for the organization. Upon host approval all these are created, and shared with the organization root administrator for logging into the system.
• Login. WFMA has a single user interface for login. Users puts in their login credentials in the Login user interface to get into the system.
• password change. Self-service portals for all the roles have this action in common.
• password reset. Self-service portals for all the roles have this action in common.