Community Forums Today's Posts     Member List     Archive    
Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2005
    Location
    Lynnwood, WA
    Posts
    3

    Access levels...

    In order to prevent a server from being taken over by even the simplest mistakes, you could implement access levels that are more extensive. Especially an access level noted as the Server Owner (SO) level, which can only be assigned to one account per server. By creating such an access level, the server could never be taken over like it can currently be by someone getting Server Admin (SA) access. Also, since it can only be assigned to one account per server, the access could never be accidently given to someone. The level wouldn't really even need much more access to it, just simply making it immune to those with SA access would be enough. That having been said, maybe people with SA access should have immunity from other people with SA access. The only person with power over the people with SA access would be whoever has the SO access or you could make it so that the SO could toggle the SA users' immunity from other people with SA access.

  2. #2
    Join Date
    Jan 2005
    Location
    Lynnwood, WA
    Posts
    3
    Expanding on this a little bit, I think it would be kinda useful to manage individual user permissions, which of course would be for managing Registered users only. This would allow Server Owners (SO) or Server Admins (SA) to grant more or less permissions to individual users unlike the current setup where the permissions are covered solely by the group rights (Server Admins, Channel Admins, Operators, ...).

    Also, I'm not so sure that the title Server "Owner" would always be applicable to the person with that access level, so perhaps the Server Admin title should be moved up to this level of an account where only one exists and then create a new level called Server Operator (SO), which takes on the role of the previous Server Admin level that multiple users can have.

    Finally, another change I would make would be the Superadmin power. I think Server Manager or Machine Admin (or something similar) would be a nice change, but only because of my next suggestion of making it so that when Server Managers/Machine Admins log into a TeamSpeak server via the client-ware, they have a "(SM)" or "(MA)" next to their name signifying their user power.

  3. #3
    Join Date
    Feb 2005
    Location
    .
    Posts
    1,010
    There will be no more updates to TS2 unless there is a security problem. Check here for the TS3 Wishlist:http://forum.goteamspeak.com/showthread.php?t=17831

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Cannot access admin login page
    By Sgt. Duke in forum [TeamSpeak 2] Server Support
    Replies: 1
    Last Post: 23-02-2005, 08:55
  2. Memory access Violation when I unplug my joystick
    By Balthzar in forum [TeamSpeak 2] Client Support
    Replies: 0
    Last Post: 09-03-2004, 01:12
  3. RC2 Server Crashing For No Reason
    By Aww You Dead in forum [TeamSpeak 2] Server Support
    Replies: 6
    Last Post: 08-03-2003, 00:49
  4. Access violation at address 0044F050
    By BBr|JRBlood in forum [TeamSpeak 2] Client Support
    Replies: 2
    Last Post: 08-02-2003, 13:09

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •