Skip to content
Documentation

Troubleshooting

Guides for authoring, running and analysing tests across web automation, API and performance — plus setup, collaboration and release notes.

Access & context

Bitassert is multi-tenant — everything is scoped to an organization and project, and access depends on accepted invitations and assigned roles. Most "missing" data or blocked actions trace back to context, invitations, or permissions.

AccessYour data or testcases "disappeared" after switching context

Testcases, datasets, and results are scoped to a specific organization and project. If something seems missing, you are almost always in the wrong org/project context. Switch to the correct one from the header before searching further.

AccessAn invited teammate can't see the project

Invitations must be accepted before access is granted, and access is limited to the org/project the invite was issued for. Ask the invitee to accept the pending invitation from their notifications, then confirm they are looking at the correct context.

AccessThe person I want to add isn’t in the project invite list

Project invitations choose from users who already belong to the organization (and aren’t yet in the project) — you can’t add an arbitrary email directly to a project. If someone isn’t listed, invite them to the organization first (org invites accept a new email address), then add them to the project.

AccessInvite won’t send: a role is required

Each invited user needs a role — an org role for organization invites, or a project role for project invites. If you also assign projects in an org invite, you must pick a project role too (that field stays disabled until you select at least one project). Provide the missing role and resend.

Access“Failed to invite user” with a specific message

The invitation was rejected and the message states why — commonly the user is already invited or already a member. Resolve what the message indicates (e.g. check pending invitations) and try again.

AccessAn action is hidden or blocked (insufficient role)

Some actions (creating run configs, setting a baseline, managing users) require a higher role. If a control is missing or disabled, you likely have read-only or limited permissions — ask an org/project admin to grant the needed role.

Still stuck?

See and , or contact us at bitassert.com/contact.