Hi.
As someone with my own TeamTalk server, I have picked up a few things that I think can help you.
1. When creating channels, there are a few things you want to do.
A. Make sure to click the permanent channel stored on server option, otherwise your channels will not save.
B. If you have file sharing, there's a field that asks you for a max quota for each channel. In this field, type 9999999999. If you don't do this, people won't be able to upload files unless they're admins.
C. In the audio channels, switch it from mono to stereo, and in the bitrate field, enter 128000. You can create an LQ channel if people keep dropping.
2. On this one, I'm speaking entirely from experience. Whatever you do, do not, and I really mean do not use the same password for your admin account that you use on another server. So for example, let's say my server was account based, and you had an account up there. You would not want to use the same password for your admin account on your server that you have on mine, because anyone could easily sign into your account and entirely screw your server over.
3. When giving people admin, manually go through and check off options. Although it may seem easy just to set the user type to admin and call it done, never do this. You don't want one of your admins going in and deleting accounts.
4. Give each user the ability to send broadcast messages. At times this may be a little spammy, but sometimes it can be convenient if someone needs to get a message to you or another admin.
Hope this helps you, and feel free to ask more questions. I'll do my best to answer them

Don't give anyone the broadcast text messages permission. This can be very annoying if abused. Use user accounts to avoid spam and other abuse. If everyone has to have a valid username and password to connect, this significantly cuts down on spam and other issues that occur due to random people connecting. It also makes getting rid of problematic users very very easy, as all you have to do is get rid of a user account and that person can no longer connect. Limit how many users can connect from a single IP address. You may also want to set it up so that only one login from any account is permitted. This will kick anyone that tries to connect using the same credentials if that account is already logged in. Finally, don't give anyone the ability to make other users and/or themselves channel operator unless you trust those people. I had this enabled on my server for a long time before someone pointed it out to me.

If you're concerned about users taking up too much storage with files, set maximum limits for both the total amount of data allowed on the server, as well as a limit on a channel by channel basis. For instance, mine is set to 10000000 which is roughly 10 GB. Once this limit is reached, the server will prevent anymore data from being uploaded.

You may want to consider purchasing the encrypted server, although I'm not sure this is totally worth it. It costs $130 which is beyond ridiculous, and user accounts may be able to keep most problems from happening in the first place. Still, it bothers me that most servers are running without encryption just because the developer wants to make a little more money. Sure, go ahead and sell the SDK, but why does he have to charge so much for encryption? Maybe I'd be more concerned if there was super sensitive data going across my server, but there really isn't. Honestly, I wish someone else would maintain the TeamTalk project. It's a great concept, but the developer is awful! He doesn't seem willing to do many things, including adding encryption as a mandatory option, adding TTS support to the macOS client, allowing the use of video on mobile devices, etc.

Encryption is a standard on the Internet now. TeamTalk sends all data in the clear. This includes channel passwords, text messages, login credentials, and all voice or video traffic. If someone got in the middle of that communication, they could see all the data going back and forth. Then again, I suppose the risk is minimized by user accounts. If you can't connect, you technically shouldn't be able to see all the data going back and forth.

Here's one more tip for good measure. Don't use an automated system for creating user accounts. If you do, it's like telling someone the key to your house is under the front mat and to come on in anytime. It totally undermines the purpose of user accounts.

I doubt I have the bandwidth for a music bot anyway.

And that brings up an entirely different question, what on earth is a music bot?

those are probably expensive, so nope

man you can get it for free no problem but i wouldn't trust just a single person that would just say i can give you for free.

Well, since things got moved around, I thought tt would be easier to have guests on youtube. How many/what kind of channels should I set up?

Oh, I know. I'm a fan of discord. I just get frustrated with the voice channels and things.

Seems like playing your own music would make more sense, and I have a lot of music.

I doubt any sighted people actually watch my streams.