Role-based capabilities
Teacher, administrator, developer, and other capabilities are checked by the service before protected workflows are exposed.
Faraday AI separates account access, workspace capabilities, connected providers, and institutional data authority so that one kind of access is not mistaken for another.
Faraday AI uses multiple boundaries together rather than treating a login or provider connection as universal authority.
Teacher, administrator, developer, and other capabilities are checked by the service before protected workflows are exposed.
Saved work and education records are scoped to authorized owners, workspaces, and organizations.
Connecting a Microsoft or Google account identifies that provider account; it does not grant classroom, school, or district-data permissions.
General, personal, guest, and synthetic-demo workspaces are not authorized for real student records.
Processing real education records requires an authorized school or district workspace, a written agreement, configured access, and a documented purpose and retention period.
Educators and institutions remain responsible for notices, consent or authority assigned to them, professional review, and decisions that must stay human.
Product features and security controls do not by themselves establish FERPA school-official authority, verified COPPA school consent, a HIPAA business-associate relationship, or a certification. Contractual and legal requirements must be confirmed for each rollout.
Microsoft 365 storage is the currently established external connection. Other Microsoft, Google Workspace, SSO, SIS, LMS, calendar, mailbox, and rostering capabilities depend on provider setup, administrator consent, account validation, and the specific institutional rollout.
Bring your roles, systems, data classifications, approval needs, and retention requirements to a tailored walkthrough.