Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 10 of 10
  1. #1
    Join Date
    October 2013
    Posts
    34

    Suggestion for Rework of TS Permissions Group and Channel creation.

    What I need from Teamspeak is an intermediate level and a complete overhaul of the format by which it structures people. Because I am having so much trouble achieving what should be a simple and straightforward easy to set up thing I felt I would provide a description of what kinds of things would be appropriate.

    1) Upon entering a new Teamspeak setup for the first time the individual who puts in the key code should be established as the Server Owner. This server group should assign itself to the individual, they should then be instructed to sign in from multiple other locations (mobile devices, additional computers, etc.) so that they can establish themselves on that identity and be able to get in and reassert possession of the Teamspeak should something go wrong with the computer they use most for access. They should be able to assign themselves, as can be done now, this position on any computer they are also logged in from. While these actions are currently possible in Teamspeak, they are not currently prompted for in the initialization of Teamspeak. Further, once the Server Owner is established then an administrative channel should immediately be generated separate from the default channel and in which they have full permissions to do whatever they want to anything on their server.

    2) Teamspeak setups are administrated by a small group of people who have specifically assigned duties to effect through Teamspeak as the communication medium. Some of these duties are specific to controlling functions, formats, and behavior within Teamspeak - but the group they support is more than virtual. Additional actions for interviewing candidates for group membership, maintaining membership records, coordinating group assets, planning schedules, publishing information through blogs, etc. all are coordinated in support of club activities. While this is true of large virtual gaming groups it is just as true of any club concerning any topic in any format anywhere in the world.

    When the Server is first set up, the Server Owner should be able to immediately create a Server Echelon/Grade/Stratum for command purposes which will have administrative powers subordinate to the Server Owner, can never exceed the Server Owner, never remove the Server Owner, etc. The Server Owner should be able to alter their permissions, but they should not be able to alter their own - though they should be able to see them. This Server Echelon/Grade/Stratum may contain as many Server Groups as are created and assigned to it.

    When an Echelon is created the creator should be given the opportunity to check a box to create and administrative channel for that Server Echelon/Grade/Stratum, which only Server Groups in the new Server Echelon/Grade/Stratum and superior to it can enter without being moved to it. Sub-channels created off of an administrative channel would also be administrative channels. They may be passworded to those of equal and subordinate Server Group permissions, but the Senior position of the Server Echelon/Grade/Stratum, superior Server Echelon/Grade/Stratum members, and the Server Owner should be able to bypass this.

    After this, each time a Spacer is set up, there should be an opportunity to create another Server Echelon/Grade/Stratum that will have administrative authority only concerning the channels between that Spacer and the next Spacer. This Server Echelon/Grade/Stratum should automatically be able to see their own permissions and the permissions of those below them, but only Server Echelons/Grades/Stratums above them should be able to edit their permissions as set by the Server Owner.

    Each time a Channel is set up, there should be an opportunity to create another Server Echelon/Grade/Stratum that will have administrative authority only concerning that channel tree. This Server Echelon/Grade/Stratum should automatically be able to see their own permissions and the permissions of those below them, but only Server Echelons/Grades/Stratums above them should be able to edit their permissions as set by the Server Owner. As with Server Echelons/Grades/Stratums above, an administrative channel should generate for this Server Echelon/Grade/Stratum.

    When Sub-channels are generated there should be an opportunity to generate a subordinate Server Echelons/Grades/Stratums for the sub-channels of that channel tree. This would not include creation of administrative channels. This would be like the current Channel Groups, but the ability of these groups to turn the chain of command upside down - as they currently do, would be something the Server Owner would be able to prohibit with a simple single check of a box on any of the methods for reviewing the permissions systems: Easy, Intermediate, or Advanced.

    Whithers.

  2. #2
    Join Date
    June 2011
    Location
    Baghdad, Iraq
    Posts
    367
    for some reason i actually did read your all that wall of text ....

    dude every thing you're asking for is already there ... and judging on your other threads ... DO U EVEN TS?

  3. #3
    Join Date
    June 2013
    Location
    TeamSpeak Community Forums
    Posts
    108
    This could easily be done with channel groups with different levels of join power & join permissions, and for really secure channels remove b_channel_join_permanent, b_channel_join_semi_permanent, b_channel_join_temporary from the server groups or make sure those three permissions aren't skipped or remove them from the server groups & add them to the secure channels but untick them, and then assign them to a channel group instead.

  4. #4
    Join Date
    May 2012
    Location
    The 3rd dimension
    Posts
    956
    Quote Originally Posted by itteam View Post
    This could easily be done with channel groups with different levels of join power & join permissions, and for really secure channels remove b_channel_join_permanent, b_channel_join_semi_permanent, b_channel_join_temporary from the server groups or make sure those three permissions aren't skipped or remove them from the server groups & add them to the secure channels but untick them, and then assign them to a channel group instead.
    Additionally those permissions need to be removed from the defauly guest channel group, to prevent them from having those permissions. It they are part of the server groups and unskipped that will work well.

    Also, to the original poster, TL;DR

  5. #5
    Join Date
    January 2010
    Location
    Secret Base in Arctic Region
    Posts
    1,671
    The only good passage in this text is the information about saving the identity when starting the client for first time or whenever creating a new identity.
    The rest is like Mr. Blackadder once said "utter crap", and can already be done with the present functions (like a template group for the "server owner").

  6. #6
    Join Date
    June 2011
    Location
    Baghdad, Iraq
    Posts
    367
    Quote Originally Posted by Alcazar View Post
    The only good passage in this text is the information about saving the identity when starting the client for first time or whenever creating a new identity.
    but.. its already possible.. if the server admin is too lazy to click 2 buttons to save his ID then...

  7. #7
    Join Date
    December 2004
    Location
    RF
    Posts
    3,008
    This is not about server, this is about client identity.
    Basically, it's like a bank-client apps, you start them first time, they generate a new identity, save it in their profile, and ask client for ANOTHER PLACE to store THE COPY of said identity for backup purposes.
    The difference is only that you don't necessarily need to encrypt TS3 identity when storing.

  8. #8
    Join Date
    October 2013
    Posts
    34
    My experience so far with Channel Groups is that there is nothing on them any place. Most material on TS - and I have googled around quite a bit over several months, are sparse, more like a brief for a CEO, and written in technospeak (not communicable standard English). Further, the skip function does not work. I have, as Server Admin, the b_client_skip_channelgroup_permissions enabled and they do not work. When I go into my channels I am unable to assign more than half of my server groups.

  9. #9
    Join Date
    January 2010
    Location
    Secret Base in Arctic Region
    Posts
    1,671
    How about joining your TS, go into said channels where it obviously "does not work", then right-click on yourself, select "permissions -> overview" and then export it and post it here?
    Maybe we can see then why its not working...

  10. #10
    Join Date
    October 2013
    Posts
    34
    Thanks go to Chris for a solution to my difficulties in assigning ranks. Though at the time that I first saw it I didn't catch it because it looked like more combing through the permissions system. Hence, I attempted various approaches to the same difficulty asking different questions in order to find a resolution. I have in separate threads suggested: 1) an intermediate level that would accomplish organizational goals rather than simply the basic and advanced, 2) Asked how to eliminate all channel groups, 3) Asked for worksheets that could be printed up and provide a solid visual representation to work with in comparing and preparing the permissions, 4) stated how Skip Channel Groups Permissions was inexplicably overriden one week afterwards, 5) stated my dismay at Channel Groups automatically overriding the power of the Server Admin and Channel Groups being superior to the administrative powers of the Server Admin, and 6) Asked for assistance in figuring out if my TS permission value settings were the problem.

    This answer was provided when I first came upon the idea of removing all channel groups from TS so that they couldn't cause problems:
    Quote Originally Posted by Chris View Post
    No, you can't do that.

    What I said was to right click youself, permissions, channel groups of client -> Remove all
    At the time this answer was given, 03SEP14, I misread it as more combing through the code based lingo of the permissions system looking for something to change.

    Thank you to all of you who made a sincere effort to assist me in these various approaches to this among other difficulties I have with getting TS to support the organizational structure of my guild.

    Withers
    Attached Files Attached Files
    Last edited by Withers; September 15th, 2014 at 07:35 AM.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 4
    Last Post: December 14th, 2013, 09:17 PM
  2. [Resolved] How do you disallow Guest - Channel Creation Permissions?
    By valtam in forum Permission System
    Replies: 2
    Last Post: December 27th, 2011, 12:27 AM
  3. Suggestion - CHANNEL SERVER GROUP PERMISSIONS
    By Chakrabarti in forum Suggestions and Feedback
    Replies: 1
    Last Post: January 14th, 2011, 04:39 PM
  4. [Solved] Token Creation is not limited by channel permissions
    By [KH]Cross in forum Permission System
    Replies: 6
    Last Post: February 14th, 2010, 04:55 PM
  5. Replies: 8
    Last Post: January 14th, 2010, 10:36 AM

Posting Permissions

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