User menu and API tokens

Registration

To create an account, an administrator first has to invite you to the instance. After you receive the email, complete the registration flow from the invitation link:

1. In the invitation email, click Accept invite.

   The registration form should open in the web browser.

   If you get the “Invitation not found” message instead, this most likely means that the invitation link has expired. Contact the instance's administrator and ask them to resend the invitation.

2. Fill in the registration form:

   • Username — a short identifier of your account. Must be unique across all accounts in the Allure TestOps instance. After the registration, you will not be able to change your username;
   • First name and Last name — your full name;
   • Password — a password that you will use to sign in to Allure TestOps.

3. Click Continue.

   You will be signed in and redirected to the home page with a list of available projects.

Allure TestOps version and service status

Two quick checks are useful before you open a support case or compare behavior with the documentation:

• Click your avatar to see the current Allure TestOps version in the user menu.
• Open <your Allure TestOps URL>/status to reach the instance status page.

The version helps you confirm whether a feature or UI behavior should exist in your deployment. The /status page helps distinguish a product-level issue from a broader service outage.

Profile settings

To view or change your name, email, password, avatar, UI theme, or navigation colors, use Personal settings.

Managing API tokens

Use an API token when a CI system, IDE plugin, CLI workflow, or your own integration needs to act in Allure TestOps with your permissions.

API tokens are personal. They have the same access as your account, and actions performed with a token are logged in Allure TestOps on your behalf.

Treat API tokens like credentials:

• create one token per external system or workflow;
• store it in that system's secret storage;
• delete it when the integration is no longer needed.

Add an API token

To add an API token:

1. Click your avatar and go to the API Tokens section.

2. Click + Token.

3. Enter a name for the token (for example, a name of the system for which you are creating the token) and click Create.

   Allure TestOps will generate the token and display it in a modal window.

4. Click the Copy icon to copy the token into clipboard.

5. Store the token in the external system that will call Allure TestOps.

Delete an API token

Delete a token to revoke that integration's access immediately.

To delete an API token:

1. Click your avatar and go to the API Tokens section.
2. In the list, find the token you need by its name.
3. Click the Delete icon next to the token name.

Activating beta features

Feature previews are user-level flags for trying beta functionality without changing the experience for other people in the same instance.

To activate a beta feature:

1. Click your avatar and go to the Feature previews section.
2. Select and activate the feature you need using the toggle (feature flag).

Features available in the Feature previews section are still in development and may not work properly. They will continue to be updated and improved until the official release.

If needed, you can deactivate a beta feature at any time to return to the regular version of Allure TestOps.

Next steps

• API of Allure TestOps if your next step is programmatic access.
• allurectl if you need CLI-based upload or CI execution.
• Integrations if the token will be used by CI, issue trackers, or export workflows.