Features per cohort
Settings is where you shape what a cohort can do and who on your team can do what. The most-used control is the per-cohort feature toggle.
Turning features on and off
You can enable or disable each student-facing surface per cohort: wellbeing (check-ins), the workspace, timetable, events, the campus map, resources (quick links), saved items, and help. Different intakes can run with different feature sets without affecting each other.
When you disable a feature, it is hidden server-side, not just visually masked. The navigation link disappears and the content never renders for that cohort. There is no half-on state a curious student could poke at.
Brand
Your institution's brand (logo, accent colour, fonts, email domains, sign-in method, and the crisis copy and signals) is set at the institution level, not per cohort, so it stays consistent everywhere a student sees First Six. It is read once when a session starts.
Audience tags and staff scope
Audience tags do double duty. They are the campus, program, and role labels you attach to content for targeting, and they also define staff scope: a staff member can only author for the tags they are scoped to.
That means scope is not a separate permissions screen bolted on top; it is the same tagging system, used to decide both who content reaches and who is allowed to write it.
The fastest answer is usually one question away.