Yes. SleekView reads the bridged Blackboard tables directly through whatever schema the active Blackboard Bridge edition exposes. The legacy Original Course View bridge stores votes in a flat counter column, and the newer Ultra Course View bridge uses a normalized reaction table. Both shapes are handled without extra config on the board side.

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

Yes. The data source picker lets you filter the underlying query by course ID, term meta, forum ID, or any meta column the bridge syncs. A single course, a single term, or a curated set of high-signal forums can each get a dedicated SleekView board on its own WordPress page for the right audience.

Status pill changes update the Blackboard discussion or feedback status column through the bridge write endpoint, so the chip on the Blackboard activity stream updates as well. Discussion content, votes, and grade entries stay untouched. Instructors can revert a status by editing the field and the next sync reconciles the change.

Hidden discussions 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 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 discussion replies 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 course discussions, votes, and statuses to prospective students. Voting itself can be gated to enrolled students by checking the standard Blackboard enrollment meta synced through the bridge 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.