Organization Management

Manage organization-level access, project-level overrides, and ownership transfer.

Organization-Level Management

TestKase uses a two-tier access model: organization-level and project-level. Understanding the distinction is important for managing your team effectively.

Organization-Level User Management

At the organization level, you manage the overall roster of users who belong to your TestKase organization. This is where you:

Invite new users to the organization and assign their initial role.
View all members across all projects in a single list.
Change a user's organization-wide role.
Remove users from the organization entirely, revoking access to all projects at once.
Manage pending invitations and resend or cancel them as needed.

Project-Level User Management

At the project level, you control which organization members have access to a specific project and can customize their permissions within that project. This is where you:

Grant or revoke project access for specific organization members.
Override default permissions for the User role within this project.
View the list of members who have access to this specific project.

A user must be a member of your organization before they can access any project. The organization-level role sets the baseline permissions, and the project-level configuration can further restrict them within the scope of that project. Only the User role is configurable, and only within the permissions that role already has — nothing at the project level grants a user more than their organization role allows.

For example, a user with the "User" role at the organization level might have delete permissions enabled in a sandbox project but disabled in a production testing project.

Organization-level management is open to both the Owner and organization Admins — they can invite users, change organization and project roles, and manage product access. Four things are owner-only: removing a member, managing billing, deleting the organization, and transferring ownership. Project-level permission configuration is accessible to the Owner, organization Admins and Project Admins.

Transfer Ownership

There may be situations where you need to transfer ownership of your TestKase organization to another user -- for example, when a team lead changes, when someone leaves the company, or during an organizational restructuring.

How to Transfer Organization Ownership

Navigate to Organization -> Settings. The page is owner-only.
Scroll down to the Danger zone and find Transfer ownership.
Select the recipient from the dropdown and click Transfer. Only existing organization Admins are eligible — a plain Member cannot receive ownership. If nobody in your organization is an Admin, the dialog says "No admins available. You need at least one admin in your organization to transfer ownership." Promote someone to Admin first.
Enter your current password. This is always required, not optional.
Once confirmed, the selected user becomes the new Owner, your organization role is changed to Admin, and you are logged out.

Important Considerations

Only the current Owner can initiate a transfer, and the recipient must already be an organization Admin. Promote them first — a Member cannot receive ownership.
The transfer is immediate, requires your password, and logs you out. Once you confirm, you lose Owner privileges instantly and cannot undo the action yourself.
Your role is downgraded to organization Admin automatically. The new Owner can subsequently change your role if needed.
All projects transfer, because they belong to the organization.

Billing does not move, because it never belonged to a person. Every subscription, invoice and seat count belongs to the organization. A transfer changes none of them — nothing needs re-purchasing and the plan keeps running without interruption — but it also means:

The saved payment method does not change. The payment authorisation that renews the subscription still charges the card the original purchaser authorised. The new Owner is never asked for a card, and nothing re-authorises the old one. If the outgoing owner is leaving the company, cancel the subscription and have the new Owner re-subscribe, or contact support.
There is no separate "billing contact" role. The organization Owner is the only role that can manage billing.
Past invoices do not follow either. Billing history is looked up by user account, so Organization → Billing will be empty for the new Owner — the organization's earlier invoices stay on the outgoing Owner's account. Download whatever your finance team needs before you transfer, or ask support for copies afterwards.

Ownership transfer cannot be undone by the previous Owner. Make sure you are transferring to the correct person. The new Owner will have full, unrestricted control over the organization, including the ability to remove any user -- including you.