auth-and-rbac

Define authentication, session management, and RBAC contracts for the Myelin platform.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Seth-arc/myelin-platform --skill auth-and-rbac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-and-rbac
Source: https://github.com/Seth-arc/myelin-platform/tree/main/primary_build_source/docs/skills/2
Command: npx skills add https://github.com/Seth-arc/myelin-platform --skill auth-and-rbac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides the definitive contract for all authentication, authorization, and access control logic within the Myelin platform, ensuring consistent and secure user management.

Core Features & Use Cases

  • Role-Based Access Control (RBAC): Defines eight distinct roles (Student, Lecturer, Admin, etc.) with specific permissions.
  • Authentication Methods: Supports email/password, OIDC, and SAML 2.0, with clear security guidelines for each.
  • Session Management: Outlines rules for session scope, revocation, and invalidation.
  • Use Case: When implementing a new feature that requires users to log in and access specific resources based on their job function (e.g., only Lecturers can review submissions), consult this Skill to ensure the correct roles and permissions are applied.

Quick Start

Use the auth-and-rbac skill to define the role of a new user as a 'Lecturer' within the 'myelin-platform' tenant.

Frequently Asked Questions about auth-and-rbac

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement role-based access control for specific user roles like Lecturer or Student?

Role-based access control is implemented by enforcing eight predefined roles, such as Student and Lecturer, each with specific permissions that gate resource access and platform interactions based on the user's job function.

How does session management work for authenticated users?

Session management enforces security by defining strict rules for session scope, revocation, and invalidation, ensuring that user identities are maintained securely across all platform interactions.

Can I use SSO and SAML 2.0 for authentication alongside email and password?

Yes, authentication supports email/password, OIDC, and SAML 2.0 for single sign-on integration, providing clear security guidelines and password hashing protocols to ensure secure identity verification across the platform.

When do I need to consult this access control contract during feature development?

You need to consult this access control contract when implementing new features that require users to log in and access specific resources based on their job function, ensuring correct roles and permissions are applied.

What are the limitations if I need a custom role outside the predefined eight roles?

This access control contract enforces strict adherence to eight predefined roles, meaning custom roles outside of this schema are not supported by default and may break permission gating logic across platform interactions.