Deleting Elements

The following tables provide information about which elements can be deleted and who is authorized to do so.

Ticket Draft

Element	User Role	Limitations	Consequences	Important Notes
Ticket Draft	Code Users 	Can only delete ticket drafts that they have created themselves.	The ticket draft and all associated data, such as attachments, is irretrievably deleted. This action cannot be undone.	
	Members	Can only delete ticket drafts that they have created themselves.	The ticket draft and all associated data, such as attachments, is irretrievably deleted. This action cannot be undone.	
	Moderators	No limitations.	The ticket draft and all associated data, such as attachments, is irretrievably deleted. This action cannot be undone.	
	Administrators	No limitations.	The ticket draft and all associated data, such as attachments, is irretrievably deleted. This action cannot be undone.	

Ticket

Element	User Role	Limitations	Consequences	Important Notes
Ticket	Code Users	Cannot delete tickets. Can cancel tickets they created themselves, and only while they are "Open" (picture).	The status changes to "Cancelled" but the ticket and all associated data, such as conversations and attachments, remains visible.	By cancelling a ticket, code users can signal that support is no longer needed.
	Members	Cannot delete tickets. Can cancel tickets which are in their responsibility (picture).	The status changes to "Cancelled" but the ticket and all associated data, such as conversations and attachments, remains visible.	
	Moderators	No limitations.	The ticket and all associated data, such as conversations and attachments, is irretrievably deleted. This action cannot be undone.	Alternative: To hide a ticket from code users without deleting it, you can simply change its visibility to "Internal". This way you can keep the data in your system (picture).
	Administrators 	No limitations.	The ticket and all associated data, such as conversations and attachments, is irretrievably deleted. This action cannot be undone.	Alternative: To hide a ticket from code users without deleting it, you can simply change its visibility to "Internal". This way you can keep the data in your system (picture).

Video Session

Element	User Role	Limitations	Consequences	Important Notes
Video Session	Code Users	Cannot delete video sessions. Can cancel video sessions that they have requested themselves, and only while they are "Requested" (picture).	The status changes to "Cancelled" but the video session and all associated data remains visible.	By cancelling a video session, code users can signal that support is no longer needed.
	Members	Cannot delete video sessions. Can cancel video sessions which are in their responsibility (picture).	The status changes to "Cancelled" but the video session and all associated data remains visible.	
	Moderators	No limitations.	The video session and all associated data, such as screenshots and recordings, is irretrievably deleted. This action cannot be undone.	Alternative: To hide a video session from code users without deleting it, you can simply change its visibility to "Internal". This way, you can keep the data in your system (picture).
	Administrators	No limitations.	The video session and all associated data, such as screenshots and recordings, is irretrievably deleted. This action cannot be undone.	Alternative: To hide a video session from code users without deleting it, you can simply change its visibility to "Internal". This way, you can keep the data in your system (picture).

Template

Element	User Role	Limitations	Consequences	Important Notes
Template	Code Users	No access to templates.		
	Members	Cannot delete templates.		
	Moderators	No limitations.	The template and all associated devices, including associated data, such as tickets, video sessions and attachments, is irretrievably deleted. This action cannot be undone.	To prevent accidental deletion, the name of the template must be entered in a pop-up window to confirm the intention to delete (picture). Alternative: To prevent a template from being used further to create new devices, you can move it to the archive (picture). 
	Administrators	No limitations.	The template and all associated devices, including associated data, such as tickets, video sessions and attachments, is irretrievably deleted. This action cannot be undone.	To prevent accidental deletion, the name of the template must be entered in a pop-up window to confirm the intention to delete (picture). Alternative: To prevent a template from being used further to create new devices, you can move it to the archive (picture).

Device

Element	User Role	Limitations	Consequences	Important Notes
Device	Code Users	Cannot delete devices.		
	Members	Can only delete devices they created themselves and only up to 1 hour after creation.	The device and all associated data, such as tickets, video sessions and attachments, are irretrievably deleted. If the device is paired with a code, the code becomes available again. If the device is linked to a customer, this connection is removed. This action cannot be undone.	Devices can only be deleted via the back office application.
	Moderators	No limitations.	The device and all associated data, such as tickets, video sessions and attachments, are irretrievably deleted. If the device was paired with a code, the code becomes available again. If the device was linked to a customer, this connection is removed. This action cannot be undone.	Devices can only be deleted via the back office application.
	Administrators	No limitations.	The device and all associated data, such as tickets, video sessions and attachments, are irretrievably deleted. If the device was paired with a code, the code becomes available again. If the device was linked to a customer, this connection is removed. This action cannot be undone.	Devices can only be deleted via the back office application

Code

