What the product does.
WexaGate organizes visits, site-entry records and work permits. Its locally verified implementation includes scoped authorization, visitor capacity, bounded visit series and scheduled CSV reports.
Local synthetic workflows are verified. Customer, physical access-device and external integration acceptance remain separate.
Product capabilities
Prepare and follow a visit
Plan visitors and visit series, review site capacity and record QR check-in or check-out in the local application. Company, site and role scopes govern access.
- Visitor plans and bounded visit series
- QR check-in and check-out records
- Site visitor capacity
Keep permits and reports in scope
The local implementation includes work permits, private storage, audit records, retention and scheduled CSV reports. English and Turkish workflows and recipient-specific outputs have local verification.
- Work permits and scoped reporting
- Audit records and retention
- English and Turkish workflows
Evaluate the relevant tasks.
Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.
- Choose a sample site, visitor and host role.
- Review capacity, visit approval and QR entry or exit records.
- Inspect a work permit and the permitted report scope.
- Agree device responsibilities and customer acceptance before operational use.
Workflow walkthroughs
Walk through a site visit and permit
Describe visitor flow, permit owners, retention needs and any physical access equipment. Do not include identity documents or real visitor lists.
- Choose a sample site, visitor and host role.
- Review capacity, visit approval and QR entry or exit records.
- Inspect a work permit and the permitted report scope.
- Agree device responsibilities and customer acceptance before operational use.
Prepare a useful support request.
Include the exact WexaGate package or preview, environment and workflow. Confirm whether the issue concerns a local evaluation or an accepted customer installation.
- Describe visitor flow, permit owners, retention needs and any physical access equipment. Do not include identity documents or real visitor lists.
- Describe expected behaviour, what happened and any steps already tried. Do not send passwords, tokens, private files or production records.
- Remaining acceptance scope: Customer and production acceptance; Physical entry devices and site integration; External service and cross-product activation.
Your questions, answered.
Does QR check-in open a physical gate?
The documented local scope records application check-in and check-out. Physical access hardware needs its own integration and acceptance.
Can reports be limited to a site?
Scoped authorization and reports are part of the local implementation. Confirm your site roles and allowed output during evaluation.