Project Scopes
Overview
A project scope is a named tag you attach to resources (such as test cases, automation objects, systems under test, folders, and schedules) so that access to those resources can be partitioned by tenant, business area, or project — for example FINANCE_PROJECT or HR_DEV. A scope on its own grants nothing; it only becomes meaningful once a role assigns a permission group on that scope to a user.
This page is where administrators manage the catalogue of available scopes. You can browse every scope defined in the system, search by name, open a scope to rename it, or create a new one. Scopes you create here immediately become available everywhere else: when tagging a resource, and when configuring a role to grant a permission group on a specific scope.
Two rules are worth knowing before you start. First, scopes are matched exactly when permissions are evaluated — a resource tagged with no scope is only reachable by grants that also have no scope, and a resource tagged FINANCE_PROJECT is only reachable by grants on FINANCE_PROJECT. Null scope is not a wildcard. Second, deleting a scope is blocked while resources (such as test cases or systems under test) are still tagged with it; you must remove or retag those first. Role grants on the scope do not block deletion — they are removed automatically together with the scope.
Tasks
How to create a project scope
- Click Create New in the toolbar.
- You are taken to the scope creation form. Fill in the name and save it there.
- The new scope appears in this list once saved. It can immediately be selected when tagging resources or configuring roles.
The Create New button is only enabled if you have permission to create project scopes — see Prerequisites & permissions.
Field reference
| Column | Description |
|---|---|
| Name | The unique name of the scope. Acts as the link to open the scope's detail page. Names must be unique across the system. |
| Created By | The user who originally created this scope. Read-only. |
| Created At | When this scope was first created. Displayed as a relative time (for example, "3 days ago"); hover to see the exact timestamp. |
| Updated At | When this scope was last modified. Displayed as a relative time. |
Tips & edge cases
- Scopes are global. The list is not itself filtered by scope — every scope defined in the system is visible to every authenticated user, because scope names are needed to fill value-help pickers elsewhere. Sensitive scope names (e.g. customer-identifying ones) should be chosen with this in mind.
- A scope on its own grants nothing. Creating a scope here does not give anyone access to anything. Permissions only take effect when a role grants a permission group on that scope and a user is assigned that role.
- Null scope is not a wildcard. A permission row with no scope only matches resources that themselves have no scope. To grant access on every scope, a role must explicitly link a permission group on each one (or on null, separately).
- Deletion can be blocked. If you delete a scope from its detail page while resources (for instance, test cases or systems under test) are still tagged with it, the deletion is rejected. Remove or retag those resources first, then delete. Role grants on the scope do not block deletion — they are removed automatically along with the scope.
- The empty list message (No project scopes found) appears when no scope matches your search or none have been created yet. A separate error message (Failed to load project scopes) is shown if the list cannot be loaded.
Related features
- Project scope detail / create / edit
- Roles
- Permission groups
- Users
Prerequisites & permissions
About permissions. Int4 Suite controls what you can see and do through roles and permission groups assigned to your user. Each role grants permissions on a specific resource (for example, Test Case, Automation Object, System Under Test) at one of four levels: Read, Write, Delete, or Execute. Some permissions are further narrowed by project scope, so you may have access to one part of the system but not another.
If a button is disabled or a list comes back empty, missing permissions are the most likely cause. Ask an administrator to review your role assignments, or check IAM → Users if you have the User: Read permission.
To use this page:
- View the list: you need the Project Scope: Read permission. Without it, the page is hidden from navigation or returns an access error.
- Create a new scope: you additionally need the Project Scope: Write permission. Without it, the Create New button is disabled.
- Edit or delete a scope: managed from the scope's detail page; see Related features for the required permissions there.
Project scopes are themselves unscoped resources — they are managed globally, not per scope.