Yes. SleekView reads the bridged Moodle tables directly through whatever schema the active Edwiser Bridge Pro version exposes. Legacy 1.x bridges store votes in a flat counter column and the newer 2.x and 3.x bridges use a normalized meta table. Both shapes are handled without extra config on the board side at all.

They do. The Moodle mobile app records forum votes through the standard Moodle Web Services API, which writes to the same row the desktop client uses. The Edwiser bridge syncs the new count to WordPress on the next interval and SleekView picks it up on the next board render without any mobile-specific config.

Yes. The data source picker lets you filter the underlying query by Moodle course ID, category ID, certificate template ID, or any meta column the bridge syncs. A single course, a single category, or a curated set of high-signal certificates can each get a dedicated SleekView board on its own page.

Status pill changes update the Edwiser status column through the bridge write endpoint, so the chip on the Moodle activity stream updates on the next sync. The forum post body, vote total, and certificate template stay untouched. Instructors can revert a status by editing the field and the next sync reconciles the change.

Hidden posts and rows from unenrolled students drop off the board because SleekView queries only visible rows for enrolled members by default. If you want an instructor view that includes hidden or expired rows, the query filter accepts a status array so instructors can see them without exposing the rows to enrolled students.

No. SleekView paginates the underlying query, caches the sorted set per page slug, and only fetches the rows it needs for the current page. A board over half a million bridged Moodle posts serves in the same time as a board with five hundred because the database does the heavy lifting once and the cache covers every subsequent visitor.

Yes. The board reads from the bridged tables independently of enrollment, so a public roadmap page can show forum threads, certificate requests, votes, and statuses to prospective students. Voting itself can be gated to enrolled students by checking the standard Moodle enrollment meta on submit.

The board keeps rendering as long as the bridged tables stay in the database. Deactivating the bridge freezes the data at the last sync so the board serves with stale counts until reactivation. A tenant move keeps the bridged schema intact, so existing votes and statuses stay correct on the next render.