Element	User Role	Limitations	Consequences	Important Notes
Code	Code Users	No access.		
	Members	Can only delete codes they created themselves and only up to 1 hour after creation.	The code is irretrievably deleted. If the code is paired with a device, this connection is severed. The device can now be paired with another code. This action cannot be undone.	Deleted codes are lost permanently. They can never be used to pair a device again. Associated QR codes become useless. Customer Organizations: The code disappears from the codes list of the customer's organization.
	Moderators	No limitations.	The code is irretrievably deleted. If the code is paired with a device, this connection is severed. The device can now be paired with another code. This action cannot be undone.	Deleted codes are lost permanently. They can never be used to pair a device again. Associated QR codes become useless. Customer Organizations: The code disappears from the codes list of the customer's organization.
	Administrators	No limitations.	The code is irretrievably deleted. If the code is paired with a device, this connection is severed. The device can now be paired with another code. This action cannot be undone.	Deleted codes are lost permanently. They can never be used to pair a device again. Associated QR codes become useless. Customer Organizations: The code disappears from the codes list of the customer's organization.
	Customer Employees (Member, Moderator, Administrator)	Cannot delete codes created by your organization.		

Employee

Element	User Role	Limitations	Consequences	Important Notes
Employee	Code Users	No access.		
	Members	Cannot delete employees.		
	Moderators	Cannot delete employees.		
	Administrators	No limitations.	The employee and the associated account are irretrievably deleted and removed from all assignments (e.g., individual tickets) and groups (e.g., Fleet Management, Teams, etc.). All employee-associated data, such as personal information, is deleted from the organization. Chats, updates, and notifications of this user remain visible, however are anonymized ("Deleted User" (picture)). This action cannot be undone.	There must always be at least one administrator account in every company. The last one cannot be deleted. Warning: If the employee is referenced in groups (e.g., Fleet Management, Teams, etc.), make sure to add a replacement, otherwise new tickets or video sessions may go unnoticed.

Account

Element	User Role	Limitations	Consequences	Important Notes
Account	Code Users	No access.		
	Members	Can only delete their own accounts. 	The account including access data and access authorizations to your organization is deleted. Chats, updates, notifications, etc. from this employee remain visible. This action cannot be undone.	To prevent accidental deletion, the password of the account must be entered in a pop-up window to confirm the intention to delete (picture). The employee remains unchanged. To connect a new user account to it, a new invitation must be sent (picture).
	Moderators	Can only delete their own accounts.	The account including access data and access authorizations to your organization is deleted. Chats, updates, and notifications of this employee remain visible. This action cannot be undone.	To prevent accidental deletion, the password of the account must be entered in a pop-up window to confirm the intention to delete (picture). The employee remains unchanged. To connect a new user account to it, a new invitation must be sent (picture).
	Administrators	Can delete their own accounts. Can delete other accounts by deleting their employees (see above).	The account including access data and access authorizations to your organization is deleted. Chats, updates, and notifications of this employee remain visible. This action cannot be undone.	Your organization must always have at least one administrator account. The last one cannot be deleted. To prevent accidental deletion, the password of the account must be entered in a pop-up window to confirm the intention to delete (picture). The employee remains unchanged. To connect a new user account to it, a new invitation must be sent (picture).

Meta Team

Element	User Role	Limitations	Consequences	Important Notes
Meta Team	Code Users	No access.		
	Members	Cannot delete meta teams.		
	Moderators	Cannot delete meta teams.		
	Administrators	No limitations.	The meta team, all associated teams, and the respective customer mappings are irretrievably deleted. The meta team and its teams are removed from any groups in which they are referenced (e.g., Fleet Management, Notifications, etc.). All customer team mappings with teams of this meta team are deleted. This action cannot be undone.	Ongoing assignments remain! Team members who are already notification receivers for existing tickets or video sessions, remain so. Therefore, the deletion of the meta team only affects future tickets and video sessions. Warning: If the meta team is referenced in groups (e.g., Fleet Management, Notifications, etc.), make sure to add a replacement and to create new customer team mappings, otherwise new tickets or video sessions may go unnoticed.

Team

Element	User Role	Limitations	Consequences	Important Notes
Team	Code Users	No access.		
	Members	Cannot delete teams.		
	Moderators	Cannot delete teams.		
	Administrators	No limitations.	The team is irretrievably deleted. The team is removed from any group (e.g., Fleet Management, Notifications, etc.) in which it is referenced. Any customer team mappings with that team are deleted. This action cannot be undone.	Ongoing assignments remain! Team members who are already notification receivers for existing tickets or video sessions, remain so. Therefore, the deletion of the team only affects future tickets and video sessions. Warning: If the team is referenced in groups (e.g., Fleet Management, Notifications, etc.), make sure to add a replacement and to create new customer team mappings, otherwise new tickets or video sessions may go unnoticed.

