A practical setup guide for administrators and workplace users

This guide outlines recommended security practices when deploying Teamgo Visitor Management across your workplace. Following these steps helps ensure your system supports strong privacy protection, controlled access, and compliance with organisational policies such as ISO 27001-aligned security expectations and workplace safety obligations.

These recommendations apply whether you are deploying:

Administrators are responsible for configuring Teamgo securely before rollout to staff and visitors.

Where possible, connect Teamgo to your identity provider:

Recommended providers:

Benefits:

Administrator accounts should always use MFA.

This prevents access if:

Best practice:

Only assign permissions necessary for each user’s role.

Typical access structure:

Avoid granting full admin access broadly.

Access should follow your organisation’s lifecycle controls:

Joiner

Mover

Leaver

Tip 💡 If using SSO provisioning, this can be automated.

Teamgo allows administrators to define automatic record retention periods.

Recommended approach:

Benefits:

Administrators can customise consent wording displayed during sign-in.

Recommended inclusions:

This supports compliance with:

Kiosks should operate in controlled device mode.

Recommended configuration:

Optional advanced protection:

🔐 Deploy via Mobile Device Management (MDM) Examples:

If using visitor badge printing:

Ensure printers:

This prevents unauthorised print access.

Multi-site organisations should apply location-level permissions. Example:

Sydney staff
→ see Sydney records only

Melbourne staff
→ see Melbourne records only Benefits:

Schedule periodic reviews:

Recommended frequency:
📅 Every 3–6 months Check:

Always run the latest:

Benefits:

Everyday users play an important role in maintaining workplace security.

If not using SSO:

Each Teamgo user must have an individual account. Shared logins:

Always verify:

Especially important for:

Access only information required for your role. Do not:

When stepping away:

This prevents dashboard access by unauthorised persons.

Ensure your:

remain current for emergency alerts and visitor approvals.

Notify administrators if you notice:

Early reporting helps prevent incidents.

Organisations with higher compliance requirements should consider:

These controls are commonly used by:

You can copy or print this checklist for deployment teams.

☐ SSO configured
☐ MFA enabled for administrators
☐ Role-based permissions assigned
☐ Joiner / mover / leaver process defined
☐ Administrator access reviewed

☐ Data retention policy configured
☐ Privacy collection notice customised
☐ Export permissions reviewed
☐ Location-level access separation configured

☐ Guided Access / kiosk mode enabled
☐ OS updates installed
☐ App updated to latest version
☐ Device physically secured
☐ MDM applied (if available)

☐ Printer connected to secure network
☐ Printer not internet-exposed
☐ Static IP configured (optional best practice)

☐ Staff accounts individually assigned
☐ Staff trained on visitor approval process
☐ Emergency notification contacts verified
☐ Periodic admin review scheduled

☐ Quarterly permission review scheduled
☐ Device updates scheduled
☐ App updates monitored
☐ Retention policy validated annually

Get in touch with Teamgo if you would like to discuss this guide or require additional support and assistance.