---
title: "How do I control who can do what, and see who changed what?"
section: "Use cases"
description: "Access control and audit trail in SmartestQA: the Admin and User roles, project access per user, Active Directory sign-in with group mapping, and an audit log of every change with user, source and result, exportable as CSV."
url: https://docs.smartestqa.ai/en/use-case-access-audit.html
audience: [customer, admin]
updated: 2026-11-12
keywords: "access control roles permissions admin user project access rbac active directory ldap sign-in group mapping deactivate user audit log audit trail who changed what who deleted test case denied attempts export csv compliance mcp changes shared login test tool shared account who changed the test change log in a shared document offboarding leaver access"
---
# Use cases: How do I control who can do what, and see who changed what?

In SmartestQA an Admin sets each person's role (Admin or User) and project access in Configuration › Company Settings › Users, or lets Active Directory groups decide both at every sign-in. Configuration › Logs › Audit logs then records every change, sign-in and denied attempt with the user, the time, the source and the result, and exports it as CSV.

## In short

**On this page you can**

- Give people the ADMIN or USER role and only the projects they work on.
- Deactivate a leaver: their open sessions end at once and their history stays.
- Let people sign in with Active Directory and take role and projects from AD groups.
- Find who created, changed, deleted, ran or stopped something, and from which source.
- Export the audit log as CSV, up to 50,000 records per file.

**How to use it**

1. Open Configuration › Company Settings › Users and click New User .
2. Pick the User Role , then assign projects with the + in the Projects column.
3. For directory sign-in, map AD groups to roles and projects in Active Directory .
4. Open Configuration › Logs › Audit logs and filter by date, area and action.
5. Click Export CSV to hand the records to an auditor.

## The short answer

