Skip to content

An Overview of Users

← Administration: Users and Security

Before reading this you might want to read: 

Main Article


Worksoft SaaS Test Automation Platform supports two different types of users.
  •  Person that can login into Worksoft SaaS
  • Machine Running Tests

 Person Users

Users of this type can login into the Worksoft SaaS application. This type of user account is used for real people that require access to Worksoft SaaS to perform, at a high level, a subset (or all) of the following activities:

  • Creating and Administering Projects, Users, Integrations
  • Developing, Executing and Maintaining Automated Tests (including data that is utilized by those tests)
  • Accessing Reports and Analytics

A 'person user' can be granted one of two roles that are supported within Worksoft SaaS:

  • Administrative Person User Role: Users with this role can perform administrative functions like creating & administering projects and users, configuring integrations with external systems (like Identity management systems, Slack, Atlassian JIRA, etc.,), and accessing customer account level reports and analytics.

  •  Non-Administrative Person User Role: Users within this role have privileges to access one or more projects within a customer account to create and/or manage and/or execute (or simply view) the test automation, and to access the reports and analytics related to the test execution outcomes.

 Machine Users

Users of this type cannot log in into the Worksoft SaaS application. This type of user account is used for systems (aka machines) that will perform, at a high level, a subset (or all) of the following activities:

  • Schedule/Trigger the execution of automated tests hosted within the Worksoft SaaS Platform on a periodic basis, mostly unmanned
  • Upload test data feeding into the automated tests, mostly unmanned
  • Accessing and Downloading Reports and Analytics, mostly unmanned

Typically, machine user accounts are recommended to be created in Worksoft SaaS for the CI/CD (continuous delivery and continuous deployment) tools that build and deploy new application releases to specific environments and then schedule automated tests (unit tests, functional tests, regression tests, etc) to be executed to validate the new releases of the application. The automated tests hosted within the Worksoft SaaS platform can also be triggered by these CI/CD tools using the machine user account(s) created within Worksoft SaaS.

Each machine user account will have a private/secure access key that will be used to trigger tests using the QaCONNECT REST API (a wide range of powerful web services offered by the Worksoft SaaS test automation platform to its customers). To know more about QaCONNECT REST API, click here.

 Unlimited Users

There is no limit on the number of person users (employees, vendor consultants/contractors) and machine users that can be created within a Worksoft SaaS domain (aka customer account). To learn how to create and administer users within your Worksoft SaaS account, use the articles listed below.

Unlike other systems that charge a license fee per user (or seat), Worksoft SaaS gives unlimited access to your whole team, so you can all work together without the extra costs and distractions. At Worksoft SaaS, we know that our platform is also highly collaborative. It is dependent upon many different teams, skill sets, and decision makers. The person who develops your automated tests, may not be the same who executes it or maintains it over time. The person who defines or configures your test data is also probably different from the person who imports your data. And there is likely a whole set of people who simply need access to the test outcomes data without ever creating or maintaining the test automation. And that's why we don't charge per user.


After reading this you might want to read: 

Feedback and Knowledge Base

(thinking…)