Team Management
Manage workspaces, invite team members, and configure workspace settings in ContextQA for organized test automation across teams.
Who is this for? Engineering Managers, IT Administrators, and VPs of Engineering configuring team access, authentication, and enterprise security controls.
ContextQA uses workspaces to organize testing projects. Each workspace is an isolated environment with its own test cases, environments, settings, and team members. This page covers how to create and manage workspaces, invite and manage users, and configure workspace-level settings.
Workspaces
What Is a Workspace
A workspace is the top-level organizational unit in ContextQA. Everything in ContextQA — test cases, test suites, test plans, environments, execution history, integrations, and user access — lives within a workspace.
Each workspace is completely isolated from others. Test cases in Workspace A are not visible from Workspace B. Users must be explicitly invited to each workspace they need access to.
Typical workspace patterns:
One workspace per product
Acme Web App, Acme Mobile, Acme API
One workspace per team
Frontend Team, Backend Team, QA Platform
One workspace per environment
Staging Tests, Production Monitoring
One workspace per client (agencies)
Client A, Client B
There is no fixed rule — organize workspaces in the way that matches your team's boundaries and access control requirements.
Creating a Workspace
Click the workspace selector dropdown in the top-left of the sidebar (it shows the current workspace name)
Click New Workspace (or + Create Workspace)
Enter a workspace name
Select the workspace type:
Web Application — browser-based UI testing
Mobile App — iOS and Android testing via device farm
API — REST API contract and integration testing
Salesforce — Salesforce-specific testing configuration
SAP — SAP testing configuration
Optionally add team members during setup by entering their email addresses
Click Create Workspace
After creation, you are switched to the new workspace automatically.
Switching Workspaces
Use the workspace selector dropdown in the top-left of the sidebar to switch between workspaces your account has access to. Click the dropdown, then click the workspace name you want to switch to.
If your account belongs to many workspaces, use the search field in the dropdown to filter by workspace name.
The workspace switcher feature requires a multi-workspace plan. If you do not see other workspaces in the dropdown, contact your workspace owner about plan access.
Workspace Settings
Navigate to Settings → Organization Settings to configure workspace-level settings:
General Settings
Organization name
Displayed in the workspace header and in shared report links
Default time zone
Used for scheduled test plan display and audit log timestamps
Default browser
Pre-selected browser when creating new test plans
Notification email
Fallback email for system notifications and scheduled test results
Test Execution Settings
Test case timeout
30
Maximum execution time, in minutes, allowed for a single test case before it times out. Accepts a value from 1 minute up to your organization's maximum. The maximum is configured by ContextQA and defaults to 160 minutes.
Retry failed steps
0
Number of times to automatically retry a failed step before marking it as failed. Set to 0 to disable retries.
Capture all step screenshots
Off
When enabled, captures a screenshot after every step — not only on failure. Useful for visual regression review but increases storage usage.
Video recording
Off
When enabled, records a video of the browser session during test execution. See Video & Screenshots.
The Organization Settings page groups these settings into tabs at the top — Company Information, Test Execution, AI Configuration, Notifications, and Viewport. Click Save Settings to apply your changes.
Company logo
Upload a company logo to brand your workspace. Once saved, the logo appears at the top of the sidebar in place of the default ContextQA mark. The logo lives on the Company Information tab of the Organization Settings page.
Supported formats and size
PNG or JPEG only. GIF is not supported.
Maximum file size: 2 MB.
A PNG with a transparent background is recommended, and a light or white version reads best against the sidebar.
Uploading a logo
Navigate to Settings → Organization Settings and open the Company Information tab.
In the logo upload box, either click Click to upload or drag and drop to pick a file, or drag an image file onto the box.
Wait for the upload to finish. The logo appears as a preview card showing a thumbnail, the file name, and its dimensions and size.
Click Save Settings to save the logo.
The preview is live: as soon as the upload completes, the sidebar shows your logo — you do not need to save to see it. The change is only persisted when you click Save Settings. If you leave the page without saving, the sidebar reverts to its previous logo.
When the sidebar is collapsed, branding is hidden and the logo does not appear.
Replacing or removing a logo
To replace the logo, click Replace on the preview card and select a new image.
To remove the logo, click Remove on the preview card. Click Save Settings to apply the removal — the sidebar then returns to the default ContextQA mark.
Default Viewport
The Viewport setting under Test Execution sets the default browser viewport for new test plans. Select a mode — Desktop, Laptop, Tablet, Mobile, or Custom — then choose a Resolution (or, for Custom, enter a width and height and click Add). If you don't select a desktop resolution, runs use the default of 1280×720.
Viewport configurations
The Viewport Configurations section — reachable from the Viewport tab on the Organization Settings page — lists the reusable viewports your organization has saved. Viewports are grouped by category: Mobile, Tablet, Laptop, and Desktop. Each viewport appears as a chip showing its label and dimensions, for example My Custom Desktop (1920×1080). If no viewports exist yet, the section shows "No viewport configurations found."
To remove a viewport, click the × on its chip.
Adding a viewport
Click Add Viewport to open the Add Viewport dialog.
Enter a Label — a descriptive name such as
My Custom Desktop.Enter the Width (px) and Height (px), for example
1920and1080.Review the Category chip. ContextQA assigns the category automatically from the width:
CategoryWidth rangeMobile
320–480 px
Tablet
481–1024 px
Laptop
1025–1600 px
Desktop
1601–3840 px
When the width is greater than the height, the chip also appends (Landscape).
Click Add Viewport to save.
Width is the primary classifier for the category. Boundary widths (480, 1024, and 1600) fall into the lower category — for example, a width of 1024 is classified as Tablet, not Laptop.
The dialog validates your entries as you type:
Width below 320px is rejected with "Below minimum supported width (320px)" — you can't save until you raise it.
Width above 3840px is allowed but flagged with "Exceeds standard display range (max 3840px)", and the category chip shows Custom / Unknown.
A height that's unusual for the derived category shows the warning "Unusual height for this category — double check". This is a reminder only; you can still save.
Saved viewports become available wherever ContextQA offers viewport or resolution choices, such as the default viewport selector in the viewport panel and cross-browser test machine configuration. See Cross-Browser Testing.
Organizations and sessions
A single ContextQA account can belong to more than one organization. Each organization is a separate tenant with its own subdomain (for example, acme.contextqa.com and globex.contextqa.com), its own workspaces, and its own data. You sign in to each organization independently, and your session in one organization is separate from your sessions in the others.
Switching organizations
Use the organization switcher to move between the organizations your account belongs to.
Click your profile avatar at the bottom of the sidebar. (You can also open the profile menu and select Switch Organization.)
The Switch Organization popover opens, showing your name and email at the top and the list of organizations your account belongs to.
The organization you are currently in shows an Active badge.
Click the organization you want to switch to.
ContextQA switches you to the selected organization and opens it on its own subdomain. You land back on the page you were viewing before the switch.
If you belong to only one organization, the switcher lists that single organization. Another organization can add you through that organization's user management, not from the switcher.
Signing out
You have two ways to end a session:
Sign out of the current organization — Open the profile menu and select Logout. This ends your session in the organization you are currently in. Your sessions in other organizations stay active.
Sign out of all organizations — In the Switch Organization popover, click Sign out of all organizations.
When you choose Sign out of all organizations, a confirmation dialog opens:
The Sign out of all organizations? dialog lists every organization your account belongs to, with the current organization marked Active.
Review the list, then click Sign out of all to confirm, or Cancel to keep your sessions.
Confirming ends your active sessions in all organizations at once. You must sign in again to access any of them.
Sign out of all organizations ends every session, including the one you are currently using. Use it on shared or public computers to make sure no organization stays signed in.
Managing Users
Viewing All Users
Navigate to Settings → User Management to see the organization user table. The current table shows Name, Email, Roles, Verified, and Admin, plus row actions. Use the search box to find a specific user.
Inviting Users
Navigate to Settings → User Management
Click + Invite User
Enter the user's Name and Email
Optionally enter a Phone Number
Select one or more Roles (see Roles & Permissions)
Click Save
If the role selector shows No roles available, create the required role on the Roles & Permissions tab before completing the invitation. Assign the least-privilege role that allows the person to do their job.
Authentication and password ownership
The current invite dialog does not ask the administrator to create a password. This separation prevents passwords from being copied into onboarding messages or shared by an administrator.
ContextQA-managed login behavior is controlled under Settings → Authentication Configuration.
With Google SSO, password policy and account recovery are owned by the configured identity provider.
Automation credentials belong in an approved secret manager, never in a user invitation or documentation screenshot.
See Authentication and SSO before changing a login method or handling the API credentials shown on the Authentication Configuration page.
Maintaining user access
Use the row actions next to a user to review the operations available in your deployment. Before changing or removing access:
Confirm the request and the target user's email address.
Record the user's existing role and any owned automation or scheduled tests.
Reassign business-critical ownership where required.
Apply the least disruptive access change exposed by the current user action menu.
Verify the result in the Verified, Admin, and Roles columns.
Review the corresponding entry under Settings → System Audits.
Available actions and their labels can vary by deployment. Do not assume that removing a user transfers their resources or preserves scheduled execution; validate ownership before making the change.
System Audit Log
Admins can review recorded platform activity at Settings → System Audits.
Audit Entry Fields
The current table exposes these fields:
Date: When ContextQA recorded the event
Module & ID: The affected application area and associated identifier
Details: The event description available for review
Using the Audit Log
For access reviews: Correlate user and role changes with an approved onboarding or offboarding request.
For change review: Use the refresh and filter controls to locate the relevant module, ID, or date when the deployment provides that filter.
For troubleshooting: Use the module and resource ID to connect an audit event to the affected test, integration, or configuration object.
The observed page does not expose actor IP addresses or a CSV export control. If those are compliance requirements, confirm deployment-specific availability and retention with the ContextQA account team instead of assuming they are enabled.
iOS Provisioning Profiles
For mobile testing on iOS devices, Apple code signing certificates (provisioning profiles) must be uploaded to ContextQA before running iOS tests.
Uploading a Provisioning Profile
Navigate to Settings → Provisioning Profiles
Click + Upload Profile
Upload the
.mobileprovisionfile downloaded from the Apple Developer PortalThe profile appears in the list with its expiration date
Profile Expiration
Provisioning profiles expire when the associated Apple Developer certificate expires — typically annually. ContextQA displays a warning when a profile is within 30 days of expiry.
Upload a renewed profile before the expiry date to avoid iOS test execution failures. The old profile can be deleted after the new one is active and verified.
Storage Configuration
Settings → Storage exposes provider cards for AWS S3 and Azure Cloud in the observed workspace. Use View Details to review a provider, and keep access keys or connection strings out of tickets, screenshots, and source control.
See System Configuration for the current screenshot and a safe configuration checklist.
Imports and Exports
The /settings/backups route is currently labeled Imports and Exports. It provides an Import action and lists available packages when they exist. In an empty workspace it displays There are no Backups created.
The observed page does not expose a scheduled daily/weekly backup configuration, retention period, or restore conflict policy. Treat an import as a controlled change: confirm the package source and target organization, record the pre-import state, and validate a small sample after processing. See System Configuration for the current screen.
Single Sign-On (SSO)
The observed Settings → Authentication Configuration page exposes No Auth, User Name and Password, and Google SSO. Identity-provider availability can vary by deployment or subscription.
Use Authentication and SSO for a screenshot-backed walkthrough, safe rollout sequence, and API credential handling. Confirm any required SAML or automated provisioning capability with the ContextQA account team when it is not displayed in the target deployment.
Enterprise-ready: SSO, RBAC, and centralized access management. Book an Enterprise Demo → — Get a walkthrough of enterprise controls, SSO setup, and compliance features for your organization.
Last updated
Was this helpful?