Understanding credentials in PlaytestCloud playtests

What are credentials?

Credentials are access information that testers need to participate in your playtest. This includes Steam keys, usernames and passwords, access codes, or any other authentication details required for testers to access your game or application.

PlaytestCloud securely manages and distributes these credentials to testers at the appropriate time during the playtest process.

Types of credentials

Steam Keys (PC/Console)

Activation codes that allow testers to download and install your game from Steam.

How to order: Use the order form's "Add Steam keys" section

Learn more: How to order a playtest with Steam keys

Once your Steam playtest is live, you can:

Review which credentials were assigned to which testers
Add extra credentials—two to three times as many as the number of players you requested makes running your playtest a lot more feasible
Download detailed reports
Track credential usage

Learn more: Managing the credentials in your playtest

Usernames and Passwords

Test account credentials for games that require login authentication.

How to order: Add a special request at the bottom of the order form with the credentials or contact PlaytestCloud support during playtest setup
- Provide extra logins—two to three times as many makes running your playtest a lot more feasible
Use cases: Games with account systems, multiplayer games, games with cloud saves
Format: One set per line, separate username and password with a comma or tab:

username1,password1
username2,password2
username3,password3

Access Codes:

How to order: Add a special request at the bottom of the order form with the credentials or contact PlaytestCloud support during playtest setup
Use cases: Closed betas, early access programs, special event access
Format: One code per line:

ACCESS-CODE-123
ACCESS-CODE-456
ACCESS-CODE-789

Other Custom Credential Types

If you have other types of credentials that don't fit the standard formats above, we can likely accommodate them. Just reach out to us during playtest setup and we'll work with you to configure the appropriate credential system for your specific needs.

Credential format requirements

General Format Rules

One credential set per line - Each line represents one complete set of credentials for one tester
Consistent formatting - All lines must have the same number of fields
No extra spaces - Avoid spaces around separators (commas, tabs)
No empty lines - Don't include blank lines in your credential list

How credentials work

Automatic Assignment

Each tester receives a unique set of credentials
No two testers will use the same credential set
Credentials are assigned when testers join the playtest

Secure Distribution

Credentials are encrypted and stored securely
Access is controlled through the PlaytestCloud platform
All credential access is logged and tracked

Timing Control

The system automatically determines when to show credentials to testers based on the credential type and playtest configuration:

Steam keys: Shown on download instructions page and after recording starts
Other credentials: Timing configured by PlaytestCloud admins based on your requirements

Best practices

For Steam Keys

Upload more keys than number of players you're ordering—two to three times as many as the number of players you requested makes running your playtest a lot more feasible
Test your keys before uploading to ensure they work
Follow Steam's official documentation for generating keys

For Other Credential Types

Add more credentials than the number of players you're ordering—two to three times as many as the number of players you requested makes running your playtest a lot more feasible
Use dedicated test accounts rather than real user accounts
Provide clear instructions about how to use the credentials via the tasks if needed
Consider expiration dates or usage limitations
Test credentials before providing them to PlaytestCloud