Trust and consent — DSAtlas for colleges

Joining

In by invitation, out at any time.

You inviteShare a link or a code with a class, batch or section.
They chooseEach student sees exactly what you would see, and picks what to share.
You see only thatNothing else, and nobody who hasn't joined.
They stay in chargeNarrow what they share or leave at any time. Access ends at once.

Consent

Switch what this sample student shares, and watch your team's view follow. Leaving ends everything at once.

Try it: switch what this sample student shares.

IdentityAlways shared: needed to join
Progress summaryProblems solved, topics covered, difficulty split and activity trend
Topic coverage vs cohortCoverage per topic, and gaps against the cohort median
Verified platform statsPer-platform counts, contest ratings and how well each account is verified
Public projectsPublic GitHub repositories and their READMEs
ContactEmail address

Leave your workspaceAny time, from their own settings. No one to ask.

Changes the moment the student does.

4 of 6 shared

Never shared with anyone: coding-platform passwords, the code you write, private repositories.

Viewers on your teamThe same, read-only. They can't change or export anything.
Other organizationsNothing. Joining yours never opens anyone else's.
CompaniesNothing, unless the student applies or accepts their invite.
Sponsors and researchersAnonymous totals only. Never a name.

Staff

Who on your team can do what

Action	Owner	Admin	Viewer	Student
View cohort dashboards	Yes	Yes	Yes	Own data only
Create or edit cohorts	Yes	Yes	No	No
Invite or remove students	Yes	Yes	No	Can leave
Assign problems to cohorts	Yes	Yes	No	Receives
Export or shortlist	Yes	Yes	No	No
Invite staff, change roles	Yes	Yes	No	No
Plan, billing and usage	Yes	View	No	No
Audit log	Yes	No	No	Own history
Close the organization	Yes	No	No	No

A workspace always has at least one owner. Admins invite other staff; only an owner makes another owner. Every change is written to the audit log.