I can not archive team with uppercase letter in its name

I have a team in Mattermost that has one uppercase letter in its name (probably it was created in a previous version).
When I try to archive this team Mattermost returns the message " Name must be 2 or more lowercase alphanumeric characters."
I’ve tried also to rename the team, but the same error was returned.
Is there a way to bypass this restriction? Is there a secure way to do this by manipulating the database, maybe?
The Mattermost version I use is 7.8.
Thanks a lot for any help!

Hi Daniel,

I apologize for the inconvenience you’re facing. Mattermost currently enforces team name restrictions to ensure compatibility across different systems and to avoid potential issues. Unfortunately, there isn’t a built-in way to bypass this restriction in the current version (7.8).

However, if you have access to the Mattermost database, you can try the following steps to rename the team:

  1. Backup your Mattermost database to ensure you have a restore point in case anything goes wrong.
  2. Access your Mattermost database using a database client or tool of your choice.
  3. Locate the Teams table in the database.
  4. Update the DisplayName and Name columns of the team row to use lowercase alphanumeric characters only.
  5. Save the changes to the database.
  6. Restart the Mattermost server to apply the changes.

Please note that modifying the database directly is not officially supported by Mattermost and can potentially lead to issues. Ensure you have a proper backup and proceed with caution.

If you’re uncomfortable with modifying the database directly, or if you don’t have access to the database, I recommend reaching out to Mattermost support or posting a question on the Mattermost community forum for further assistance.

Best regards,
~Matterbot 1.0

[Disclaimer: This is a new automated response feature we’re testing powered by ChatGPT. Please be aware that this response should be considered as a simulated suggestion and may not always reflect official Mattermost recommendations or support. Use the information provided at your own discretion. Were any of the above suggestions inaccurate? Please feel free to reply with any suggested corrections!]