I have been using the tools for a short while and I love them TY for creating this system.

Imagine a community with 100% Extension users 🤔 Which functions would be interesting for you as a community owner or as a community member? --- Stellt euch eine Community mit 100% Extension Nutzern vor 🤔 Welche Funktionen wären dann für euch als Community Owner oder als Community Mitglied interessant?

How does your Skool extension setup look like? I used this background with many communities pinned on the left. --- Wie schaut euer Extensions-Setup aus? Ich nutze gerade diesen Hintergrund und habe auf der linken Seite einige meiner Communities angepinnt.

𝗟𝗶𝘃𝗲 C𝗮𝗹𝗹 𝗦𝗰𝗿𝗲𝗲𝗻𝘀𝗵𝗮𝗿𝗲 — 𝗠𝗲𝗺𝗯𝗲𝗿𝘀 𝘀𝗵𝗮𝗿𝗲 𝘁𝗵𝗲𝗶𝗿 𝘀𝗰𝗿𝗲𝗲𝗻 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗮𝗻 𝗮𝗱𝗺𝗶𝗻 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗼𝗼𝗺 Skool hands out screenshare in a live call one person at a time, and only someone with host rights who is actually sitting in that call can do it. A call without an admin therefore means nobody can share anything — the members wait for someone who never shows up. Auto Screenshare solves half of that: it grants everyone automatically, but only while a host is present. This is the other half. As the owner you open screenshare for your community once, and from then on every member gets it the moment they enter a call there — with nobody from your team in the room, and without you being online at all. There is no separate switch for it. The "Auto Screenshare" toggle in the Live Call settings is the unlock: turn it on and screenshare opens for every community you own, turn it off and the permission is withdrawn again. Ownership is verified on our side, so nobody can open a community that isn't theirs. It runs on your own Skool access, so you need to have used the extension yourself — otherwise there is nothing it could grant in your name with. For members it happens quietly. On entering the call the extension asks once, for that one person, and only for the call they are in — no dialog, no message, no waiting: the share button is simply there. Leave and come back and it asks again for the new call. Nobody else's permissions are touched, and the requests are capped per member so a reload loop can't hammer anything. One limit is worth knowing: the permission can only be handed out for calls that were created under your own account. Skool gives that right to whoever created the call, so if another admin scheduled the event in their name, screenshare stays closed there. Members also need the extension running — without it nobody asks, and Skool's normal rules apply. Opening screenshare for a community is a VIP feature. Using it costs members nothing; they just need the extension. --- 𝗟𝗶𝘃𝗲𝗰𝗮𝗹𝗹 𝗦𝗰𝗿𝗲𝗲𝗻𝘀𝗵𝗮𝗿𝗲 — 𝗠𝗶𝘁𝗴𝗹𝗶𝗲𝗱𝗲𝗿 𝘁𝗲𝗶𝗹𝗲𝗻 𝗶𝗵𝗿𝗲𝗻 𝗕𝗶𝗹𝗱𝘀𝗰𝗵𝗶𝗿𝗺, 𝗮𝘂𝗰𝗵 𝗼𝗵𝗻𝗲 𝗔𝗱𝗺𝗶𝗻 𝗶𝗺 𝗥𝗮𝘂𝗺

I want to take a moment to give a special thank you to @Kimberly Armatys for introducing me to the Skool Extensions community. I honestly had no idea how many tools and features were available to help community owners stay organized, better understand their members, and manage their communities more efficiently. Kimberly didn’t just point me toward the community. She also took the time to answer my questions and help me understand how everything works a little better. That kind of support makes a real difference when you are learning something new. Thank you, Kimberly, for sharing the resource, being patient with me, and helping me see what is possible. Because of your recommendation, I decided to invest in the VIP membership and invest in becoming a stronger community owner. I truly appreciate you!