Run the learning platform
The right workspace for each person.
Analytics staff, school managers and content managers receive explicit permissions and scopes.
School manager: example access
- Classroom scope
- Northstar School · Python Lab + Web Studio
- Classroom and learner lists
- Granted
- Submission summaries
- Granted
- Full learner detail
- Additional permission; off by default
- Analytics tabs
- Overview · Grading · Progress
Permissions and scope answer different questions
- 01
Role
Which workspace does this person use?
- 02
Permission
Which operations or depth of detail can they access?
- 03
Scope
Which schools, classrooms or content records are included?
Non-empty classroom-scope dimensions intersect. An empty dimension means no restriction on that dimension. No account or permission is changed here.
What this part of Arc does
- Role-specific permissions and landing pages
- Scope by region, school, school code and selected classrooms
- Separate student-summary and student-detail permissions
- Content-pack/questionnaire scope and independent builder-library access
This is a browsable portfolio interpretation of Arc’s workflows with fictional examples. Navigation, filtering and theme previews work here; editing, execution and platform services belong to the original application.
Inside the original application.
This demo view is grounded in Arc’s source. Explore the recorded workflows for a look at the original interface.
Source references & review notes
config/system_users.phpapp/Platform/Portals/Admin/Controllers/AdminSystemUsersController.phpapp/Platform/Domain/Analytics/V3/ActorScopeRestrictions.php
Source reviewed at development revision 5549bf96. Original captures have their own pinned revisions; the live platform has a separate release.