Before you start
Only the saMas team makes someone a super admin. If you do not see the Platform menu after you sign in, ask them.
-
Sign in
- Open beta.samas.school, the main saMas School site. On production it is admin.samas.school.
- Press Continue with Google if your email is a Google account. Otherwise type your Email address and press Continue.
- On Check your email, type the 6-digit code we sent you and press Sign in.
You'll seeYour dashboard, with the Platform menu on the left. -
Set up your two-step code
- Press your picture at the top right, then Account and security.
- Press Set up two-step. You may be asked to confirm it's you first.
- Scan the QR code with an authenticator app (Google Authenticator, Microsoft Authenticator or 1Password) and type the 6-digit code it shows. Press Turn on two-step.
- Save your backup codes with Copy or Download, then press I have saved them.
Each backup code works once, for a day your phone is not with you. Office work on the admin site needs this code. If the code does not match, delete older saMas School entries in your app and set your phone's time to automatic.
-
Check the Platform menu
- The left menu should show a Platform group: Schools, Operations, Help health, Help buddy, Reports, samas.school, Platform keys, Internal API docs and Requirements graph.
- If it does not, you are not a super admin yet: ask the saMas team.
Your first week
In this order. High tasks first.
-
Read the reports overview
- Open Reports, then the Overview tab.
- Pick the window: 7 days, 30 days, 90 days or All.
- Read the tiles: open now, cannot carry on, fixed, confirmed by reporters and the median times. Press a tile to open those reports in the Queue.
- Look at By school, Needs a person, Aging and Over time.
You'll seeEvery number opens the reports behind it in the Queue, with a button above the list that says how it was filtered.Production, beta and demo keep their own reports. Use the Environment links at the top to see another one.
-
Work a report in the Queue
- Open Reports, then the Queue tab. Narrow it with Kind, School, Status and Age, or press Mine.
- Pick a report on the left. Set a priority with P1, P2 or P3 and choose who looks after it under Assign.
- Write to the reporter in the thread at the bottom and send it.
You'll seeThe reporter sees your message under My reports.School matters only reach you once the school office passes them on.
-
Mark a report fixed, with a picture
- When the fix is live, open the report in the Queue and press Mark fixed.
- Write what was fixed in a sentence, and add 1 to 3 pictures of the fix working under Pictures of the fix.
- Press Mark fixed.
You'll seeThe reporter is emailed with the pictures attached and asked whether it is fixed for them. The email is copied to you and to that school's admins.An app problem cannot be marked fixed without a picture. Never email a reporter yourself, around the app or the API.
-
Send school matters on and link repeats
- A report the school office should handle: press Send to the school, write why, and press Send it. It leaves your queue.
- The same problem reported twice: press Same as another report, paste the first report's reference, and press Link. This reporter gets the fixed email when the first one is fixed.
- Nothing to fix: press Close without a fix.
-
Decide what joins the roadmap
- Open Reports, then the Roadmap tab. The fixer's proposals wait under Proposed.
- For each one press Confirm, Merge or Decline. Decline asks for a note the reporters read.
- To add an item yourself, press New item, write a title and what a school will be able to do, and press Add it.
- To put an idea from the Queue on the roadmap, open it there and press Add to roadmap.
You'll seeEach stage change emails the reporters of the item's ideas once. -
Show a roadmap item on samas.school
- Press an item on the Roadmap to open it. Under Stage, move it to Considering, Planned or Being built.
- Tick Show on samas.school.
You'll see"Shown on samas.school". The public Wishes page shows its stage and how many schools asked, never a school's name. Once released, What's new shows it with its pictures.The box shows only from Considering on. Not now and Declined take an item off the site by themselves.
-
Mark a roadmap item released
- When the work is live, open the item and press Mark released.
- Write what is new, the page to try it on, and add 1 to 3 pictures under Pictures of it working.
- Press Mark released.
You'll see"Released; every school is told." Every open idea on the item is marked fixed with your note and pictures, and every active school gets the update email.Released is final. The box says how many people will be emailed before you press it.
-
Tell every school about a fix
- Every fix or new feature people will notice is told to every active school once it is live, reported or not.
- There is no screen for this yet. It is sent through the saMas API (the school update email), with what changed, the page to try it on and 1 to 3 pictures of it working. Ask in chat to have it sent.
- Mark released on a roadmap item already sends it, so do not send it twice.
The email goes to the school's admins and principals, with the pictures attached, and is copied to the sender. Anything about finance can also go to the finance in-charge. Update the help guides in the same change.
-
Check the daily fixer
- Open Reports, then the Fixer tab. Each run shows what it fixed, replied on, linked or proposed, or why it failed.
- Read Waiting for a person: those need you. Press Run now to ask for a run before the next one.
The fixer never touches money, sign-in, permissions or deletions; those always wait for a person.
-
Answer requests for a demo school
- Open samas.school in the Platform menu. The Requests tab lists requests from the public site, newest first; the filter starts on New.
- Press a request to see who asked, the size of the school, how to reach them and their fit quiz answers.
- Move it on with Contacted, Demo made, Live or Declined. Write what was agreed in Notes and press Save notes.
- Pick the school you made in The school made from it.
The page promises a demo within a working day. Each new request is also emailed to you.
-
Add a quote for the home page
- On samas.school, open the Quotes tab and press Add a quote.
- Write a first name and an initial, what they said, who they are and the day they agreed. Anyone under eighteen also needs the day a guardian agreed.
- Press Add it. Use Hide to take a quote off the home page, and Show to put it back.
A quote shows only once consent is complete. The names in the home page's register are set through the API or by asking in chat, never on this screen.
-
Make a platform key for automation
- Open Platform keys. Under New key, give it a Name and choose Stops working after.
- Tick only what it needs under What it may do. A key that replies on reports or tells schools asks who to copy on what it sends.
- Press Create key, then Copy and keep it in a password manager. Press Done.
You'll seeThe key is shown once. The Keys list shows each key, what it may do and when it was last used; Revoke stops it at once.A key that gives school roles must stop within 30 days, works only on beta, and emails the super admins on every use.
When you have time
-
Look at Help health
- Open Help health: how guides, ? panels and searches do across every school, and which guides need a person.
-
Answer questions the help buddy could not
- Open Help buddy. On the Overview tab, Questions with no guide lists what people asked that no guide answers.
- Press Reply, write the answer and press Send reply. The person sees it on the buddy. Better still, write the guide.
-
Check Operations
- Open Operations: Health and alerts, API figures and Jobs, with the email and webhook logs and maintenance mode.
Some platform work has no screen yet and is done through the saMas API or by asking in chat: listing a school on samas.school (only with its admin's written yes), the names in the home page's register, and the school update email. Data fixes and role grants go through the API too, never straight into the database.
When something goes wrong
| You see | What to do |
|---|---|
| The sign-in code did not arrive | Wait a minute and look in Spam or Promotions. Check the email address is the one your school has. Press Start over for a new code, or use Continue with Google. |
| This sign-in is not linked to any school yet | Your school has not added this email. Ask the office to add you, then sign in again. |
| Mark fixed stays grey on an app problem | Add at least one picture of the fix working under Pictures of the fix. |
| The Platform menu is missing | You are not a super admin on this site. Ask the saMas team. |
| Operations says: End View-as first | You are viewing the app as someone else. End View-as, then open Operations again. |
| Show on samas.school is not on the item | Move the item to Considering, Planned or Being built first. |
| The key is gone and was not copied | It is shown once. Revoke it and create a new one. |
Report a problem
- Press Feedback at the top of any screen, or Report a problem next to an error. The form opens beside the screen, so you do not lose your place.
- Choose what kind it is: Something is broken in the app, A question or problem for the school, or An idea or suggestion.
- Say what happened and how much it is stopping you: I cannot carry on, I can work around it or Just a small thing. Press Add a picture of this screen if it helps: you see it first, with fields blurred, and can hide anything private. Never passwords or codes.
- Press Send report. You get a reference number, and an answer within one working day under My reports. You can write back there, and attach one picture to a message with the picture button beside the box.
Check yourself
Three levels of five questions. Pass a level with 4 right to open the next. Your answers stay on this device.
The quiz needs JavaScript turned on.
Trained: Super admin
You passed all three levels. Take a screenshot of this card for your school office. Your certificate of completion will be ready to claim here soon; your result is kept on this device until then.