Account access
Signed-in workspace access
Assessment workspaces use account sign-in. Participants should use their own account and keep invitations and access details private.
Access / Trust & information
Security & privacy
Device permissions.
Assessment data.
Read about device checks, assessment controls, and the information used during a round.
The assessment workflow
Assessment controls
and their purpose.
Access supports a structured round. Its controls and review signals should be understood alongside your organizer’s instructions.
Device preparation
Readiness before entry
Candidates can check their device and required permissions before a round. Entry checks depend on the assessment configuration.
During the round
A controlled assessment session
The desktop app records device, focus, connection and presence events for assessment review. Session events are queued on the device and sent to the assessment service.
Review process
Context for a human decision
Reviewers can consider submissions alongside available session activity and reported issues. An activity flag alone is not proof of misconduct.
The exact setup depends on the round and device. These controls do not guarantee uninterrupted access or prevent every prohibited action.
Information used by Access
What you share
depends on what you do.
Visiting the website, contacting the team, and taking an assessment involve different information.
What Access checks and records- When you contact Access
- The details and message you provide help the team understand and respond to your enquiry.
- When you take a round
- Readiness reports are sent before entry. Submitted work and timestamped activity, including focus, connection and presence events, support participation and review.
- When media is required
- Calibration images stay local in the reviewed flow. Separate presence-check stills can be sent with session events. Microphone permission is distinct from audio recording.
- When you need help
- Incident descriptions and diagnostic information help investigate the problem you report.
For candidates and organizers
Agree on the details.
Before assessment day.
Your round’s notice and instructions should make these questions easy to answer.
- Which device checks and permissions are required?
- What information or media is collected, and for what purpose?
- Who can review the work, results, and session activity?
- How long are records kept, and how can a request be made?
- Who handles technical issues and questions about a result?
Common questions
Permissions and privacy questions
Start here for common questions about participation, permissions, and privacy.
Does browsing this website use my camera?
No. The marketing website does not request camera or microphone access. The desktop app has separate permission and readiness steps for assessments.
Can camera images leave my device?
Camera checks support device setup and face presence during a session. Local calibration images are separate from session images: when a presence check finds no face or more than one face, a still image can be included in the activity sent to the assessment service.
Does microphone access mean audio is recorded?
The app requests microphone access during setup and when opening the live session media stream. Permission to use a microphone is not, by itself, evidence that audio is recorded or stored. The reviewed 2.3.1 flow does not include continuous audio or video recording.
Does an activity flag decide my result?
An activity flag is a signal for review, not proof of misconduct on its own. Code evaluation and entry checks can produce automated outcomes; your organizer should explain the assessment and review process.
Can I take part if a permission is unavailable?
A required permission may prevent entry or affect participation. Speak to your organizer before the round about your device or any alternative arrangement you need.
Who should I contact about my assessment data?
Start with the organizer that invited you for assessment records, results, and round-specific privacy questions. Contact Access if your question concerns the website, an enquiry, or you are unsure where to direct it.
Raise a concern
Found a security issue?
Email the AMS team about the security concern. Describe the affected feature, what you observed, and when it happened.
team@amshq.inKeep passwords, invitation codes, and other people’s information out of an initial message. Only test systems you are authorized to test.