testeiya 0.2.0

package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/index.mdx

@@ -0,0 +1,285 @@
+---
+title: Users Roles & Access Overview
+description: Manage users and permissions in Testomat.io with ease. Learn how to invite users, assign roles (Owner, Manager, QA, Accountant, Read-Only), add users to projects, manage teams, and perform bulk user management efficiently.
+type: article
+url: https://docs.testomat.io/management/company/users-and-permissions
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: user roles, access control, test management permissions, company roles, project roles, invite users, manage user roles, assign permissions, team management, read-only access, bulk user management, Testomat.io user roles, Testomat.io access control
+---
+
+import DirectoryLinks from "/src/components/DirectoryLinks.astro";
+
+<DirectoryLinks directory="management/company/users-and-permissions" />
+
+Managing users and permissions in Testomat.io is essential for effective team collaboration and project organization. Everything starts at the Company level — this is where you create your team space, invite users, and assign roles.
+
+Before you begin managing users and their permissions, make sure your company is created. If you haven’t created a company yet, follow this guide to get started: [How to Create a Company](https://docs.testomat.io/management/company/administration/#how-to-create-a-company)
+
+:::note
+
+Each user can only own one company to ensure project separation and clear access control.
+
+:::
+
+On the Companies page, you have a list of companies you participate in with mentioning your role in them.
+
+![Company dashboard](./images/att1_356.png)
+
+Once your company is ready, you can:
+
+- Invite users and assign roles (Owner, Manager, QA, Accountant, or Read-Only)
+- Add users to specific projects within the company
+- Manage user permissions and roles at the company and project levels
+- Organize users into teams for easier access control
+- Use bulk management options for large teams
+
+Use this section to learn how to effectively manage your users and ensure your team has the right access to get the job done.
+
+## Users Roles Overview
+
+Testomat.io provides different roles within projects and companies to make your testing process more convenient.
+Different team members have different access levels to management options.
+
+### Roles Within a Company
+
+- **Owner** is a team member who created a company, can purchase a subscription, invite/delete members to a company and a project, change other team members' roles inside the company, create projects, and has access to all features within the project.
+- **Manager** is a team member who can purchase a subscription, create projects, invite members to a company and a project, can change other team members' roles inside the company, except the owner role, and has access to all features within the project.
+- **QA** is a team member who can create projects and has access to all features within the project.
+- **Accountant** is a team member who can only update subscriptions and it is free of charge.
+- **Read-only** is a team member who has permissions for viewing or reading information, but can't make any changes. It is free of charge and available in Professional and Enterprise plans.
+
+### Roles Within a Project
+
+- **Owner** is a team member who created a project, can invite/delete members and Support user to a project, change other team members' roles inside the project, and has access to all features within the project.
+- **Manager** is a team member who has almost the same rights as the project owner: can invite/delete members and Support user to a project, has access to all features within the project but can't change other team members' roles inside the project.
+- **Regular User** is a team member who has access to all project features but limited access to project settings, can't invite or delete members and Support user to a project, nor change their roles within the project.
+- **Read-only** is a team member who has permissions for viewing or reading information, but can't make any changes. All team members with a read-only role at the company level automatically have a read-only role at the project level, and this role can only be changed to a non-read-only role at the company level.
+
+:::note
+
+The role within the **Company** does not always match the role within the **Project**. For example, user with the owner role at the Company level may be added to the Project within the Company as the regular user or read-only.
+As well, the same user within a Company may have different roles on different projects.
+
+:::
+
+## How to Invite a User to a Company
+
+Follow these steps to invite users to your company:
+
+1. Go to the **Companies** page
+2. Click the **Invite** button next to the company you want to invite users to
+
+![Testomatio - Invite_users](./images/att1_5718.png)
+
+Once the **Invite Users** page opens
+
+3. Enter the user's email. To invite multiple users, separate addresses with commas
+4. Select a specific role:
+
+- **QA** (Paid, project-level seat. Plans, designs, executes, and reports tests; creates and manages projects; files bugs, verifies fixes, and uses every feature needed for quality-assurance work within the project.)
+- **Manager** (Paid, project-level seat. Includes all QA capabilities plus the ability to invite teammates to projects and purchase or modify project subscriptions.)
+
+:::note
+
+Manager can only be invited one at a time. If multiple emails are entered, the **Manager** role option will be disabled.
+
+:::
+
+- **Accountant** (Free seat. Make payments, views invoices, payment methods and updates billing or tax information; no access to any project content or settings.)
+- **Read-only** (Free seat. Available on paid pricing plans. Views test cases, runs, and reports across projects but cannot edit or create anything.)
+
+:::note
+
+Users invited with **Read-only** access are assigned the QA role by default, but their permissions remain limited to read-only. They do not have full QA rights and cannot edit or create content.
+
+:::
+
+5. Click **Invite** button
+
+![Testomatio - Invite_button](./images/att2_5718.png)
+
+---
+
+- You will be redirected to the Company page
+- A confirmation message will appear to confirm that users have been successfully added
+- If the paid seat limit is reached, only eligible users will be added
+- If an invited email is invalid (wrong format or already exists), an orange warning message will appear
+- After users are added to the Company, you can assign them to Projects
+
+![Testomatio - Confirmation message](./images/att3_5718.png)
+
+## How to Add a User to a Project
+
+There are two ways to add a user to a Project: from the **Company Settings** or directly from the **Project Settings**.
+
+### How to Add a User to a Project from the Company Settings
+
+1. Go to the ‘Companies’ page.
+2. Select Company.
+
+![Testomat.io - Company](./images/Team_1n.png)
+
+3. Click on ‘Actions’ button and pick ‘Projects Access’ option or click on member’s name.
+
+![Testomatio - Invite_users](./images/Invite_users_4n.png)
+
+4. Choose the project via ‘Add to Project’ button or add to all projects with one click via ‘Add to All Projects’ button.
+
+![Testomatio - Invite_users](./images/Invite_users_5n.png)
+
+5. See that a member was successfully added to projects and click ‘Back’ button.
+
+![Testomatio - Invite_users](./images/Invite_users_6n_.png)
+
+6. See that projects appeared in added member’s line.
+
+![Testomatio - Invite_users](./images/Invite_users_7n.png)
+
+### How to Add a User to a Project from the Project Settings
+
+1. Go to the ‘Dashboard’ page.
+2. Select Company and Project.
+
+![Testomat.io - Project](./images/User_1.png)
+
+3. Go to Settings-> Users.
+4. Click ‘Invite’ button.
+
+![Testomat.io - Project](./images/User_2.png)
+
+5. Choose a User from the dropdown list.
+6. Click ‘Send’ button.
+
+![Testomat.io - Project](./images/User_3.png)
+
+7. Invitation has been sent.
+
+![Testomat.io - Project](./images/User_4.png)
+
+:::note
+
+Only company members can be added to the Project via Project Settings.
+
+:::
+
+## How to Manage Team Members on Company Level
+
+All invited members have a **QA** role by default. You can change the member's role on the Company Team Members page ('Companies' page -> Select Company -> 'Actions' button).
+
+![Testomatio - Manage team member](./images/Manage_team_member_1n.png)
+
+You can delete a team member by clicking on the 'Delete' button.
+
+![Testomatio - Delete team member](./images/Delete_team_member_n.png)
+
+With this action deleted team members will be moved to the **Removed** section.
+
+![Testomatio - Delete team member](./images/Delete_team_member_2n.png)
+
+So you can reactivate them at any time with previous role by clicking on the 'Reactivate' button or with Read-Only permissions by clicking on the 'Make Read-Only' button
+
+![Testomatio - Reactivate team member](./images/Reactivate_n.png)
+
+### How to Change Company Owner
+
+In Testomat.io, a company can only have one Owner. There are two ways to transfer ownership:
+
+- Transfer by the Current Owner **(recommended)**
+
+Only the current Owner can assign ownership to another user:
+
+1. Go to **Companies** page
+2. Select the company
+3. Open the **Actions** dropdown
+4. Select **Make Owner** option
+5. Confirm the action
+
+![change owner](./images/att1_429.png)
+
+- Transfer via Support (if the Owner is **unavailable**)
+
+If the current Owner cannot access the account (e.g. has left the company, email disabled, etc.):
+
+- A user with the Manager role must send a request to [support@testomat.io](https://docs.testomat.io/support/)
+- The request must be sent from the email address the Manager uses to log into Testomat
+- The email should include:
+  - the current Owner’s email
+  - the new Owner’s email
+
+:::note
+
+We strongly recommend using the first option whenever possible, as it is the most secure and efficient way to transfer ownership.
+
+:::
+
+## How to Manage Team Members on Project Level
+
+You can manage team members not only at **Company Level** but as well at **Project Level**.
+
+All members invited to the project have a **Regular User** role by default. You can change the member's role within the project on the Users page (Select Project -> Settings -> Users -> click on 'Extra menu' button).
+
+![Testomatio - Manage team member Project](./images/Users_roles.png)
+
+You can delete a team member from the project by clicking on the 'Remove' button.
+
+![Testomatio - Manage team member Project](./images/Remove_user.png)
+
+:::note
+
+In case, if a user deleted at the **company level** - they will be automatically **deleted from all projects** within the company.
+In case, if a user removed at the **project level** - they will be deleted **only from that project**, but remain in the company and can be added to a project again at any time.
+
+:::
+
+## Bulk User Management
+
+For faster and more convenient user management, Testomat.io provides a Bulk Actions menu. This menu appears when you select one or more users via checkboxes:
+
+- Selecting the checkbox in the header row selects all users on the page
+- Selecting a checkbox next to a specific user selects only that user
+
+Once selected, a dropdown menu and Execute button will appear, allowing you to apply actions to one or multiple users at once.
+
+![Bulk Actions](./images/att2_356.png)
+
+### **Available Bulk Actions**
+
+Here’s what you can do from the bulk actions menu:
+
+- Add to Project(s): Add selected users to one or more projects within the company
+- Remove from Project(s): Remove selected users from one or more projects
+- Make Manager: Assign the 'Manager' role to selected users at the company level
+- Make QA: Assign the 'QA' role to selected users at the company level
+- Make Accountant: Assign the 'Accountant' role at the company level
+- Make Read-only: Change user access to read-only mode
+- Grant Write Access: Upgrade from read-only to a regular role (QA or Manager depending on previous role)
+- Delete Users: Remove selected users from the company (they will be moved to the Removed section)
+- Export Users: Download selected users’ data into .csv and .xlsx files (includes Name, Email, Role, Status, etc.)
+
+Using bulk actions is especially helpful for managing teams at scale — saving time and reducing manual effort when updating permissions or organizing access across multiple projects.
+
+## Export Users List
+
+You may need to get data about users who are members of your company. Fortunately, Testomat.io makes it easy and convenient:
+
+![Testomat.io - Export Users List](./images/Export_Users_List_n.png)
+
+:::note
+
+Only users with Owner or Manager roles can export Users List
+
+:::
+
+The exported .csv file contains the following information about the company's users:
+
+- Name.
+- Email.
+- Role.
+- Status.
+- Paused At (UTC).
+- Last Login (UTC).
+
+![Testomat.io - Exported File](./images/Exported_File_n.png)

package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/read-only-user.md

@@ -0,0 +1,67 @@
+---
+title: Read-Only User Role in Testomat.io
+description: Learn how to add or manage Read-Only users in Testomat.io to provide stakeholders with view-only access to test cases, reports, and analytics without editing permissions.
+url: https://docs.testomat.io/management/company/users-and-permissions/read-only-user
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io read-only role, read-only user, read-only access, stakeholder access, add read-only user, invite read-only user, manage read-only permissions, grant write access, revoke write access, company roles, view-only access
+---
+
+## Read-Only User
+
+Some of your company members such as managers, BA, or other stakeholders may need to have read-only access to Tests, Run Reports, and Analytics in order to read, but not change any data. You can invite read-only users or make existing users read-only on the Company page.
+
+[![CleanShot 2022-05-27 at 20 27 19@2x](./images/170760796-fb2e6618-88b2-478b-ad34-a986a0933dc2.jpg)](https://youtu.be/W09O9jEXAIo)
+
+### Invite Read-Only User to a Company
+
+1. Navigate to the 'Invite users' from Company page
+2. Enter valid user's email (use comma to enter multiple emails)
+3. Select 'Read-only' option
+4. Click 'Invite' button
+
+![Testomat.io - Read-Only](./images/att1.png)
+
+:::note
+
+By default, Read-only users are invited with a **QA role**.
+
+:::
+
+### Make a Company Member Read-Only
+
+1. Click on 'Actions' button for selected member from Company page.
+2. Click on 'Make Read-Only' option from the dropdown menu.
+
+![Testomat.io - Read-Only](./images/Read_only_2n.png)
+
+### Make the Read-Only Users a Member
+
+1. Click on 'Actions' button for selected Read-Only user from Company page
+2. Click on 'Grant Write Access' option from the dropdown menu
+
+![Testomat.io - Read-Only](./images/Read_only_3n.png)
+
+:::note
+
+Read-Only users are free of charge and available in Professional and Enterprise plans.
+
+:::
+
+### Make user read-only on project level
+
+1. Go to Project Settings and open the Users tab.
+2. Click the three-dot menu next to the user’s name.
+3. Select 'Make Read-Only' from the dropdown options.
+
+![Testomat.io - Read-Only Project Level](./images/Read_only_project_level.png)
+
+### Make read-only user  a regular user on project level
+
+1. Go to Project Settings and open the Users tab.
+2. Click the three-dot menu next to the user’s name.
+3. Select 'Grant Write Access' from the dropdown options. 
+
+![Testomat.io - Grant Write Access Project Level](./images/Grant_write_access_project_level.png)

package/skills/testeiya/testomatio-docs/docs/management/company/users-and-permissions/teams.md

@@ -0,0 +1,138 @@
+---
+title: Managing Teams in Testomat.io
+description: Learn how to create and manage teams in Testomat.io to simplify user access across multiple projects by grouping users and assigning team-level permissions.
+url: https://docs.testomat.io/management/company/users-and-permissions/teams
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io teams, create team, manage teams, assign users to projects, group project members, team access management, bulk user access, test project permissions, team roles, team workflows, user groups, project collaboration, team management tools
+---
+
+## Teams
+
+Teams in Testomat.io help you organize your growing organization by grouping users together and managing access to multiple projects efficiently. Instead of assigning users individually to each project, you can now create Teams and assign them to any number of projects in just a few clicks.
+
+This feature is critical for scaling organizations, improving permission control, and streamlining onboarding for new team members.
+
+**Why Use Teams?**
+
+- Simplified access management: Assign an entire group of people to projects in one action — no need to manage access user-by-user
+- Clear structure: Organize users based on people's roles, departments, or external teams
+- Consistent permissions: Ensure everyone in a specific role or team has access to the right projects — with a single assignment
+- Better control: Easily update access when people join, leave, or change teams
+- Visibility: See all projects and members connected to a team — all in one place
+
+[![Testomatio - Teams](./images/170760639-2b8710a6-20fb-4ae0-ad1e-d393295676b8.jpg)](https://youtu.be/_ejW1C9ciLo)
+
+### Real-World Benefits & Use Cases
+
+- **Onboarding new people quickly**
+
+When a new team member joins, simply add them to the appropriate team (e.g., QA Team), and they'll automatically gain access to all relevant projects — no manual steps required.
+
+- **Managing departments efficiently**
+
+In companies with several functional departments — like Backend, Frontend, QA, or DevOps — it's common for each group to work on multiple projects. With Teams, you can reflect that structure: create one team per department and assign them to the projects they’re responsible for.
+For example, your QA team can be granted access to 5 projects at once — no need to assign each QA engineer individually.
+
+- **Controlling access for contractors**
+
+Need to give external testers or developers limited access? Create a dedicated contractor team, assign only the projects they need, and manage their access independently from your core teams.
+
+- **Supporting role changes and reassignments**
+
+When someone changes roles — for example, moving from QA to a Project Manager position — simply remove them from their current team and add them to the new one. Their project access will be updated instantly based on the permissions of the new team.
+
+- **Temporary cross-functional initiatives**
+
+For time-limited efforts like major releases or audits, create a dedicated team (e.g., Release Task Force) and give them quick access to all related projects. When done, simply deactivate the team.
+
+### Teams Dashboard
+
+The Teams Dashboard provides a complete overview of all teams within your company — showing team names, members, assigned projects, and available actions like edit or delete.
+
+This centralized view helps you stay organized and manage access efficiently.
+
+To start organizing your teams and streamline access control, begin by creating your own team.
+
+![Teams Dashboard](./images/att1_356-1.png)
+
+### How To Create a Team
+
+To create a Team you need:
+
+1. Go to the 'Companies' page.
+2. Open your Company.
+
+![Testomat.io - Teams](./images/Team_1n.png)
+
+3. Click 'Extra menu' button.
+4. Select 'Teams' option from the list.
+
+![Testomat.io - Teams](./images/Team_2n.png)
+
+5. Click 'Create New Team' button.
+
+![Testomat.io - Teams](./images/Team_3.png)
+
+6. Enter Team name.
+7. Click 'Create' button.
+
+![Testomat.io - Teams](./images/Team_4.png)
+
+Team is created and now you need to add Projects and Users to your new team.
+
+### How To Assign a Team To a Project
+
+To add Projects:
+
+1. Click 'Add Project' button.
+
+![Testomat.io - Teams](./images/Team_5.png)
+
+2. Select projects from the list.
+3. Click 'Add Project' button.
+
+![Testomat.io - Add Project](./images/Add_project.png)
+
+Once added, all team members automatically gain access to these projects.
+
+### How to Add Users to a Team
+
+:::note
+
+Users must already be members of the company. Learn how to invite users [here](https://docs.testomat.io/management/company/users-and-permissions/#how-to-invite-a-user-to-a-company).
+
+:::
+
+1. Click 'Add User' button.
+
+![Testomat.io - Add User](./images/Add_user.png)
+
+2. Select users from the list.
+3. Click 'Add User' button.
+
+![Testomat.io - Add User](./images/Add_user_2.png)
+
+You can also edit your Team, add/remove user or assign the Team to another project by editing it at any time later.
+
+Namely, you can:
+
+1. Delete a team from a project by removing a project from the Team.
+2. Delete a user from the Team.
+3. Assign the Team to a project by adding a project to the Team.
+4. Add a new member to the Team.
+
+![Testomat.io - Edit Team](./images/Edit_team.png)
+
+5. Edit the Team name.
+6. Delete the Team.
+
+![Testomat.io - Edit Team](./images/Edit_team_2.png)
+
+### Tips for Effective Team Management
+
+- Regularly review team membership to ensure access remains up-to-date and relevant
+- Use clear and descriptive team names that reflect their roles or functions within your organization
+- Deactivate temporary teams once their projects or initiatives are completed to maintain a clean and organized workspace

package/skills/testeiya/testomatio-docs/docs/management/project/settings.md

@@ -0,0 +1,87 @@
+---
+title: Project setup and management
+description: Discover how to manage project settings in Testomat.io, including configuring the project timezone for teams across different regions. This guide outlines step-by-step instructions to adjust settings for accurate time synchronization and project administration.
+type: article
+url: https://docs.testomat.io/management/project/settings
+head:
+  - tag: meta
+    attrs:
+      name: keywords
+      content: Testomat.io, project settings, timezone configuration, project management, test management tools, team collaboration, software testing, administration
+---
+
+## Project Timezone
+
+If you have a multi-national team and everyone is working in different parts of the world, you need to avoid time mismatches. All your actions in the project will be displayed at UTC+00:00 by default. So you need to specify the project time manually.
+
+To do this, follow these steps:
+
+1. Click on **Settings** in the sidebar
+2. Click the **Project** button
+3. Active **Administration** mode
+
+![Testomatio.io - Project Settings](./images/New_0XUPKOcb_2024-10-05.png)
+
+4. Select the required time in the **Timezone** field
+5. Click the **Update** button to save changes
+
+![Testomatio.io - Project Timezone](./images/New_0oOC4blY_2024-10-07.png)
+
+## Project Testing Framework & Language
+
+A testing framework provides a structured set of rules and best practices to ensure effective and reliable test automation. It helps testers create and manage test cases more efficiently, reducing effort and improving consistency. By using a testing framework, teams can minimize testing time and costs, decrease the risk of errors, and enhance test accuracy.
+
+### How to Change the Testing Framework
+
+You can change the testing framework to meet your needs. To do this, follow these steps:
+
+1. Click on **Settings** in the sidebar
+2. Click the **Project** button
+3. Enable **Administration** mode
+4. Click **OK** in the popup **’Are you sure?’**
+
+![Administration_Mode](./images/att1_238.png)
+
+5. Select **’Project Framework’** from the dropdown
+6. Select a programming language you use in **’Project Language’** dropdown
+7. Click **Update** button
+8. Click **OK** to save the changes
+
+![Project_Framework&Language](./images/att2_238.png)
+
+In addition, when **’Administration’** mode is activated, you can:
+
+1. Delete the project – Click the **’Delete Project’** button
+2. Then confirm by clicking **’OK’** in the popup
+
+![Delete_Project](./images/att3_238.png)
+
+3. Archive the project – Click the **’Archive’** button
+4. Then confirm by clicking **’OK’** in the popup
+
+![Archive_Project](./images/att4_238.png)
+
+If you don’t see **’Administration’** mode, please note that this option is available only to users with **Manager** or **Owner** roles at the company level.
+For more details on **’How to Manage Company Roles’**, please explore here <a href="https://docs.testomat.io/management/company/#how-to-manage-company-team-members">Manage Company Roles</a>
+
+## Purge Old Runs
+
+To help manage storage and keep your test runs organized, the system automatically removes old runs based on a configurable storage period. Below are key details and guidelines about how this feature works and how you can control it:
+
+- By default, all test runs (both archived and unarchived) are stored for **90 days**
+- Only users with **Owner** or **Manager** roles can change the storage period to any value **up to 365 days**
+- Test runs (both archived and unarchived) that exceed the configured storage period are **automatically and permanently deleted** on a daily basis
+- Changing the storage period affects the next daily purge according to the new setting
+- Deletion is permanent and irreversible — deleted runs (both archived and unarchived) **cannot be restored**, even via the Pulse page
+
+To adjust the storage period:
+
+
+1. Click on **Settings** in the sidebar
+2. Click the **Project** button
+3. In the **Purge Old Runs** section, set the number of days (up to 365) you wish to keep the test runs
+4. Click the **Save** button to apply the changes
+
+After saving, a confirmation message will appear: **'Purge Old Runs settings have been successfully updated'**
+
+![Purge Old Runs settings have been successfully updated](./images/att_1207.png)