Darasa Hub - Learning Lions
Dira Portal Safety and Welfare ICT Support
SCS3.1

Workspace Admin I

Level 2 · BootCampSCS3 WorkspaceTaught week 5 Tuesday morning

Submit Your Work

What You Turn In

  1. Your change log, with the audit-log match (repo link)
    1. A row for every action, written before the click with the time; every row matched to the console's record or its gap explained
  2. The reference shop's access map (repo link) fill in on the hub
    1. Every person with unit, groups, role and a why; the owner alone with super-admin; read cold by your partner
  3. Your how-to card with the AI receipts (repo link)
    1. Six console paths in your own words, as the console was today; one 'AI receipt:' line per look-up
  4. Your two exports — stay in the evidence folder
    1. Users list and admin log CSVs in ~/scs/evidence/scs3.1, never in the repo; not attached
  5. Your client's access map — photo of the first page fill in on the hub
    1. In the client folder, from the owner's words, blanks marked 'ask the owner', staff names covered
  6. check-scs3.1 receipt and your method note
    1. Every NOT YET fixed; six lines, the sixth a real doubt and how you would find out
  7. Photo of the signed rules page and the Definition of Done
    1. Rules signed; the Definition of Done with your initials and your partner's fill in on the hub

Stuck, or want to check your thinking? Paste this card into your own AI and ask it to question you, not answer for you.

How

  1. Asha, by Saturday's update.
Done when
  1. Change log with audit-log match: A row per action written before the click, timed, with path, who, why and check; every row matched to the audit export or its gap explained; no time edited
  2. Reference shop's access map: Every person with unit, groups, role and a why; owner alone super-admin; groups and units not confused; read cold by a partner
  3. How-to card + AI receipts: Six console paths as the console showed them today; one AI receipt per look-up with what was different
  4. Users list + admin log exports: Both CSVs present, read by check-scs3.1; never in the repo
  5. Client's access map: From the CC1 notes and the owner's words; owner's row first with super-admin; blanks marked 'ask the owner'; nothing guessed; never in the repo
  6. check-scs3.1 receipt + method note: Every NOT YET fixed, automatic items PASS; six lines, the sixth a real doubt and a real check
  7. Rules photo + Definition of Done: Signed sandbox rules page; Definition of Done with two sets of initials; unit left as the rules require

Counts toward: the SCS3.1 badge, 1 to 3 stars · the client folder · attendance for the Taught and SGL blocks · LP (Lion Points) for accepted badge work.

Fill in the worksheet Submit work for SCS3.1