Locking a room when Sync Permissions from Category/Channel is enabled does not Lock Room

[shell cloud]

Title. When I Lock a room, Connect permissions that are granted to Roles from initial creation are not revoked. These are pulled from Category/Channel on creation as different areas of the Discord have different groups that should and shouldn't be able to access the VCs generated, hence syncing permissions. Pictures to follow.

Room Locked: See Above

Verified Users and others above all can still Connect:

A non-trusted member is able to join:

Is this a bug, or somehow a misconfiguration? Are private rooms not supported when syncing permissions from a Creator Channel/Category?

The only Member Role that can see is Verified currently. The test user that was joined was unverified:

[dense flicker]

Seems like not a bug but might be complicated. What permissions are you syncing from the creator?

[shell cloud]

It's a mixture based on Role and what that Role is allowed to do. Generally, they have these Voice Permissions, below.
Some have Priority Speaker, three more "moderator-type" roles have Move Members.

I have an Enforce PTT creator that denies Use Voice Activity to everyone. Another creator is in a more restricted area that only a certain group can utilize, but that everyone can "view" (cannot connect) so people know that group is online and active. Again, a mixture.

[dense flicker]

@shell cloud I am very sorry about the current situation in #notification. I will compensate somehow the time the custom bots are now offline

[shell cloud]

No worries, hardware issues happen.

[dense flicker]

I will help you with you problem here when everything is running fine again. Hopefully later or tomorrow

[dense flicker]

Thank you for your understanding. Its the first time I had such a problem

[dense flicker]

If I understood it right you give role X all these permissions which should be synced for the temp channels

And you also set this role X as member role

In that case you have to remove the „Connect“ and „View Channel“ permission from the category from role X because these permissions are managed my the member role setting and shouldn’t be synced

[shell cloud]

I'll give that a try tonight.

[dense flicker]

I will also investigate. I thought I fixed this problem

[dense flicker]

So I have a problem. I would need to add 4 new input fields but that just too much

Overall I am not happy with this modal because it doesnt really explain whats the matter of renaming default placeholders

[shell cloud]

Hmm. Would it be easier to add a tab called Custom Placeholders? Then you just have space to stack as many as you want within the tab.

[shell cloud]

The permissions edits gets private rooms working for the "General" VC creators, but unfortunately not for my use-cases elsewhere, which is fine. Those other areas don't need private rooms, really, so it works out!

Ultimately, it boiled down to all the areas being set/configured as Private Channels. Disabling this and setting all roles neutral / inherit-from-global got the privacy lock/hide options working.

[dense flicker]

Sure but I am not a fan of a new tab just for 1 feature :/

[dense flicker]

Hm okay but I still need to fix this bug to avoid confusion in future

[shell cloud]

Give me a ping once that bug is patched and I'll test again on the other areas.

[dense flicker]

I Hope I can reproduce the issue. I will let you know if I need help

[shell cloud]

Perhaps a Premium tab, then? As the Activity Name is a premium feature. Gives space to have other premium configuration options.

Just a thought, as always having a❔as the Activity placeholder is causing strife with my users. Can't utilize the feature seeing as a good chunk of the server do not share their activity, or people join VC before booting up the game. Both parties have to manually override the name when it fails over to ❔, instead of it falling back to the standard naming convention of "Room".

But, that's just my organization being picky. In the end, the core of the features all work for us, so it's more of a nice-to-have at this point. Would be nice to utilize Activity Name and such, but not mandatory at this point.

[dense flicker]

I will find a Solution to make it clear in the dashboard

For now you can tell me what placeholders you want to get renamed and I will do this for you manually. (So I am not under pressure to update the dashboard ;D)

[shell cloud]

Your efforts are appreciated. Overall, it is a huge help to be able to sort all our crews into their own VCs when operations get hectic in Main. Plus allowing players to choose between an Open or Enforce PTT VC has been a hit.

The only placeholder I'll need right now is:
{ACTIVITY_NAME} = Room

With that, I can change my Custom from:
Room #{NUMBER}
to
{ACTIVITY_NAME} #{NUMBER}
This way, rather than hitting ❔ #1 often, they'd get:

• Sharing Activity: GameName #1
• Not in game: Room #1
• Not sharing activity: Room #1

[dense flicker]

Alright now I need your server ID and the channel ID of the creator

[shell cloud]

Server:
||862753558620536892||
Creator Channels:
|| 1100640887144456242 1109343783700668556 1109626074196881490 1109626347661316166 1108585907264692254||

[dense flicker]

Alright will do it later

[shell cloud]

Much appreciated. Thank you!
Let me know once completed, and I'll run some tests to confirm.

[dense flicker]

Done

[shell cloud]

Awesome, I'll test in a few minutes

[shell cloud]

It works! Thanks for the help!

[dense flicker]

Nice now I dont have the pressure to make the dashboard better ;D

[dense flicker]

Found the issue and its finally fixed 🥳

https://discord.com/channels/904322845646135317/1110683882371694602

[shell cloud]

[shell cloud]

Hey. I noticed that if a user has set a custom status, the rooms generate with Custom Status. Any way to have that fail over to the Placeholder/Default that's set as Room?

[dense flicker]

Usually it should display the default name of the placeholder or the second activity of the user

I will look into it

[shell cloud]