Customer

Element	User Role	Limitations	Consequences	Important Notes
Customer	Code Users	No access.		
	Members	Cannot delete customers.		
	Moderators 	No limitations.	Private Customer: The customer is irretrievably deleted. Corporate Customer: The customer, including all its departments and inviations (customer employees), is irretrievably deleted. This action cannot be undone. Note: All codes and devices of this customer remain unchanged, but lose their association. They can now be added to another customer.	Dependent Organizations*: The connection between the two organizations is severed, and the customer is deleted from your platform. The customer's organization continues to exist, however, loses any devices, tickets and video sessions associated with your organization. Independent Organizations: The connection between the two organizations is severed, and the customer is deleted from your platform. The customer's organization continues to exist, however, loses any devices, tickets and video sessions associated with your organization. Devices, tickets and video sessions, originating from the customer's organization or another organization, remain unchanged. *Organizations that are not customers of sqanit themselves, but are only on the platform because of your invitation ("Managed Customer" setting active).
	Administrators	No limitations.	Private Customer: The customer is irretrievably deleted. Corporate Customer: The customer, including all its departments and inviations (customer employees), is irretrievably deleted. This action cannot be undone. Note: All codes and devices of this customer remain unchanged, but lose their association. They can now be added to another customer.	Dependent Organizations*: The connection between the two organizations is severed, and the customer is deleted from your platform. The customer's organization itself continues to exist, however, loses any devices, tickets and video sessions associated with your organization. The connection between the two organizations is severed, and the customer is deleted from your platform. The customer's organization continues to exist, however, loses any devices, tickets and video sessions associated with your organization. Devices, tickets and video sessions, originating from the customer's organization or another organization, remain unchanged. *Organizations that are not customers of sqanit themselves, but are only on the platform because of your invitation ("Managed Customer" setting active).

Invitations (Customer Employees)

Element	User Role	Limitations	Consequences	Important Notes
Invitations (Customer Employees)	Code Users	No access.		
	Members	Cannot delete invitations.		
	Moderators 	No limitations.	The customer employee and the associated account are irretrievably deleted. All employee-associated data, such as personal information, is deleted from the organization. Chats, updates, and notifications of this user remain visible, however are anonymized ("Deleted User" (picture)). This action cannot be undone.	Dependent Organizations*: All employee-associated data, such as personal information, is deleted from both your organization and your customer's organization. Independent Organizations: Invitations cannot be deleted. *Organizations that are not customers of sqanit themselves, but are only on the platform because of your invitation ("Managed Customer" setting active).
	Administrators	No limitations.	The customer employee and the associated account are irretrievably deleted. All employee-associated data, such as personal information, is deleted from the organization. Chats, updates, and notifications of this user remain visible, however are anonymized ("Deleted User" (picture)). This action cannot be undone.	Dependent Organizations*: All employee-associated data, such as personal information, is deleted from both your organization and your customer's organization. Independent Organizations: Invitations cannot be deleted. *Organizations that are not customers of sqanit themselves, but are only on the platform because of your invitation ("Managed Customer" setting active).
	Customer Employee (Member)	Cannot delete employees (=invitations).		
	Customer Employee (Moderator)	Cannot delete employees (=invitations).		
	Customer Employee (Administrator)	No limitations.	The employee and the associated account are irretrievably deleted. All employee-associated data, such as personal information, is deleted from both your and your customer's organizations. Chats, updates, and notifications of this user remain visible, however are anonymized ("Deleted User" (picture)). This action cannot be undone.	

Customer Team Mapping

Element	User Role	Limitations	Consequences	Important Notes
Customer Team Mapping	Members	Cannot delete team mappings.		
	Moderators	No limitations.	The individual customer team mapping is deleted.	Ongoing assignments remain! Team members who are already notification receivers for existing tickets or video sessions, remain so. Therefore, the deletion of the customer team mapping only affects future tickets and video sessions. Warning: If the deleted customer team mapping isn't replaced, new tickets or video sessions will be sent to the default team (picture). If there is no default team, new tickets or video sessions may go unnoticed (picture).
	Administrators	No limitations.	The individual customer team mapping is deleted.	Ongoing assignments remain! Team members who are already notification receivers for existing tickets or video sessions, remain so. Therefore, the deletion of the customer team mapping only affects future tickets and video sessions. Warning: If the deleted customer team mapping isn't replaced, new tickets or video sessions will be sent to the default team (picture). If there is no default team, new tickets or video sessions may go unnoticed (picture).

My Company

Element	User Role	Limitations	Consequences	Important Notes
My Company	sqanit Administrators	No limitations.	Your organization and all associated data is irretrievably deleted.	Must be requested.