Access control

Authorization in Vidext is a single permission model — resources and the actions each role may take on them — applied consistently everywhere a request can originate.

The boundaries

• Organization — the hard tenant boundary. People, content, knowledge, analytics, and settings exist inside one organization; nothing is shared across organizations.
• Team — the delivery unit inside the organization. Learner access flows through team membership and course assignment; authoring does not.

The roles, briefly

Organization roles (admin / member / learner / requester) govern workspace and content rights; team roles (admin / learner) govern team management and learning assignment. The full breakdown lives in Roles and permissions.

Two properties worth knowing as an evaluator:

• Pending means nothing. A join requester has no access of any kind until an admin approves them.
• Membership precedes everything. Nobody can hold a team role without first being an active organization member.

One model, every surface

The same permission checks run regardless of how a request arrives:

• the app (every screen and action);
• chat (workspace and module chat act as the signed-in user);
• connected AI assistants (an assistant authorized via MCP holds a token scoped to one user and one organization, and passes the same checks).

There is no privileged side door: an AI agent cannot do anything its human could not.

Content visibility rules

• Draft modules and courses are visible to builders, never to learners.
• Learners see exactly what their teams' assignments grant — see Enrollments.
• Archived content disappears from learner and default views.