Access has two parts. The role decides what a person can do: **Admin** or **User**. Roles are fixed. Project access decides where: a User opens only the projects assigned to them, an Admin sees all projects. An Admin sets both in **Configuration** › [**Company Settings**](https://docs.smartestqa.ai/en/company-settings.html) › **Users**. With [**Active Directory**](https://docs.smartestqa.ai/en/company-settings-active-directory.html), role and projects come from AD groups on every sign-in.

The audit log answers the second question. **Configuration** › [**Logs**](https://docs.smartestqa.ai/en/logs.html) › [**Audit logs**](https://docs.smartestqa.ai/en/logs-audit-log.html) records every request that changes something, every sign-in and sign-out, and denied and failed attempts too. Each record names the user, the time, the action, the record it touched, the result and the source: the app, an AI assistant through MCP, or an API key. Records cannot be edited or deleted and are never removed automatically.

## The problem this solves

A test tool holds things that matter: test data, sign-in details for test environments, schedules that run against shared systems. In many teams people share one or two logins, or every account has full rights, because finer access takes effort to set up. When someone leaves, the shared password often stays the same.

Then something changes: a test case is gone, or a pipeline runs at another hour. With shared accounts nobody can say who did it. Some teams keep a change list in a shared document, which holds only what people remember to write down. An auditor usually asks for more than that.

## An example

This is an illustration, not a customer story. An insurer’s test team works on an online claim form; the QA lead is an Admin in SmartestQA.

1. A new tester joins. The QA lead clicks [**New User**](https://docs.smartestqa.ai/en/company-settings-users.html#add-user), picks the [**User Role**](https://docs.smartestqa.ai/en/company-settings-users.html#add-user) USER and clicks **Create**: “A password setup link has been sent to:” and the address.
2. The new tester sees “No Project Access” until the QA lead clicks the **+** in the **Projects** column, ticks **Assign** for the claims project and clicks **Save**: “Project permissions updated.”
3. A contractor’s last day is Friday. The QA lead unticks **Active** and clicks **Save Changes**. The contractor cannot sign in, their open sessions end at once, and their test cases, runs and history stay.
4. On Monday a regression test case is missing. In [**Audit logs**](https://docs.smartestqa.ai/en/logs-audit-log.html) the QA lead sets **From** and **To** to last week, **Area** to Test case and **Action** to Deleted, and types part of the name. The row shows who did it, when, from which source, and whether it went through.
5. The QA lead then sets **Result** = Denied and sees the requests that were refused because of the person’s role.
6. Before the yearly audit the QA lead filters the year by date and clicks **Export CSV**. The file holds the newest records first, up to 50,000.

Each change now has a name and a time next to it, and the auditor gets a file where the team used to give an explanation.

## With shared accounts, with a change list in a shared document, and with SmartestQA

| Question | Shared accounts | A change list in a shared document | SmartestQA |
| --- | --- | --- | --- |
| Who can sign in? | Anyone who knows the password | The list does not control access | Each person with their own account and the role Admin or User, or through Active Directory |
| Can a person be limited to some projects? | No | No | A User opens only the projects assigned to them; an Admin sees all. There is no read-only project access |
| What happens when someone leaves? | The password has to be changed and passed on to everyone else | Nothing | Untick **Active**: the user cannot sign in, open sessions end at once, and their work stays |
| Who changed or deleted something? | The users of one account cannot be told apart | Known only if the person wrote it down | The audit log records every request that changes something, with the user, the time, the action, the record, the result and the source |
| Can the record be altered? | There is no record | Yes, by anyone who can edit the document | Records cannot be edited or deleted from the app, by admins either |
| Does it show who only looked at something? | No | No | No. Opening, reading and searching are not recorded |
| What do you hand to an auditor? | An explanation | The document | A CSV from **Export CSV**, up to 50,000 records per file |

## Steps

1. **Add the user**

   In **Configuration** › [**Company Settings**](https://docs.smartestqa.ai/en/company-settings.html) › **Users**, click [**New User**](https://docs.smartestqa.ai/en/company-settings-users.html#add-user). Fill **First Name**, **Last Name**, **E-mail** and [**User Role**](https://docs.smartestqa.ai/en/company-settings-users.html#add-user), then click **Create**. The e-mail must be a corporate address.

   “A password setup link has been sent to:” and the address. The user appears in the table.
2. **Give project access**

   A new User sees no project until you assign one. Click the **+** in the user’s **Projects** column, tick **Assign** for each project and click **Save**.

   “Project permissions updated.”
3. **Change a role when the job changes**

   Choose **ADMIN** or **USER** in the row’s **Role** list and click **Save Changes** above the table.

   “Users updated successfully”.
4. **Deactivate leavers**

   Untick **Active** and click **Save Changes**. The user cannot sign in, all their open sessions end at once, and their test cases, runs and history stay.
5. **Optional: let Active Directory decide**

   In [**Company Settings**](https://docs.smartestqa.ai/en/company-settings.html) › [**Active Directory**](https://docs.smartestqa.ai/en/company-settings-active-directory.html), enter the connection, add one row per **AD group** with its **Role** and **Projects**, check a person with [**Test a user**](https://docs.smartestqa.ai/en/company-settings-active-directory.html#test-user), and switch on [**Allow sign-in with Active Directory**](https://docs.smartestqa.ai/en/company-settings-active-directory.html#connection). Accounts are created on first sign-in.
6. **Find who changed something**

   Open **Configuration** › [**Logs**](https://docs.smartestqa.ai/en/logs.html) › [**Audit logs**](https://docs.smartestqa.ai/en/logs-audit-log.html). Pick **From** and **To** around the moment it changed, set **Area** and **Action**, for example Test case and Deleted, and type part of the name in the search.

   The row shows who did it, when, from which source, and whether it went through.
7. **Review refused attempts and AI changes**

   Set **Result** = Denied to see requests that were refused because of the person’s role or company. Set **Source** = MCP (Claude) to see what an AI assistant applied under a person’s name.
8. **Export for an auditor**

   Set the filters and click **Export CSV**. The export contains exactly what the filters and the search show.

   A CSV file downloads with the newest records first, up to 50,000.

## What Admin and User can do

| Item | Admin | User |
| --- | --- | --- |
| Create and edit test cases, steps, requirements, actions and API requests | Can | Can |
| Run test cases and pipelines; set up pipelines and schedules | Can | Can |
| Approve in Maintain (auto-heal, AI step and network conversions) | Can | Can |
| See projects | Can (all) | Limited: only the projects they are a member of |
| Create, edit and delete projects; add people to projects | Can | Cannot |
| Archive or bring back other people’s work; delete permanently | Can | Cannot |
| Add users, change their role and projects | Can | Cannot |
| Integrations, task statuses, company profile and licence | Can | Cannot |
| See the audit log | Can | Cannot |
| Delete users, set their password | Cannot (SmartestQA only) | Cannot |

For the User role, **Configuration** › Project Panel, [**Company Settings**](https://docs.smartestqa.ai/en/company-settings.html), **Integrations** and Logs are greyed out with “Please contact your administrator to access this feature.” A third role, Super Admin, is SmartestQA’s operator role and cannot be given by an admin or by Active Directory.

## What the audit log records

| Field | Values |
| --- | --- |
| **Time** | Local date and time, to the minute. |
| **User** | Who made the request, with the source below: App, MCP (Claude), API key or Not signed in. |
| **Action** | Created, Updated, Deleted, Archived, Restored, Ran, Stopped, Imported, Exported, Signed in, Signed out, Other, with the area below it, for example Test case, Pipeline, Project settings or User. |
| **Record** | The name of the record, or `#id` when it has no name, with its project below. |
| **Result** | Done, Denied (no permission) or Failed (error). |
| Details of a row | The request (HTTP method and path), status and duration, the error message for failed or denied requests, the client and a request ID to quote to support. |
| Sent fields | A summary of the request: at most 30 top-level fields, texts cut at 200 characters. Field names that look secret show `***`. |

Not recorded: opening, reading, searching and previews; machine traffic such as agent heartbeats and run logs; AI chat questions. For screens that can hold secrets, such as sign-in, users, data sources and integrations, the record is kept but its field values are not.

## What you get

- **Two fixed roles for your team.** Users can do all test work in their projects; Admins also manage people, projects, settings and integrations.
- **Access per project.** A User with no project sees “No Project Access”. Access is all or nothing: there is no read-only project access.
- **A protected last admin.** The last active admin cannot be demoted or deactivated, and nobody can change their own role.
- **Directory sign-in.** People use their Active Directory password over `ldaps://`. If several mapped groups match, the most privileged role wins and the projects are combined. Access granted by a group is removed when the user leaves the group.
- **Protection against password guessing.** 5 wrong passwords for one sign-in name, or 30 from one network address, in 15 minutes pause AD sign-ins for it.
- **A log that cannot be changed.** Audit records cannot be edited or deleted from the app, by admins either, and are never removed automatically.
- **AI changes under a name.** A change made by an AI assistant through MCP is recorded with the source MCP (Claude) and the name of the person whose connection it used.

## Questions and answers

### Q: Which roles does SmartestQA have?

Two for your team: Admin and User. Roles are fixed, so you cannot define your own. Super Admin is SmartestQA’s operator role and cannot be given by an admin or by Active Directory. See [What each role can do](https://docs.smartestqa.ai/en/company-settings-roles.html#matrix).

_Audience: customer, admin_

### Q: Can I limit a user to certain projects?

Yes. A User opens only the projects ticked in [**Assign Projects**](https://docs.smartestqa.ai/en/company-settings-users.html#project-access), which an Admin opens with the **+** in the **Projects** column. Admins always see every project of the company. See [Give project access](https://docs.smartestqa.ai/en/company-settings-users.html#project-access).

_Audience: customer, admin_

### Q: Is there a read-only role or read-only project access?

No. Project access is all or nothing, and a User can create, edit and run tests in every project they are a member of. What a User cannot do is listed in the role matrix. See [What each role can do](https://docs.smartestqa.ai/en/company-settings-roles.html#matrix).

_Audience: customer, admin_

### Q: What happens when I deactivate a user?

The user cannot sign in and all their open sessions end at once. Their own agent host is removed and shows offline. Their test cases, runs and history stay; nothing is deleted. Deleting users is done by SmartestQA only. See [Deactivate or reactivate a user](https://docs.smartestqa.ai/en/company-settings-users.html#deactivate).

_Audience: customer, admin_

### Q: Can people sign in with their Active Directory account?

Yes. With [**Allow sign-in with Active Directory**](https://docs.smartestqa.ai/en/company-settings-active-directory.html#connection) on, people sign in on the normal SmartestQA sign-in page with their AD user name and AD password. You need a service account that can read users and groups, and domain controllers reachable on `ldaps://` (port 636). See [Before you start](https://docs.smartestqa.ai/en/company-settings-active-directory.html#before-you-start).

_Audience: customer, admin_

### Q: How do Active Directory groups become roles and projects?

You map each AD group to a role and a list of projects. At every AD sign-in, the user gets the most privileged role among their matching groups and all projects of those groups, plus projects an admin assigned by hand. If no group matches, [**Role when no group matches**](https://docs.smartestqa.ai/en/company-settings-active-directory.html#groups) applies; its default is **Do not allow sign-in**. See [Groups and roles](https://docs.smartestqa.ai/en/company-settings-active-directory.html#groups).

_Audience: customer, admin_

### Q: How do I find out who deleted or changed a test case?

In **Configuration** › [**Logs**](https://docs.smartestqa.ai/en/logs.html) › [**Audit logs**](https://docs.smartestqa.ai/en/logs-audit-log.html), set the date range, **Area** = Test case and **Action** = Deleted, and search the name. For one test case, its **History** in Automate shows the same records without filtering. See [Find who changed something](https://docs.smartestqa.ai/en/logs-audit-log.html#find-who).

_Audience: customer, admin_

### Q: Can I see who viewed a report or a test case?

No. Reading is not recorded. The audit log holds changes, sign-ins and sign-outs, including denied and failed attempts. See [What is and is not recorded](https://docs.smartestqa.ai/en/logs-audit-log.html#what-is-recorded).

_Audience: customer, admin_

### Q: How long are audit records kept, and can anyone delete them?

They are never removed automatically. They cannot be edited or deleted from the app, by admins either. See [How long are audit records kept?](https://docs.smartestqa.ai/en/logs-faq.html#faq-retention)

_Audience: customer, admin_

### Q: What do I give an auditor who wants proof of who changed what?

A CSV per period from **Export CSV**, filtered by date and by project if needed. One file holds up to 50,000 records, newest first; for more, export in several date ranges. Denied attempts are included and secrets are masked. See [Export as CSV](https://docs.smartestqa.ai/en/logs-audit-log.html#export).

_Audience: customer, admin_

## Read more

- [Company Settings](https://docs.smartestqa.ai/en/company-settings.html): all sections and who can open them.
- [Users](https://docs.smartestqa.ai/en/company-settings-users.html): add, change role, deactivate, project access.
- [Roles & permissions](https://docs.smartestqa.ai/en/company-settings-roles.html): the full matrix and how to choose roles.
- [Active Directory](https://docs.smartestqa.ai/en/company-settings-active-directory.html): connection, group mapping, [Test a user](https://docs.smartestqa.ai/en/company-settings-active-directory.html#test-user) and [how sign-in works](https://docs.smartestqa.ai/en/company-settings-active-directory.html#sign-in).
- [Logs](https://docs.smartestqa.ai/en/logs.html): what the audit log is for and where it fits.
- [Audit log](https://docs.smartestqa.ai/en/logs-audit-log.html): filters, the record details and the CSV export.
- [Safe changes through MCP](https://docs.smartestqa.ai/en/mcp-safe-changes.html): how an AI assistant’s changes are approved and traced.
