Find your way around Admin

Admin is where you set up schoolOS for your district: your account, your people and schools, and the settings for each product you have. The page is titled Admin Settings. It lists every Admin page you can open, grouped into sections, each with its name and a line on what it's for. Select one to open it.

To open Admin at all, your role needs the Open the Admin console permission. Without it, schoolOS sends you to your home page and tells you Admin isn't yours to open.

Search Admin#

The Search settings box at the top filters the list as you type. It matches a page's name and the short description under it, so "sla" finds SLAs and "logo" finds Account Settings, where your logo is on the Branding tab.

• Sections with no matching pages are hidden while you search.
• Sections with a match open, even if you'd collapsed them.
• If nothing matches, you see No settings found matching and your search, with Clear search to start again.

Clear the box to see every page again.

Sections#

Every section starts open. Select a section's name to collapse it, and again to open it. A collapsed section shows how many pages it holds, and stays collapsed the next time you come back on this browser.

The sections appear in this order:

• Account. Your account as a whole: Account Settings (with your branding), AI Features, Departments, Integrations, Workflows, Views and Logs.
• Otto. The AI Otto for admins: AI Capabilities and Prompts (its suggested prompts and review queue).
• Locations. Your schools and buildings: Import Locations & Rooms, Locations and Location Fields.
• People. Import Users, Users, Roles, User Fields and Fines.
• Assets. Settings for schoolAssets: import, asset tags, labels, funding sources, statuses, types, fields, depreciation, manufacturers and models.
• Tickets. Settings for schoolHelpdesk: statuses, priorities, types, topics, tags, fields, teams, SLAs, macros, routing and repair kiosks.
• Agent. Settings for schoolAgent: Configuration, Conversations and Analytics.

The same sections and cards appear in the Admin sidebar, so you can move between pages without coming back here.

Why a card is missing#

Two separate checks decide which cards you see. A card needs to pass both.

1. Your plan. Some sections only appear when your district has the product:

| Section | Appears when your plan includes | | --- | --- | | Assets | schoolAssets (devices or inventory) | | Tickets | schoolHelpdesk for IT | | Agent | schoolAgent |

Account, Otto, Locations and People appear for every plan. If a whole section is missing, it's almost always the plan. Talk to schoolOS about adding the product.

2. Your role. Each card also needs a permission. For example, Departments needs Manage departments, Views needs Manage shared views, and Logs needs View the audit log. If a section is there but one card isn't, your role doesn't include that card's permission. An admin who can edit roles can add it on Admin › People › Roles. See Roles and permissions.

One card has a third check:

• Workflows is an early-access page. It only appears after schoolOS turns it on for your account, even for full admins. Ask schoolOS if you need it.

A few cards and tabs are for schoolOS staff only, such as the Permissions and Built-in defaults tabs of Roles. Districts never see them.

Two examples:

• A district with only schoolAgent. Its Super Admin sees Account, Otto, Locations, People and Agent. There's no Assets or Tickets section, for anyone, until the district adds schoolAssets or schoolHelpdesk.
• A help desk lead with a role of your own that has Helpdesk settings at Full and Admin console at View. They see the Tickets section's settings, like SLAs and Macros, but not Teams, which needs Users at View. In Account they see Account Settings (both its tabs) and Logs but not Departments, because managing departments comes with Admin console at Edit.