"Why can't I see this option?"
When a button, menu, or setting seems to be missing in ContextQA, it's almost always one of three reasons:
Permissions — access in ContextQA is controlled by a per-user Admin toggle plus custom roles that your workspace defines. Each role grants specific permissions — view/create/update/delete across Users, Workspaces, Tests, Roles, and Plugins. If your role doesn't include a permission, the related option is hidden or unavailable.
Plan gating — the feature isn't included in your organisation's plan. If an option appears greyed out or absent and you have Admin access, ask your account owner about the plan.
Wrong location — some controls only appear in specific places (for example, the Execution Environment picker only appears in the run confirmation dialog).
If you believe you should have access and don't, contact your workspace Admin first — they can adjust your role or permissions.
How roles work in ContextQA
Unlike tools with fixed role names, ContextQA roles are created by your workspace, so the role names you see (for example "QA") are specific to your organisation. Admins manage them under Settings → User Management → Roles & Permissions, where each role lists exactly which permissions it grants. Separately, each user has an Admin toggle on the Users tab — Admins can manage users, roles, and workspace settings regardless of role.
To check your own access: if you can open Settings → User Management, you have admin-level access and can see everyone's roles there. If you can't, ask a workspace Admin what role you've been assigned and what it includes.
Who can add users and change roles
Workspace Admins, from Settings → User Management: the Users tab to invite users (Invite user) and grant or remove Admin status, and the Roles & Permissions tab to create or edit roles. If you need a colleague added or your own permissions changed, ask any Admin in your workspace.
Trouble logging in
If you can't sign in to your workspace:
Check the workspace URL — each organisation has its own subdomain (e.g.
yourcompany.contextqa.com). Logging in at the wrong subdomain will fail even with correct credentials.Reset your password using the link on the login page, and check spam for the reset email.
Confirm your account is active and verified — if an Admin removed or deactivated your account, or your email was never verified, login will fail; ask your workspace Admin to check User Management.
Try a fresh session — log out everywhere, clear the browser cache or use a private window, and try again.
If none of that works, contact support with your workspace URL, the email you're signing in with, and the exact error message or a screenshot — that's a problem on our side to investigate, not yours.
Locked out and can't open the in-app messenger?
The help messenger lives inside the product, so if you can't log in you can't use it. Email support directly instead, or ask a logged-in teammate to raise it for you, including the workspace URL and the time the problem started.