Manage vendor sandboxes and tester access

The sandbox panel records the test environment offered by one project vendor and the people expected to use it. It is an inventory and coordination surface, not a password vault. Keep the environment URL, ownership, availability and tester assignments current, while exchanging credentials through your organisation’s approved secure channel.

Before you start

• Agree the testing window, supported use cases and who owns environment support on both sides.

• Create or identify the stakeholders who will test, and choose an approved method for delivering credentials separately.

Step by step

1. Open the vendor sandbox panel

From the project Vendors list, open the vendor detail and locate Sandbox or test environment. Each vendor’s environment and access list are independent.

2. Record the environment

Add the environment URL, supported ownership or status fields and useful non-secret access guidance. Update availability when the vendor provisions, pauses or retires the environment.

3. Add named testers

Assign the internal members or stakeholders who need to test this vendor. Give each person their own access where the vendor supports it instead of sharing an account.

4. Connect structured use cases

Send stakeholder use-case testing through the Stakeholder workflow when responses must be scored. Use sandbox notes for logistics, not as a replacement for the questionnaire.

5. Monitor access and evidence

Check that testers can reach the environment, resolve vendor support issues and chase outstanding scorecards. Record material findings in the appropriate response or meeting record.

6. Close access at the end

Remove testers or mark access inactive when testing finishes. Ask the vendor to revoke temporary accounts and retain only the evidence required by policy.

What happens next

• Compare sandbox results with demo, RFI and proposal evidence before a decision.

• Run a later testing round when the environment or use cases materially change, preserving the earlier evidence.

Troubleshooting

A tester cannot open the environment

Confirm the URL and sandbox status, then ask the vendor owner to check that person’s named account. Do not publish credentials in project notes.

A tester is not selectable

Add them to the project or stakeholder directory as required, and confirm they are active in the current workspace.

Sandbox findings do not affect comparison

Ensure the tester submitted the assigned stakeholder or sandbox scorecard and that the corresponding project stream has weight.

Related guides