Administration

Administration section contains all the organization wide settings of Allure TestOps.

You need to have role ROLE_ADMIN assigned to you to be able to access the Administration area.

Administration overview

if you see this write to help.qameta.io

Below in the table you will find the brief description of each item in the settings.

Item	Description
Users	Area where you manage your users. You can add, delete, assign certain roles here
Groups	Area where you manage user groups to provide easier access to projects on group level instead of user level
Roles	Place were you define global roles to be used for mapping in the projects, e.g. Owner, Lead, Reviewer
Statuses	Here you define global statuses of tests life cycle (draft, review, active, or outdated, etc.)
Workflow	Defines the right transition between Statuses, e.g. Active -> Outdated for automated tests. This is adjustable.
Test layer	Defines global Test layers to be used for mapping in the projects. E.g. UI Tests, or API Tests
Custom fields	Defines the global custom fields to be used for mapping in the project, e.g. Feature, Story, Suite
Environment	Defines the global Environments labels to be used for mapping in the project, e.g. Host, Browser, Branch
Error categories	Defines global Errors categories and rules to match these categories in the test results.
Credentials	Storage for credentials used for the integrations; could be Username and Password pairs or secret tokens used to authenticate Allure testOps in third party solutions like TMS, Issue trackers etc.
Build server	Storage of the connection settings for the integrations with build (CI) servers
Issue tracker	Storage of the connection settings for the integrations with Issue trackers
Test Management Systems	Storage of the connection settings for the integrations with third party Test Management Systems
Clean up policies	Stores the rules for the deletion of old data like attachments or scenarios for old test results.