Roles and permissions
Organization and team roles, and what each can do.
Use this page to decide which role to give someone and to check what a role lets them do. Access in Vidext is role-based at two levels: the organization (your company's account) and each team (a group of people a course is assigned to). The same rules apply everywhere: in the app, in the chat where courses are built with Vidext's agents, and to AI assistants connected over MCP.
Organization roles
| Role | What it means |
|---|---|
| Admin | Runs the organization: people and roles, teams, organization settings, and all content, including archiving and deleting. |
| Member | Builds: plans and builds courses and their modules in the chat with Vidext's agents, and publishes courses across the organization. |
| Learner | Learns: signs in to a learning home listing the courses assigned to their teams. No creator dashboard, no chat, no settings, no AI assistant connections. |
| Requester | Has asked to join and is waiting for an admin. No access until approved, and then joins as a learner. |
What each organization role can do
| Action | Admin | Member | Learner |
|---|---|---|---|
| Build in the chat, and share a conversation with other admins and members | Yes | Yes | No |
| Build modules; create courses and add modules to them | Yes | Yes | No |
| Publish, update, and unpublish a course; withdraw or restore a module in it; turn on public access | Yes | Yes | No |
| Assign teams to a course | Yes | Only as admin of a team the course is already assigned to | No |
| Archive, restore, or delete a course; archive or restore a module | Yes | No | No |
| Invite people | Any role | Learners, into the default team | No |
| Change roles, remove people, approve or deny requests | Yes | No | No |
| Create teams | Yes | No | No |
| Organization settings: General, Certifications, LMS integrations | Yes | No | No |
| Connect an AI assistant over MCP (read-only) | Yes | Yes | No |
| Take assigned courses | Yes | Yes | Yes |
A chat conversation is visible only to the person who started it and the people they invite. Being an admin does not open someone else's conversation.
Team roles
| Role | What it means |
|---|---|
| Admin | Manages the team's settings, members, and invitations, changes which teams a course assigned to the team goes to, and sees learner progress and certificates for the courses assigned to the team. |
| Learner | Learns: gets the live modules of the published courses assigned to the team. |
Organization admins have admin rights in every team. Team roles never grant building or publishing: a team admin who should also build needs the organization Member role.
How invited people get a role
A team Learner invitation creates an organization Learner. A team Admin invitation creates an organization Member, then grants team-management rights; only organization admins can give the team Admin role. People who build content but do not manage a team should be organization Members and hold the team Learner role when assigned to a team.
How this plays out
- Who builds? Organization admins and members, in the chat. Learners never reach the creator dashboard or the chat.
- Who publishes? Organization admins and members. Vidext's agents build modules but never publish, and connected AI assistants only read. See Draft, built, and live.
- What do learners see? Live content only: the live modules of the published courses assigned to their teams. See Enrollments and Access control.
- Who manages people? Organization admins manage membership and roles; team admins manage their team's roster. See Members and roles.
Same rules for AI assistants
When someone connects an AI assistant to Vidext, the assistant acts as that person, in one organization, with that person's permissions and nothing more. Only admins and members can connect one. See Authentication for agents.
Last updated on