Match access to the exercise
List the operations participants actually need, such as opening the approved tool, entering fictional text and viewing a result. Avoid requesting administrator permissions simply because they might be convenient. A fictional office team practising summaries may not need connections to live business systems at all. Keep optional demonstrations separate from mandatory hands-on requirements. The facilitator should know which steps depend on an account setting or organisational approval before the session, rather than discovering those dependencies while the group waits.
Confirm the approved account route
Tell participants which business-approved account and access method to use. Do not ask them to share passwords or put credentials into a training document. Record the person responsible for resolving access problems. If a participant has only a personal account, follow the decision of the organisation about whether it is suitable for the exercise instead of making an assumption. This guide does not prescribe a particular product or account plan. The goal is a clear authorised route that matches the prepared training material.
Test on the actual device
Ask participants to complete a short check using the device and network they expect to use during the workshop. The test can involve opening the tool and working with a fictional sentence. Record whether the required step works, not just whether the login page loads. If the session uses shared equipment or a meeting room, confirm the arrangements separately. A facilitator demonstration from another device does not establish that every participant can perform the exercise. Keep the check bounded and avoid introducing live data merely to test access.
Confirm practice permissions and material
Make clear which information participants may use and which actions remain outside scope. Use the approved fictional examples rather than inviting people to paste arbitrary work documents. If an exercise needs file input, verify that specific permitted action with the prepared file. Do not widen permissions to fix an unexplained problem without identifying the requirement. Keep sending, publishing and production changes outside the training task unless separately authorised. Access to a button should not be interpreted as permission to use it on behalf of the business.
Prepare a fallback that preserves learning
If access remains unavailable, give the participant a way to review a prepared example, work through the task with an authorised partner or follow a facilitator-led exercise. Explain which practical step they could not perform so attendance is not reported as completed hands-on work. Avoid a last-minute installation or account purchase merely to keep the agenda moving. The training owner can decide the appropriate next step. A useful fallback should keep the participant engaged with the task and review criteria while respecting the unresolved access boundary.
Close access issues after the session
Record unresolved access problems, owners and the follow-up required. Distinguish technical access from confidence using the tool: someone may have logged in successfully but still need guided practice. Remove temporary arrangements through the approved process where appropriate and keep the ordinary support route clear. Do not report that the team is ready for routine workplace use solely because the workshop exercise ran. Any ongoing use should follow the approved scope of the organisation, material-handling rules and human review expectations.