COPPA & under-13 accounts
COPPA-aligned school-directed provisioning.
RunMyCampus is built for institutions to control when and how learner accounts are created—not for direct child sign-up without school direction.
Live preview · Platform
Illustrative campus data — updates with this workspace personality.
[
&
#
x
2
7
;
B
u
i
l
t
f
o
r
s
c
h
o
o
l
s
w
o
r
l
d
w
i
d
e
&
#
x
2
7
;
,
&
#
x
2
7
;
F
l
e
x
i
b
l
e
a
c
a
d
e
m
i
c
c
a
l
e
n
d
a
r
s
&
#
x
2
7
;
,
&
#
x
2
7
;
M
u
l
t
i
-
c
u
r
r
e
n
c
y
f
e
e
s
t
r
u
c
t
u
r
e
s
&
#
x
2
7
;
,
&
#
x
2
7
;
R
o
l
e
-
b
a
s
e
d
p
o
r
t
a
l
s
&
#
x
2
7
;
,
&
#
x
2
7
;
O
f
f
l
i
n
e
-
r
e
a
d
y
w
o
r
k
f
l
o
w
s
&
#
x
2
7
;
,
&
#
x
2
7
;
S
e
c
u
r
e
a
u
d
i
t
t
r
a
i
l
s
&
#
x
2
7
;
,
&
#
x
2
7
;
M
u
l
t
i
-
c
a
m
p
u
s
s
u
p
p
o
r
t
&
#
x
2
7
;
]
What this surface delivers
Concrete outcomes your teams should expect—not a generic feature list.
School as gatekeeper
Accounts for learners under 13 should be created by the school (or designated staff) using your consent and directory policies—not open self-registration.
Parental consent workflows
Your institution selects notice and consent patterns appropriate to jurisdiction; RunMyCampus supports role-scoped access and auditability for those workflows.
Data minimization
Collect only fields required for education operations; restrict staff roles to minimum necessary access for each workflow.
Why teams standardize here
- Predictive risk scoring and intervention action-center workflows.
- Student passport and transcript portability across schools.
- Super-admin mission control for approvals, billing, and support.
Popular solution topics
Start with a focused story—browse the full solutions hub when you need the complete map.
See it with your team
Book a guided walkthrough, validate your architecture, and align rollout with the right operating model.