How to manage private BJJ academy video access

Define an active member before inviting accounts

Choose who at the academy is responsible for the active-member roster and when they update it. Think through routine cases such as a new student, a pause in training, a departure, and a returning member. Use the academy’s real membership decision rather than assuming possession of a link proves current membership.

Academies collect student dues outside Dendrition. The product records active academy membership; it does not verify external dues payments. If your academy changes a student’s status after reviewing its existing billing system, an authorized instructor still needs to manage that student’s library access.

Use the academy code for entry, then individual accounts

The instructor can share one reusable academy join code with current gym members. Each student enters it with their own email, receives a private invitation, and completes password setup. The student later signs in using their individual account. The code is an enrollment gate and should not be described as a shared member login.

For example, when a new member joins the evening class, the instructor shares the academy entry route and code. The member completes their own invitation; they do not borrow another student’s account. If entry fails, resolve the person’s invitation or account state rather than handing them a working member’s password.

Keep teaching responsibility separate from belt rank

A gym may have a brown belt assisting an evening class or a black belt teaching a regular session. Decide what each person is responsible for, then use the appropriate academy account role. Experience on the mat is not an automatic grant of permission to manage member accounts, change access, or handle the owner’s subscription.

Dendrition distinguishes owners, instructors, assistant instructors, and students. Owners and instructors manage academy access; assistant instructors have narrower permissions, and subscription controls remain owner-only. Updating a student’s recorded belt rank does not grant staff authority or restrict that student to a different set of published programs. All active members currently receive the full published library.

Check both publication and membership

A private library has two distinct decisions: whether the academy has published the lesson and whether the person has academy access. A draft lesson is not member content simply because its video has finished processing. Likewise, an accessible public product explanation does not grant permission to view private academy recordings.

Dendrition checks access before issuing private playback, and a recording must be ready for playback. Current active members receive every published program in their academy, including later-published material. Selected belt-rank restrictions are planned and unavailable today; use that actual behavior when deciding what to publish.

Choose the appropriate action when membership changes

Ending academy access removes a student from that library while preserving the account and personal progress for restoration. This is appropriate to evaluate when the academy needs to stop access without permanently removing the student’s account. Keep a record of who made the membership decision and resolve disputes through the academy’s own process.

Permanent student deletion is a separate irreversible action. Dendrition restricts it to eligible ordinary student accounts and protects identities connected to another academy or privileged roles. Treat deletion as an account decision with its own confirmation, not as the routine equivalent of pausing library access.

Review allowed and denied paths

Before sharing a library widely, use accounts you are authorized to test to review both the expected entry and a blocked entry. An active member should see the published academy library. A person without academy access should not gain private playback from a copied lesson address. Draft recordings should remain outside the student library.

When an account is blocked, confirm the academy, the person’s membership status, and whether the lesson is actually published and ready. Keep support details private. A public help message should explain the next step without exposing account lists, private lesson information, or technical credentials.

• Confirm the roster reflects the academy’s current membership decisions.
• Review the member library after publishing new material.
• Check that a departing member’s academy access has ended.
• Keep individual passwords and invitation emails private.

Agree a recording and sharing policy separately

Account access controls decide who may open the library. The academy also needs its own decisions about who appears in recordings, permission to record, how members may use the material, and whom to contact with a removal concern. Explain those expectations before recording or inviting members.

Private playback is not a guarantee against screen capture or redistribution by an authorized viewer. Discuss sensitive recording decisions with the people involved and obtain appropriate advice for your academy’s circumstances. Publishing only reviewed material and keeping the access roster current are useful operating habits, not substitutes for that policy.