When no Jira groups are selected for a Vansah permission, Vansah uses the user’s Jira permissions for that action. An empty group selection does not block access to the function.
Use this guide to understand the default checks and decide whether you need to restrict an action to specific Jira groups. Users still need access to the Jira space and the relevant Vansah feature.
How access is checked
Permission setting | How Vansah checks access |
No Jira groups selected | Vansah uses the default Jira permission for the action. For supported actions, the item’s creator can also retain access. |
One or more Jira groups selected | The user must belong to at least one selected group, or qualify through Allow Creator for an action that supports it. |
Feature requires administrator access | A group selection does not replace a separate administrator requirement, such as access to Space Settings. |
Default checks for common actions
The table below summarizes the checks used in Vansah’s screens when no groups are configured for the action. Where alternatives are listed, the user needs one of them.
Jira permission needed | Vansah actions |
Permission to browse the Jira space | View the Vansah Board, work item panel, test cases, reports, and Recycle Bin. Create, edit, clone, link, and execute test cases; manage test case versions; create or edit Test Folders and Test Plans; add labels; export test cases and Cucumber features. |
Permission to delete work items or administer the Jira space | Delete test cases, Test Plans, plan iterations, Test Folders, Test Runs, Test Plan Folders, and case/run/plan attachments. Also used for permanent deletion and restoration actions in the Recycle Bin. |
Permission to make bulk changes, delete work items, or administer the Jira space | Import test cases, import test case results, and access Cucumber report import from the Vansah Board. |
Permission to administer the Jira space | Delete a saved report or stop sharing it from the report menus. Viewing, creating, cloning, editing, and sharing reports normally use space browsing access. |
Jira administrator or Jira space administrator access | Open and manage Vansah Space Settings, including permission configuration. |
Example: A tester who can browse the Jira space can normally create and execute test cases when those functions have no group restrictions. Deleting a case uses a different default check, unless the creator rule applies.
Opening the Recycle Bin and restoring or permanently deleting an item are separate actions. Viewing the bin does not by itself grant access to every action inside it.
Some features and direct REST API operations apply additional checks. For an integration, use the permissions documented in the relevant API guide.
What Allow Creator means
Allow Creator is available for supported actions such as editing a test case, deleting a Test Plan, or editing a folder. It refers to the person who created the relevant item.
When Jira groups are configured, enabling Allow Creator can let that person perform the action without belonging to a selected group. Other users need membership in one of the selected groups.
When no groups are configured, Vansah also retains a creator fallback for actions that recognize the item’s creator. Clearing the group selection therefore returns the function to its Jira permission and creator checks.
Review or change a permission
Open Vansah in the Jira space.
Select the settings gear, then Settings and Compliance → Space Settings.
Open Permissions and find the function you want to review.
Check the selected Jira groups and whether Allow Creator is available and enabled for that function.
To restrict the function, select the groups that should have access and review the creator setting. To use the default Jira checks, leave the group selection empty.
See Managing User Permissions with Jira Groups for configuration details, or Accessing Vansah Space Settings if you cannot open the settings page.
If a user cannot perform an action
Confirm that the user can access the correct Jira space.
Check the permission for the exact action. For example, creating a case and deleting it use different checks.
If groups are configured, verify the user’s membership and the Allow Creator setting.
If no groups are configured, ask a Jira administrator to review the user’s Jira permissions and any applicable creator access.
Check that the feature is enabled and available for the Jira space. If the issue continues, contact your Vansah administrator with the action and the message shown.